I am getting on one of my slaves (69.25.129.117) yet on the other I get
the zone to come across from the master. Just a quirk here is that the
.117 slave has to be recycled before the zone comes across yet the .118
comes across when the master is recycle and a change has occurred in one
of the zones. By the way until this zone I have not had problems with
zones coming across to either slave although I have had to do a recycle
to the .117 to get them there.
Anyone know why I am getting this "not authoritative" message and no
zone file on .118 all of a sudden?
Thanks,
Steve
This is the log message in the 69.25.129.119 Master
client 69.25.129.117#1305: transfer of 'manzanitavacation.com/IN': AXFR
started
client 69.25.129.117#1305: transfer of 'manzanitavacation.com/IN': AXFR
ended
This is the log message in the 69.25.129.118 slave
client 69.25.129.117#1304: received notify for zone
'manzanitavacation.com': not authoritative
This is the log message in the 69.25.129.117 slave
zone manzanitavacation.com/IN: Transfer started.
transfer of 'manzanitavacation.com/IN' from 69.25.129.119#53: connected
using 69.25.129.117#1305
zone manzanitavacation.com/IN: transferred serial 2008111901
transfer of 'manzanitavacation.com/IN' from 69.25.129.119#53: Transfer
completed: 1 messages, 8 records, 251 bytes, 0.109 secs (2302 bytes/sec)
zone manzanitavacation.com/IN: sending notifies (serial 2008111901)
=[1]== named.conf for 69.25.129.117 Slave =========
options {
directory "C:\WINDOWS\system32\dns\etc\named";
pid-file "C:\WINDOWS\system32\dns\etc\named\run\named.pid";
dump-file
"C:\WINDOWS\system32\dns\etc\named\dump\named_dump.db";
statistics-file
"C:\WINDOWS\system32\dns\etc\named\stats\named.stats";
zone-statistics yes;
forwarders { 63.251.161.33; 216.231.41.2; };
allow-query {any;};
recursion yes;
// allow-recursion {69.25.129.119;};
allow-transfer {69.25.129.119;};
listen-on-v6 { any; };
};
// log to named\log\named.log events from info UP in severity (no debug)
// defaults to use 3 files in rotation
// failure messages up to this point are in the event log
logging{
channel my_log{
file
"C:\WINDOWS\system32\dns\etc\named\log\named.log" versions 3 size 250k;
severity info;
};
category default{
my_log;
};
};
#
zone manzanitavacation.com. in {
type slave;
file
"c:\windows\system32\dns\etc\named\zones\db.manzanitavacation.com.zone";
masters { 69.25.129.119; };
allow-notify {69.25.129.117;69.25.129.118; };
};
=[1]=========================================
=[2]== named.conf for 69.25.129.119 Master =========
options {
directory "C:\WINDOWS\system32\dns\etc";
dump-file "C:\WINDOWS\system32\dns\etc\named\dump\nameddump.db";
statistics-file
"C:\WINDOWS\system32\dns\etc\named\stats\named.stats";
pid-file "C:\WINDOWS\system32\dns\etc\named\run\named.pid";
recursion yes;
zone-statistics yes;
forwarders { 63.251.161.33 ; 63.251.161.1; };
#forward first;
listen-on-v6 { any; };
dnssec-enable yes;
};
key "rndc-key" { algorithm hmac-md5; secret ??????????????????????"; };
controls {
inet 127.0.0.1 port 953 allow { localhost; } keys {
"rndc-key"; };
};
logging{
channel my_log{
file
"C:\WINDOWS\system32\dns\etc\named\log\named.log" versions 3 size 250k;
severity info;
};
category default{
my_log;
};
};
#
zone manzanitavacation.com. in {
type master;
file
"c:\windows\system32\dns\etc\named\zones\manzanitavacation.com.zone";
};
=[3]== named.conf for 69.25.129.118 Slave ======================
options {
directory "C:\WINDOWS\system32\dns\etc\named";
pid-file "C:\WINDOWS\system32\dns\etc\named\run\named.pid";
dump-file
"C:\WINDOWS\system32\dns\etc\named\dump\named_dump.db";
statistics-file
"C:\WINDOWS\system32\dns\etc\named\stats\named.stats";
zone-statistics yes;
forwarders { 63.251.161.33; 216.231.41.2; };
allow-query {any;};
recursion yes;
// allow-recursion {69.25.129.119;};
allow-transfer {69.25.129.119;};
listen-on-v6 { any; };
};
// log to named\log\named.log events from info UP in severity (no debug)
// defaults to use 3 files in rotation
// failure messages up to this point are in the event log
logging{
channel my_log{
file
"C:\WINDOWS\system32\dns\etc\named\log\named.log" versions 3 size 250k;
severity info;
};
category default{
my_log;
};
};
#
zone manzanitavacation.com. in {
type slave;
file
"c:\windows\system32\dns\etc\named\zones\db.manzanitavacation.com.zone";
masters { 69.25.129.119; };
allow-notify {69.25.129.117;69.25.129.118; };
};
=[3]=======================================
=== manzanitavacation.com zone file on master =====
$ORIGIN manzanitavacation.com.
$TTL 900
@ IN SOA ns1.escapia.com. nsadmin.escapia.com. (
2008111901 ; serial
10800 ; refresh
3600 ; retry
86400 ; expire
86400 ; minimum
)
manzanitavacation.com. 900 IN NS ns1.escapia.com.
manzanitavacation.com. 900 IN NS ns2.escapia.com.
manzanitavacation.com. 900 IN NS
pdns2.ultradns.net.
manzanitavacation.com. 900 IN NS
pdns1.ultradns.net.
manzanitavacation.com. 900 IN A 69.25.129.65
www.manzanitavacation.com. 900 IN A
69.25.129.65
===========================================
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
