Master/slave DNS in PSA8

[Highland]

I have tried and tried to figure out why my two servers will not mirror their respective DNS settings.

Server #1 FC4/PSA 8.0.1
ns.domain.com

Server #2 Centos 4.3/PSA 8.0.1
ns2.domain.com

I have #2 set up as slave DNS and have added each server to each other's common ACL. Still I cannot make them show the DNS for the other. Glue records are correct btw.

Any help is appreciated

 

[Who-m3]

Please check your settings to verify that...

Server 1 is set to Master, with NS2 listed in it's records as a record (i.e. NS2 is listed as a nameserver on the records).

Server 2 is set to slave with Server 1's IP set as Master. Please veirfy that the IP Server 1 is sending the named records from is set as the Master (you can verify this through a tail of your /var/log/messages when the transfer attempts if it fails). Please note: when set to slave on server 2, you can NOT modify the DNS settings on Server 2 directly. This is the "slave" mentality.

As long as you're set in the ACL, with the Master/Server settings properly configured, everything should work properly unless there are firewall issues involved. If the above settings are in place, check your firewall settings for TCP and UDP port 53 to verify you're not blocking either. Both do need to be open, as bind uses them for the record transfer.

 

[Highland]

Server 1 is set to Master, with NS2 listed in it's records as a record (i.e. NS2 is listed as a nameserver on the records).

Server #1 is master. ns2.domain.com has an A record pointing to server #2's main IP.

Server 2 is set to slave with Server 1's IP set as Master. Please veirfy that the IP Server 1 is sending the named records from is set as the Master (you can verify this through a tail of your /var/log/messages when the transfer attempts if it fails). Please note: when set to slave on server 2, you can NOT modify the DNS settings on Server 2 directly. This is the "slave" mentality.

ACL is set for both. Port 53 is open for TCP and UDP (incoming and outbound traffic). I have tried forcing updates but to no avail. Only domain.com is shown by both servers. Here's the relevant portion from /var/log/messages

Aug 3 11:40:39 named[16217]: client 10.10.10.10#34452: transfer of 'domain.com/IN': AXFR-style IXFR started
Aug 3 11:40:39 named[16217]: client 10.10.10.10#34452: transfer of 'domain.com/IN': AXFR-style IXFR ended
Aug 3 11:40:40 named[16217]: client 10.10.10.10#33548: received notify for zone 'domain.com'

 

[Who-m3]

dig @ns2.domain.com <record that should exist on ns2>

see if that pulls up. Acording to your /var/log/messages, the transfer is completing. /var/log/messages isn't going to outline the entire transfer, but merely that the transfer has occurred.

However, please verify step 1 of the above post that you have an NS record for NS2, not just the A record for NS2 for the domain. Having the A line for the NS2 doesn't mean anything without the NS itself being configured.

 

[Highland]

Dig returns the correct IP (no big shock as there's a glue record). I also have NS records for all of my nameservers.

Let's try this. Run a dnsreport on highlandtaylor.com and then umbrellasource.com. You'll notice highlandtaylor.com returns no errors while umbrellasource.com fails to show up on ns2 (lame server error). The same errors occur on the server ns2 resides on as none of its DNS records are present.

 

[Who-m3]

Acording to the information you've posted to me, and the reports I've obtained through DNSReports and DNSStuff, it seems as though umbrellasource.com is not listed as a domain being hosted on Server2 (NS2).

Although HighlandTaylor.Com is fully operational (both NS's are working properly for it), I'd have to recommend checking the second server to verify you have the second domain (umbrellasource.com) listed. Each domain you want to have a second nameserver for has to be added (either manually or through plesk) to be recognized. There are easy ways to handle this (such as the control panel), and there are other ways to handle this (some that wont effect your domain limits, if you're so limited).

As you have stated, it does appear that your NS2 is not recognizing that it should be serving records for the second domain. Check /etc/named.conf to see if that domain is in fact listed as well. If it is not, that's going to be the first problem. If it's listed on the Control Panel, but not in the /etc/named.conf, you'll need to make a change to the DNS settings in the Control Panel to force the named to reload. There is a command line utility to force the update, but I cannot remember it at this time. For that, it's easier to just do a quick modification to make the reload occur...

Hope that gets you to where you wanna be...