bind9-users Digest V5 #155

[Jean Tourrilhes]

On Wed, Jun 16, 2004 at 01:42:29AM +0200, Sten Carlsen wrote:
> Jean Tourrilhes wrote:
> 
> >	With my proposal, it does not matter. The key is too keep
> >configuration associated with interfaces through the "include"
> >directive.
> > 
> >
> I slightly disagree; the key is to use the includes in the right 
> sequence or priority. One thing I did not catch in your proposal was how 
> to select the proper include file at this moment (probably I was not 
> paying attention).

	Simple. If the file exist, you include it. If it doesn't, you
don't. DHCP and PPP make sure that they create and destroy those files
as needed.
	If both files exist, the first file take precendence and the
other definitions are added at the end, like if you were merging both
files.
	If you really want to be fancy, you can also use conditional
blocks, to make some part of the config conditional to an interface
beeing up. But, I don't think this is needed for the DHCP and PPP
case, this is more for the static config case.
	As I say, my proposal doesn't give you a complete solution,
working out of the box, but it offer hooks so that, in conjunction
with other scripts (PPP, DHCP, other), you can build the perfect
solution.

> Bringing up PPP does not change that file. Bringing WLAN down while PPP 
> is up does change it to reflect two different nameservers and no domain. 
> Wlan back up, changes it back to the one listed above.
> In short: it works like a dream.

	Well, you are only up'ing and down'ing interfaces, which is
easy (we agreed in an earlier e-mail that my proposal would allow to
do that). If you change manually the routing table, what happens ?
	I think that OS-X store all the interface DNS config in a
separate file associated with each interface, and each time an
interface state is changed, regenerate a new resolv.conf based on
those files. My only annoyance with that is that it's all hidden, so I
have no control on what's happening.
	I can assure you that if we don't extend resolv.conf, every OS
and every Linux distro will have it's own little magic sause on how it
automatically generate a resolv.conf, and you won't be able to change
this default behaviour anymore.

> >	Fortunately, we are not dealing (yet) with multicast DNS ;-)
> > 
> >
> You probably will have to, or you could use UPNP. Some sort of service 
> discovery will be needed to utilise such devices. Specially the very 
> mobile ones.

	I tend to work one step at a time. I currently just want to
make regular DNS works.

> Sten Carlsen

	Jean