-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Actually this is a separate problem. What Carl is reporting is that his router is not pulling DNS servers out of the DHCP response that his router receives. Since his linux box does get this info, it is likely a bug in the DHCP client which resides in the firmware of his router.
What you are reporting is the DNS cache. Many (if not most) ISPs cache DNS requests to cut down on bandwidth utilization (this actually does make a big difference). 4 Days is on the high end of the "average" (think bell curve) but it won't be considered a "problem" until the 1-2 week range. For your debian box feel free to edit /etc/resolv.conf manually with vi/emacs/joe/some_obscure_text_editor_that_almost_no_one_uses If you want this to persist, you can edit the /etc/dhcp3/dhclient.conf file with these options: supersede domain-name "cg.shawcable.net mydomain.tld anotherdomain.tld"; prepend domain-name-servers 123.123.123.123; There are a lot of interesting options in here, but this should get you started. Finding recursive DNS servers outside of your ISP is going to get more difficult in the coming months. Most sane and or competent admins will be disabling recursion from outside their networks. Of course you could run a caching DNS server to service your home network, a quick goodle of caching dns server how+to (http://www.google.ca/search?q=caching%20dns%20server%20how%2Bto) or the venerable tldp.org (http://www.tldp.org/HOWTO/DNS-HOWTO-3.html) are good places to start for this. Cheers, Jon wrote: > This is a Shaw problem. Those two nameservers haven't updated in days. I > moved a domain four days ago and every nameserver on the planet points to the > new location except these two: > > nameserver 64.59.135.133 > nameserver 64.59.135.135 > > I can't remember the two I'm using now, but they're working fine. I'll dig > them up when I get home tonight. Of course every time I reboot I get the old > ones back. This might be a good time to ask how and where I hard code these > into my Debian system? > > I phoned Shaw on Sunday to "let them know", but I highly doubt anyone has > done anything about it. > > It's them though, not you. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEMYP9wRXgH3rKGfMRAghJAJ9IwwiiiCeStB8Kt+vj3fV9ngRmNwCgkh3a qMtBbW/yY9GLVhrLKnmld3w= =339g -----END PGP SIGNATURE----- _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
