Caching nameserver

Jeff Lightner jlightner at water.com
Tue Dec 19 17:01:13 UTC 2006


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?

-- 
Scott B. Ackerman
1212 Baker Street
Fort Collins, Colorado 80524
970-231-9035
www.scott-ackerman.com


"Every improvement in the standard of work men do is followed swiftly
and inevitably by an improvement in the men who do it" - William Morris 




More information about the bind-users mailing list