[clug-talk] Shaw DNS Not Updating
gustin at echostar.ca
Sun May 14 23:27:52 PDT 2006
-----BEGIN PGP SIGNED MESSAGE-----
Answers threaded below.
Brad Camroux wrote:
> This was an interesting thread, and I'm sorry I'm so late into this. But I do have two
> On Mon, Apr 03, 2006 at 02:22:21PM -0600, Gustin Johnson wrote:
>> 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 184.108.40.206;
>> There are a lot of interesting options in here, but this should get you
> What does "supersede domain-name" do? (I'm sorry... I have had a lot of trouble finding
> answers to DHCP questions through the online "help" in the past.)
Basically the DHCP server sets the default DNS suffix (it is referred to
by a number of different names), the supersede domain-name option
replaces what ever the DHCP server assigns with one that you set.
>> 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.
> What is the issue with recursive DNS? I've recently set up a BIND/DNS server on my home
> PC, but had a hard time understanding some of the stuff about recursion. They don't often
> seem to make clarity a priority when writing books on the subject.
Basically recursion allows for for querying all domains. So in your
case, you would want to lock it down so that only hosts within your LAN
could make recursive requests, while those outside your lan only gets
responses to the domain(s) that you manage (if any).
The site tldp.org has a couple of DNS and bind docs. Also the orielly
book is really good IMO.
> Cheers, and sorry again for my late reply ;O)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the clug-talk