Need help with DNS, please!

[bert]

I moved the master DNS server to another Cpanel server earlier today. I have done this about 4 times now in the past year, however this time, the new slave server (which used to be the master) is not getting the proper transfer. It is getting the named.conf file and it does not show anything wrong, but the files inside /var/named are not being transferred.

Any suggestions are very much appreciated. The IP address change has still not propagated completely, so I need this server still to act as master for the outside world.

 

[bert]

Sh***t. I deleted my named.local and named.ca files. Can someone also please post those files here? Thanks very much.

/var/named/named.local
/var/named/named.ca

 

[bert]

Nevermind. I fixed it. The transfer did not work because the file named.ca was missing therefore named could not start.

Thanks.

 

[bert]

OK, still the same problem.

bash: /scripts/dnstranfer: No such file or directory
[email protected] [~]# /scripts/dnstransfer
Rebuilding DNS Zones List from master server .....
stdin: is not a tty
named.conf 100% |**********************************************************************************************************| 72790 00:00
ndc: reload command successful
Rebuild Complete


But, nothing inside /var/named gets transferred unless I explicitly restart named:
/etc/rc.d/init.d/named stop
/etc/rc./dinit.d/named start

The command above does the trick, but just the dnstransfer script with ndc reload does not transfer anything. /etc/named.conf on the other hand is being transferred without problems.

Nick, please ??

 

[jumpdomain]

Hello,

Are you trying to transfer between a bind 8 server (RH 6.2) and a bind 9 server (RH 7.2)?

 

[bert]

Nope, not at all. Both, primary and secondary run on 7.2 with bind 9.

It, for some reason does not transfer the zones when using /scripts/dnstransfer. Only transfers the named.conf file.

 

[jumpdomain]

Bert,

Yes, this is what the script does, it only updates the named.conf file on the master server to make the entries slaves and then moves over the named.conf file. Bind recreates the actual zone files using the named.conf file that was moved and the settings on the master name server. That is a zone transfer.

 

[bert]

jumpdomain,

The files in /var/named are not getting transferred or recreated by named on the secondary DNS. This is really what the problem is.

 

[jumpdomain]

Bert,

We always do a:
/etc/rc.d/init.d/named stop
/etc/rc.d/init.d/named start

To transfer over the new zones after the named.conf is transferred as that does it instantly... I do not know if a ndc reload will eventually bring them over. How long did you wait to see if they were moved over? I know an ndc reload takes some time to update an existing zone on the slave server when you update the serial number.

 

[bert]

Well, it is good to know that you restart named to get it done. I am used to just doing /scripts/dnstransfer and seeing the files going into the /var/named directory.

I could literally remove all the files inside of /var/named , then do a dnstransfer and could see all the files again in /var/named in about 10 minutes. We don't have more than about 2000 zone files. Now, we have to restart name, which is not a big deal, but don't know why the difference.

I guess I will stop wondering and will live with it