This is the mail archive of the cygwin-apps mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [ITP] bind-9.6.0-1

At 12:37 PM 1/21/2009, Corinna Vinschen wrote:
>On Jan 21 11:20, Yaakov (Cygwin/X) wrote:>
> Corinna Vinschen wrote:
>> > Why does the bind package require an /etc/resolv.conf file?  Isn't that
>> > used only by the resolver lib?  And the resolver lib is part of Cygwin
>> > 1.7 anyway, or in the minires package for Cygwin 1.5.  Minires/Cygwin 1.7
>> > don't need a resolv.conf file, so why does bind?!?
>> I was attempting to avoid a FAQ.  BIND is a DNS suite, and it needs to
>> know the address of a nameserver in order to do lookups.  The usage of
>> /etc/resolv.conf is well documented in both the manpages and the online
>> manual.
>Ok, but the Cygwin resolver lib also works without this file because the
>nameserver information can be (and is) fetched from Windows.  Would it
>be feasible to use the same method as the resolver lib so that we don't
>have two libs using different methods?  The resolver lib uses
>/etc/resolv.conf, but falls back to calling the Windows function
>GetNetworkParam to fetch this information if the resolve.conf file
>doesn't exist(*).

There is another problem. If resolv.conf exists then minires and the cygwin 1.7
resolver default to using the name servers directly instead of using the internal
Windows resolver.
That's useful to those who don't want to use the default dns server of their isp, which
may offer a "DNS assistance" feature that maps non existent domains to a web
server operated by the ISP, while keeping dns assistance for their web browser.

If it's a problem we can change the behavior of the cygwin 1.7 resolver to require
more than the existence of resolv.conf to enable the bypass.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]