Subject: Re: Named holding back dns?
To: Grant Stockly <gussie@stockly.com>
From: Manuel Bouyer <bouyer@antioche.lip6.fr>
List: port-i386
Date: 08/04/1999 12:01:43
On Tue, Aug 03, 1999 at 08:22:37PM -0800, Grant Stockly wrote:
> I get my IP by DHCP.
> 
> You see, I don't like the IP they give me so I have to go through this big
> long process of:
> 
> ifconfig ae0 inet 24.237.1.238 netmask 255.255.248.0 broadcast 24.237.7.255
> ifconfig ae0 alias 24.237.6.172 netmask 255.255.248.0 broadcast 24.237.7.255
> 
> 1.238 being the IP I want and 6.172 being the IP they gave me.
> 
> After pinging 24.237.0.1 (inetgw.anchorage.ak) it picks up that the IP I
> want is 1.238.
> 
> I've done this in the past and don't remember having to kill and run named.
> 
> I plugged my BSD server and Mac into a hub, then a switch to monitor the
> BSD server.
> 
> Using EtherPeek I found out that there were requests sent to my computer
> for www.stockly.com, and my computer sent replies, but the remote computer
> "didn't care".
> 
> Once I killed named and ran it, all the computers trying to reach it all of
> a sudden "cared".

Well, I think it's because named looks for interfaces addresses at start
time. If you change them named won't notice it, you have to restart it.

--
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
--