On Fri, 2013-12-20 at 22:29 +0000, Bryan Harris wrote:
Hi Jakub,
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

Well, I had originally tried for something else, but it was not up to me and for whatever reason the .local in the domain was decided upon at some point by the customer. To be honest the thought of the domain causing problems has not even crossed my mind until your email. I suppose that I would need to know for sure that this would all work with a different domain name, which I may not be able to do.

Thanks for your response. I will try and remember this next time someone tries to use a .local for the domain.

Bryan