On 5/25/2012 7:40 AM, Yang Tse wrote:
> Nice can of worms here...
Nothing unexpected from Microsoft ;-)
> MS 'fixed' default name resolution behavior in Vista to make it work
> more like c-ares does, probably due to the security implications of
> previous behavior.
>
> http://blogs.technet.com/b/networking/archive/2009/04/16/dns-client-name-resolution-behavior-in-windows-vista-vs-windows-xp.aspx
>
> Some info of 'old' behavior...
>
> http://technet.microsoft.com/en-us/library/cc961411
Interesting read, thanks for the pointer.
But... has nothing to do with the way c-ares handles this, which is
independent of the way Windows handles it (as described very well in the
first article).
c-ares could be improved, or like Dima points out, you can work around
the problem with changes in configuration (either the DNS server, or
Windows).
My preferred solution would change the order in ares_init.c's
get_DNS_Windows(), use get_DNS_NetworkParams() first, get the DomainName
from the fi struct, and enable/use config_domain() for the Windows case.
Simple, nowhere as complex as the dot option on host, or the similar,
but way more complicated, functionality on Windows as described in the
article.
-- René BerberReceived on 2012-05-25