What is the *proper* way to do forwarding? I have about 80 zones, but
70 of them forward to other zones. Like seacoastsynergy.com and
seacoastsynergy.net. First I had it set up in the nsd.zones file so
that both zones point to the same db file, but that caused a problem.
On my secondary server, I am using named-xfer to do the zone transfers.
When I set up more than one of the zones to point to the same db file,
the secondary server wasn't able to update its zones. It would check
the serial, determine what needed to be updated, download the data, and
error on the rebuild. I checked for errors and couldn't find any. So I
copied the file straight from the primary to the secondary and did a
rebuild. That worked flawlessly. So something in the named-xfer messed
everything up. It only errors for the zones that share a db.
I have attached text files of the zones before and after the transfer.
Thanks, Dave
(attachments)
zone file after.txt (886 Bytes)
zone file before.txt (871 Bytes)
David Coursey wrote:
What is the *proper* way to do forwarding? I have about 80 zones, but
70 of them forward to other zones. Like seacoastsynergy.com and
seacoastsynergy.net. First I had it set up in the nsd.zones file so
that both zones point to the same db file, but that caused a problem.
On my secondary server, I am using named-xfer to do the zone transfers.
When I set up more than one of the zones to point to the same db file,
the secondary server wasn't able to update its zones. It would check
the serial, determine what needed to be updated, download the data, and
error on the rebuild. I checked for errors and couldn't find any. So I
copied the file straight from the primary to the secondary and did a
rebuild. That worked flawlessly. So something in the named-xfer messed
everything up. It only errors for the zones that share a db.
I'm not sure I understand you correctly, but I think you mean you have an NSD zone configuration file with something like this:
zone seacoastsynergy.com. seacoastsynergy.zone
zone seacoastsynergy.net. seacoastsynergy.zone
And in the "seacoastsynergy.zone" file you avoid using absolute domain names so the correct origin gets appended automatically.
Unfortunately, that doesn't work with an AXFR. When doing an AXFR, the absolute domain names are always specified. In this case you will start getting errors about out-of-zone data on the secondaries. So on the secondaries you should specify something like:
zone seacoastsynergy.com. seacoastsynergy.com.zone
zone seacoastsynergy.net. seacoastsynergy.net.zone
in your zone configuration file.
I hope this makes sense...
Erik