Stupid Windows DNS
Posted in Tech
First dog watch, 1 bell (4:45 pm)

Well here goes another Windows rant. I set up a new Redmine server on the internal network. I also added records for it to our primary and secondary DNS servers. Unfortunately Windows hosts couldn't reach it, or even ping it!

I used nslookup (which I thought was deprecated years ago in favor of dig but apparently not by Microsoft) and sure enough, DNS queries halted at our domain server, which only serves out local DNS (not for the Redmine server). It should have deferred the query to an authoritative DNS server, but it wouldn't until I told it to dump its entire DNS cache.

Windows continued to refuse to resolve the name until I ran a ipconfig /flushdns on each host that exhibited the problem. This should never have happened with a hostname that has never been used before.

Can you say "stupid?"

Leave a Comment »

Leave a Reply