Caching nameserver
Mark Andrews
Mark_Andrews at isc.org
Tue Dec 19 21:50:01 UTC 2006
> 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?
Look at you dhcp client's documentation.
> --
> 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 ine
> vitably by an improvement in the men who do it" - William Morris
>
>
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at isc.org
More information about the bind-users
mailing list