I am checking out NO-IP's service one my home server. I have the update client installed and all seemed well.
I have a caching only name server running on the local network as well.
The problem: When the modem reboots and changes ip addresses, my local name server remembers the old one and the page is inaccessible.
Any thoughts on how to get past this???

thanks,

Fmertus

Sorry i can't awsner your question...

But coudl you tell me how you setup the Caching Name Server, I'd like to do one for my hoem network.

Thanks.

I was using Redhat 8.0 and it comes with a config file already to go, just activate the services.
I can post the document that I wrote for class...

The first part of this project is setting up and configuring a cache only DNS server. The default configuration file is included with commentary. I did find that most of the documentation on this was poorly written. It took several searches and piecing together the info to figure this out.

· First edit the /etc/named.conf file (use vi).

· Forwarders was added by me. The DNS servers mentioned are for my ISP. The rest of the file was left alone.

// generated by named-bootconf.pl

options {
directory "/var/named";
forwarders { 216.104.64.5; 216.104.72.5; };
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};

//
// a caching only nameserver config
//
controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
zone "." IN {
type hint;
file "named.ca";
};

zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};

zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};

include "/etc/rndc.key";

· Now we need to set ‘named’ to automatically start on reboot. We do this by adding a link from /etc/rc.d/init.d/named to /etc/rc.d/rc3.d/.

o ln -s /etc/rc.d/init.d/named to /etc/rc.d/rc3.d/S88named
o I used S88 to ensure that all other network parameters were configured prior to bringing up the named daemon.
o OR you can use chkconfig named on

NOTE: The two methods listed are an example of the odd writing style of the author(Kabir). I am not sure why he insists on doing things different ways throughout the book.

· Then start the named daemon.

o /etc/init.d/named start

If all goes well this will start the server going. At this point you will either need to reconfigure your dhcp server to dish out this new dns nameserver or reconfigure your /etc/resolv.conf.

· If you use DHCP then resolv.conf is automatically generated. Otherwise:

o vi /etc/resolv.conf

o change ‘nameserver xxx.xxx.xxx.xxx’ to the IP address of your DNS server.



I hope this helps...