Caching nameserver

[Sten Carlsen]

On FCx you should look for man dhcpd and look for client-enter-hook or
something like that.

That is a method to get your own shell script run instead of the
standard one. I have made an empty function and I no longer see this
problem. This way you can replace the script that overwrites your
/etc/resolv.conf

It is possible and I would even say recommended to think about
implementing the same method for NTP if you want your own setup of that.


Jeff Lightner wrote:
> Haven't done it on FC4. 
>
> On Debian I was using dhclient and edited /etc/dhclient.conf.  In there
> I uncommented the line for superseding the domains:
>
> supersede domain-name "water.com dsw.net dmz.water.com";
>
> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
> Behalf Of Scott Ackerman
> Sent: Tuesday, December 19, 2006 8:59 AM
> To: bind-users at isc.org
> Subject: Caching nameserver
>
> I have just set up my Fedora Core 3 box with Bind and configured it as a
> caching name server. Everything seems to be working fine except that
> when I use "dig" the name server that responds is 68.87.85.98 which is a
> Comcast name server. Now the reason that I am getting that is because I
> am on a cable modem and the linux box that is set up to be my
> router/firewall/proxy server/dhcp server/dns server, is set up to
> acquire it's IP address via DHCP and whenever I restart it the
> resolv.conf file automatically gets changed to reflect Comcast's
> nameservers. I am sure that this is a simple problem, but how do I fix
> it?
>
>   

-- 
Best regards

Sten Carlsen

No improvements come from shouting:

       "MALE BOVINE MANURE!!!"