-   Linux - Networking (
-   -   Do I need to restart Named after making DNS changes? (

imsam 07-23-2004 12:26 PM

Do I need to restart Named after making DNS changes?

I'm fairly new to Linux. We're using RedHat 9.

I think after making DNS record changes I need to increment the Serial Number by one, save the .dns file and restart named. Is this correct?

I'm also having trouble restarting named. I did some google searches and they suggest I need to do /usr/sbin/ndc restart but when I do that I get an error message that states there's no such file.

One article I found suggests, if I don't have ndc, I must have an old system. It suggests I do /usr/sbin/named restart.

However, when I try that it's expecting more parameters.

So I'm a little confused about the process. I'm also not sure if I need to go to the secondary server and do anything after making my changes on the primary server.

I'd appreciate some pointers on how to handle DNS on a Linux box. Thanks.


ppuru 07-23-2004 12:39 PM

after each change to your .dns file, you must change the serial number - increment it by one.

The unwritten standard is yyyymmddnn e.g. if you made a change for the 5th time today, you can have a serial number of 2004072205.

You do not really have to restart named.

imsam 07-23-2004 12:53 PM

What if I create a new dns record?
Do I need to restart named if I create a new dns record i.e. a new domain?

And how do I restart named anyway? Thanks.


ppuru 07-23-2004 01:14 PM

you need not restart named. You can simply reload it.

If you are using RedHat/Fedora/Mandrake

service named reload
OR simply

kill -HUP `pidof named`
Please note ` is not apostrophe.

imsam 07-23-2004 03:13 PM

Do I have to create DNS records on the secondary server?
If I'm creating the necessary records for a new domain, I do the following on the primary server:

1. file in /var/named
2. Put a reference to file in /etc/named.conf
3. service named reload

After this, do I need to go through the same steps on the secondary DNS server? Obviously, I set it so that the records read "slave" instead of "master" on the secondary server.



ppuru 07-24-2004 04:01 AM

You do not have to do anything to the secondary server .. only edit the named.conf on your secondary server to make it aware of the new domain.

imsam 07-24-2004 08:56 AM

Thank you all
Thank you very much all for your valuable help.

bitfuzzy 07-24-2004 01:02 PM

if 'ndc' isn't available try:

rndc restart

All times are GMT -5. The time now is 12:45 PM.