I do enjoy my Apple products, but I have to say OS X’s behaviour with DNS leaves me in a permanent state of annoyance. This is not a problem I have with any other hosts on my local network. All the Windows, Linux and Solaris machines in my environment, with the same DNS configurations, have absolutely no problem whatsoever.
Some engineer or engineers at Apple responsible for name resolution coding in OS X, as far as I’m concerned, are deserving of atomic wedgies for every day this ‘feature’ persists:
So, I can resolve a hostname via official DNS tools (and before you ask, dig gives the same answer as nslookup), but if I then try to connect to the hostname, I’m told it doesn’t exist. And so, I’m told via a cat of /etc/resolv.conf that the file isn’t really used any more, and checking the network configuration:
According to various Apple threads, this is likely to be caused by a nameserver not responding fast enough, and Apple dropping it from the nameserver search list, which can be restored by killing/restarting mDNSResponder. But no, that doesn’t resolve the problem and, I only have one DNS server for my home environment – and it’s all on the same LAN, so there’s not any latency issues. Certainly no other hosts on the network (virtual or physical) has problems. Just the OS X hosts. In fact, not even the iOS devices have name resolution problems. Just the OS X servers.
You may ask – why haven’t I posted this on an Apple support forum? I’d answer with – why would I bother? After all, I’m increasingly finding that OS level support forums for the most part are overrun with pretentious gits who are actually more interested in pointing out why you should be doing something differently than answering your questions. That’s why I’ve given up asking questions in them.
No thanks, I don’t a bunch of people to tell me that I should just remember to type “.local” at the end of every bloody hostname in order to use bonjour name resolution instead. I. Just. Want. DNS. To. Work.
Is that too much to ask?