I am using the configuration options shown in that faq, but I am running
into a problem when my master server send a NOTIFY to the slaves. I have a
zone with the same name in all four views. When the master send a notify
for that zone to the slaves, the slave query the master to see what the
serial is. When they do this they are sending the query through their
default IP and not the IP I have set as the transfer source for that
domain. Since they are using their default IP they are getting a serial of
the same zone in a different view and not requesting the updated zone file
from the master. The slave servers are getting the new zone file when doing
a refresh call to the master server, since they are using the
transfer-source for that operation. Is there anything I can do besides
lowering the refresh interval to 5 minutes?
Mark
On Jul 28, 2009 9:35am, "Dixon, Justin" <justin.di...@bbandt.com> wrote:
>I have 3 servers set up
using bind 9.2.4-30. I am using 3 different views and have an IP address
on each
slave for each view so that the slaves >are directed to the correct zone
files when contacting
the master to refresh a zone, etc. I have run into a problem with the
slaves
not respecting >the
ip address using transfer-source in the zone definitions. The slave uses
the
transfer-source IP when retrieving the zone file for the first time >from
the master &
when refreshing the zone file. However when a notify is received by the
slave
from the master, the slave tries to retrieve the >new zone file using the
slave servers
default IP. The slave is not directed to the correct view on the master
causing
the slave to not receive the >updated
zone file. Does anyone have an idea on why this would happen?
>
>Thanks,
>
>Mark
See https://www.isc.org/node/282
Justin
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
