It seems that Windows by default caches the result of failed (aka. negative) DNS lookups for 6 minutes!

If you're using dynamic DNS in your company, this can be pretty upsetting. Imagine: you try to check whether a virtual machine is up and running by pinging it's FQDN (eg. virtual12.example.com). Since you use dynamic DNS registration, the ping request will tell you that the DNS request failed. What you probably don't know is that the "DNS Client" Windows service will cache this reply for you for 6 minutes! You start the virtual machine and expect to be able to ping it in a few seconds. Wrong! You're DNS client won't find the IP for the virtual machine (even though the VM already registered the hostname with the company DNS server) for another 6 minutes.
Recent comments
1 day 14 hours ago
1 day 19 hours ago
3 days 3 hours ago
3 days 7 hours ago
3 days 11 hours ago
5 days 8 hours ago
1 week 9 hours ago
1 week 2 days ago
1 week 5 days ago
2 weeks 44 min ago