[openbeosnetteam] Re: our package
- From: Philippe Houdoin <philippe.houdoin@xxxxxxx>
- To: openbeosnetteam@xxxxxxxxxxxxx
- Date: Sat, 4 Sep 2004 18:26:54 +0200
Lars Hansson said:
> resolv.conf is just a configuration file for the stub resolver. In
> effect it "supports" both static and dynamic entries with the lookup
> statement, ie lookup file bind.
Like many "settings" files, user don't expect the system modify them in their
back. Fir me, resolv.conf is just a user-defined list of DNS server(s)
address(es) the resolver should consider. From his (the resolver) point of
view, there're static entries.
> I dont see how it hurts to keep this
> file around since
It doesn't hurt, but we want to remove most if not all external settings files
depencies. The stack should works fine, using automatic (aka dynamic)
configuration guessing.
> the stub resolver has to get it's configuration from
> somewhere.
From DHCP protocol, for example.
If available, obvioulsy, but asking for an DHCP server must be the default way
to configure each interface. In the process, if DHCP server(s) is present, it
make the configuration of DNS resolver automatic too.
We still want and need to support user-defined configuration, using these
well-known Unix settings files, but only for this purpose, not as a mandatory
for the stack to run fine.
> I think you might have resolv.conf confused with the hosts file here.
I don't think I was, but who know?! ;-)
Am I wrong considering resolv.conf provide a user-defined ordered list of name
servers addresses the DNS resolver should query when he needs to resolve an
host name?
DHCP, on the other side, provide dynamicly a preferred name server (or is it a
list, can't remember) to use, per interface. We must add this server to DNS
resolver's list of servers, no?
Or did I totally miss why it's called Dynamic Host Configuration Protocol!?
About /etc/hosts, this file is a permanent store of user-defined (aka static)
address <-> name list the DNS resolver should look into first before (when not
found) query name server(s).
To put shortly, both files are not mandatory but allow user to define
him/herself extra data the DNS resolver could use to do his job.
Our stack must support them, but should not depends on their presence to run.
That's not the case currently.
> > But I've fear about it.
> > Do you guys know about good/better opensource (and compatible with Haiku
> > licence) DNS resolver than BIND's one?
>
> skadns, BSD-like license
> http://www.skarnet.org/software/skadns/index.html
>
> djbdns' library interface, Public Domain (afaik)
> http://cr.yp.to/djbdns/dns.html
>
> adns, GPL
> http://www.chiark.greenend.org.uk/~ian/adns/
Thanks.
I'll look at them for R2 purpose, but I trust Waldemar when he said BIND 9 is
way better coded than previous ones, and it's also the one who get security
issues fixed first, so let's try to keep with BIND, just twisting it for our
needs.
Until we can't stand it anymore ;-)
- Philippe
Other related posts:
