IN the past I've had separate internal and external, master and slave servers.
Moving from AIX to Lnx/VMware, I'm doing one master (with internal and external
views) and one slave. When the slave's copy ages out, it seems to successfully
pulls new zone files from the master.
But when I update the master (either the external or internal zone files), while
it appears to do a notify, slave's serno doesn't change....the push isn't working
I've been struggling with this off and on the last week or two and have tried
lots of thing. Currently, the named.conf internal views look like this :
MASTER (10.5.0.5) ========================================
view "internal" {
match-clients { "internalnets"; };
recursion yes;
allow-query { "internalnets"; };
transfer-format many-answers;
notify-source 10.5.0.5;
allow-transfer { 10.5.0.6; };
also-notify { 10.5.0.6; };
notify explicit;
zone "bard.edu" {
type master;
file "internal/bard/bard.db";
};
SLAVE (10.5.0.6) ========================================
view "internal" {
match-clients { "internalnets"; };
recursion yes;
allow-query { "internalnets"; };
transfer-source 10.5.0.5;
zone "bard.edu" {
type slave;
masters { 10.5.0.5; };
transfer-source 10.5.0.5;
file "internal/bard/bard.db";
};
I've turned logging on to debug 1 and see these log entries when I update the
serno on the master to 2011011306 and refresh:
MASTER (10.5.0.5) ========================================
Jan 13 12:36:50 nsi1 named[21007]: zone bard.edu/IN/internal: starting load
Jan 13 12:36:50 nsi1 named[21007]: zone bard.edu/IN/internal: journal
rollforward completed successf
ully: no journal
Jan 13 12:36:50 nsi1 named[21007]: zone bard.edu/IN/internal: loaded
Jan 13 12:36:50 nsi1 named[21007]: zone bard.edu/IN/internal: loaded serial
2011011306
Jan 13 12:36:50 nsi1 named[21007]: zone authors.bind/CH: starting load
Jan 13 12:36:50 nsi1 named[21007]: zone authors.bind/CH: loaded
Jan 13 12:36:50 nsi1 named[21007]: zone hostname.bind/CH: starting load
Jan 13 12:36:50 nsi1 named[21007]: zone hostname.bind/CH: loaded
Jan 13 12:36:50 nsi1 named[21007]: zone version.bind/CH: starting load
Jan 13 12:36:50 nsi1 named[21007]: zone version.bind/CH: loaded
Jan 13 12:36:50 nsi1 named[21007]: zone id.server/CH: starting load
Jan 13 12:36:50 nsi1 named[21007]: zone id.server/CH: loaded
Jan 13 12:36:50 nsi1 named[21007]: dns_zone_maintenance: zone
bard.edu/IN/internal: enter
Jan 13 12:36:51 nsi1 named[21007]: zone_timer: zone bard.edu/IN/internal: enter
Jan 13 12:36:51 nsi1 named[21007]: zone_maintenance: zone bard.edu/IN/internal:
enter
Jan 13 12:36:51 nsi1 named[21007]: zone bard.edu/IN/internal: sending notifies
(serial 2011011306)
Jan 13 12:37:37 nsi1 named[21007]: zone bard.edu/IN/internal: notify to
10.5.0.6#53: retries exceeded
Over on the Slave the serno doesn't change from 2011011200 even when I do a
refresh there too.......
There is nothing in the slave's log for the timestamp that the retries were
exceeded
SLAVE (10.5.0.6) ========================================
Jan 13 12:42:41 nsi2 named[24441]: zone bard.edu/IN/external: starting load
Jan 13 12:42:42 nsi2 named[24441]: zone bard.edu/IN/external: journal rollforwar
d completed successfully: no journal
Jan 13 12:42:42 nsi2 named[24441]: zone bard.edu/IN/external: loaded
Jan 13 12:42:42 nsi2 named[24441]: zone bard.edu/IN/external: loaded serial
2011011200
Jan 13 12:42:42 nsi2 named[24441]: dns_zone_maintenance: zone 0.0.127.in-addr.ar
pa/IN/internal: enter
Jan 13 12:42:42 nsi2 named[24441]: dns_zone_maintenance: zone
bard.edu/IN/external: enter
......
Jan 13 12:42:41 nsi2 named[24441]: zone bard.edu/IN/internal: starting load
Jan 13 12:42:41 nsi2 named[24441]: zone bard.edu/IN/internal: journal rollforwar
d completed successfully: no journal
Jan 13 12:42:41 nsi2 named[24441]: zone bard.edu/IN/internal: loaded
Jan 13 12:42:41 nsi2 named[24441]: zone bard.edu/IN/internal: loaded serial
2011011000
.....
Jan 13 12:42:42 nsi2 named[24441]: zone authors.bind/CH: starting load
Jan 13 12:42:42 nsi2 named[24441]: zone authors.bind/CH: loaded
Jan 13 12:42:42 nsi2 named[24441]: zone hostname.bind/CH: starting load
Jan 13 12:42:42 nsi2 named[24441]: zone hostname.bind/CH: loaded
Jan 13 12:42:42 nsi2 named[24441]: zone version.bind/CH: starting load
Jan 13 12:42:42 nsi2 named[24441]: zone version.bind/CH: loaded
Jan 13 12:42:42 nsi2 named[24441]: zone id.server/CH: starting load
Jan 13 12:42:42 nsi2 named[24441]: zone id.server/CH: loaded
Jan 13 12:42:42 nsi2 named[24441]: dns_zone_maintenance: zone
bard.edu/IN/internal: enter
......
Jan 13 12:42:42 nsi2 named[24441]: zone_timer: zone bard.edu/IN/internal: enter
Jan 13 12:42:42 nsi2 named[24441]: zone_maintenance: zone bard.edu/IN/internal:
enter
Suggestions? Of course this single internal/external server has a NIC for each
view. It does work to resolve queries so traffic coming in on the NIC, goes
out on that same NIC.
--
"Where's the kaboom? There was supposed to be an Earth-shattering kaboom!"
- Marvin the Martian
Stewart Dean, Unix System Admin, Bard College, New York 12504 sd...@bard.edu
voice: 845-758-7475
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
