Hi,
I have been using and managing bind9 servers here for awhile,
and recently we deployed NAT district wide. We have one single public
master, and 3 slaves at various points in the WAN. We have two views,
and internal view (10/8) and an external view (everything else), a
PIX firewall handles NAT, no internal devices have public addresses
on their interfaces. I was wanting to open up one of the slaves for
public use resolving our domains incase of master failure.
The problem is that the slave is publishing our private view
(chs.cusd.claremont.edu IN A 10.2.2.2) instead of our public view
(chs.cusd.claremont.edu IN A 134.173.108.2) to the external internet.
The only idea I am having as to why this happens is because the slave
is requesting the zone transfer for my external zone from the
internal view. Any ideas? That thread on DNS failover solutions
looked promising, but I was wondering if there was a way to get bind
to AXFR/IXFR the proper view in named.conf?
Our master is Solaris 7, slaves are all FreeBSD 5.1
Thank you,
Kelly
--
Kelly Kane
Claremont Unified School District
|
