|Matt Mossholder on 20 Apr 2010 04:46:16 -0700|
On Tue, Apr 20, 2010 at 7:23 AM, Michael Leone <email@example.com> wrote:My thinking is that you have two name services that think they are authoritative for the same .local domain. Since it can't find the host via mdns4_minimal (which is returning an NX, or host non-existant record), it isn't ever making it to straight DNS to try looking up the host.
Try removing mdns4_minimal, [NOTFOUND=return], and mdns4 from your hosts line in nsswitch.conf, then run "kill -1 1" and see if resolution works correctly.
Note that this is going to break multicast DNS for some newer devices like network attached printers, etc.
And finally, in the future, you should avoid using the .local TLD for AD. Yes, I know many sites do this, and some people advocate for it, but .local is part of the multicast DNS RFC, and has a defined purpose.
___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug