trentbuck@gmail.com (Trent W. Buck) writes:
James Harper <james.harper@bendigoit.com.au> writes:
I have a server that now refuses to resolve dns for the local domain (say xxx.local)
Knee-jerk reaction: .local is reserved for mDNS/DNS-SD crap, and GUI systems can get confused if you use it. Recommend .lan instead.
Apologies, I should have read the rest of the thread and seen this was already covered. But it does make me wonder -- what *is* the best practice for dealing with an AD-managed domain? Assume that AD is entrenched, you can't replace it with samba4, and it's (presumably) extremely nontrivial to change it to a different local domain, what do you do? The least worst solution I can think of is to ensure mdns/dnssd stuff is either not installed, or at least not in nsswitch.conf. That seems awfully prone to unexpected failure, though, as the OP showed.