Hot answers tagged domain-name-system
Many registries use the Extensible Provisioning Protocol (EPP) to facilitate their registrar interactions. It's worth noting that this is a whole separate protocol from DNS itself, specifically dealing with name registration and provisioning. It only indirectly populates the relevant zone in DNS. Unless you are either a registry or a registrar it really ...
No, those IPs don't belong to your ISP. They cannot change that, they belong to CloudFlare. You don't need a reverse DNS record for normal HTTP/HTTPS browsing. You could contact CloudFlare but I doubt they will configure it. Those IPs are shared between many customers.
Your host does not seem to be caching dns lookups. It should be. No Your operating system (not postfix) should cache every DNS record lookup it needs. NSCD is one common tool to cache "hosts" queries.
By default, the value of parameter smtp_host_lookup is dns. Because of that, postfix will always try to resolve the MX record recipient domain to determine the next-hop destination. Postfix rely on libc resolver to do the lookup so the expected behaviour would depends on the library. For example, postfix will alwasy do lookup via NS server defined in ...
NMap uses hostnames / IP addresses to scan hosts, but you used an URL, which includes the protocol also. Try using simply nmap website.
Are you trying to access this from the machine that has these entries in /etc/hosts? You might also want to check /etc/nsswitch.conf to check that 'hosts' comes before 'dns' etc. You can use getent hosts subdomain.sitename.domain.com to see what would be returned to an application when it does a lookup (do this from your [Linux] client)
You are asking for the NS record of www.timeandbill.de. That is not the same as the NS record of timeandbill.de. That is a specific record type you are asking for, which returns no answer as you don't have those configured. You should query for an A or AAAA record. So unless you want the subzone www.timeandbill.de delegated to different DNS servers ...
This sounds like expected behavior. Exactly what happens when the HTTP server receives a request that it does not know how to deal with can differ, but no redirect is expected unless it happens at the HTTP level. A CNAME record is merely stating that a given name in DNS is an alias of a different name in DNS. What happens when you have a CNAME record in ...
Only top voted, non community-wiki answers of a minimum length are eligible