update-resolver
* Emile van Bergen <emile-deb@evbergen.xs4all.nl> [030409 13:06]:
> > Hm, I never worked with anything dynamic like dhcp or ppp or even
> > several of them. So I wanted to ask why there are entries for
> > several configurations. (When I remember correct a program resolving
> > an address has no way to specify an interface for doing so).
>
> The advantage is that a system managing a single interface, does not
> need to 'edit' a shared file; each has a file of its own. That is an
> aspect of directories that's generally underused IMHO.
Seems I forgot enabling/disabling interfaces. If there was no reenabling
them it would suffice to give them as arguments to a update-resolver
and not store it inplicit to a file.
> A default version would concatenate (with due care to concatenate
> 'search' and 'domain' entries into 'search' lists, for sure), the
> various resolv.confs into a single one to which /etc/resolv.conf could
> be a symlink. Or, as said, you could initially skip this and just have
> the admin choose an interface to link his /etc/resolv.conf to.
As John Hasler pointed out, nameserver entries are not easily
concatenated, as only 3 are used. Merging to a 'search' has also
a maximum of 6 interpreted.
Thus there had to be some mechanism to determine which is used.
(An if concatenated, which sequence to use)
This seems to be a hard one, as there are good reasons for
taking the last actived (as newer interfaces are likely to be the actual
connection out) and for taking the earliest activated. (As this might
already be stable and the new one not working, leaving one with no
resolving).
Things might get more complicated by interfaces theoretical beeing able
to introduce a nameserver but not in a special case...
Hochachtungsvoll,
Bernhard R. Link
--
Sendmail is like emacs: A nice operating system, but missing
an editor and a MTA.
Reply to: