Simo Sorce wrote:
On Fri, 2013-12-20 at 22:29 +0000, Bryan Harris wrote:
> I re-ran the command with -d 255 and tried my best to sanitize, here
> it is. I am just posting this here in case someone with more
> expertise knows what to do or has seen the same thing. Thanks again.
>
> Also I noticed that just adserver does not resolve in DNS. I am
> _forced_ to use the FQDN like adserver.domain.local if I do a dig to
> find the A record. Does that make any difference? I could put it in
> my /etc/hosts or I could login to the AD server and run the DNS
> management GUI to find out what is going on.
>
> Oh on second thought, never mind my previous paragraph. After I put a
> "search domain.local" in my /etc/resolv.conf now I can resolve just
> the short host name.
>
Is your domain really called ".local" ?
That can cause quite some trouble on the Windows side, as .local is
generally reserved for mDNS ...
https://en.wikipedia.org/wiki/.local
Yes, one should remove any references to mdns related modules in
/etc/nsswitch.conf when using top-level domain .local.
(BTW: Is anybody really using mDNS/zero-conf? I really wonder why everybody
has to disable this cruft.)
Ciao, Michael.