To clarify, I added this to the named.conf on the slave:
};
zone "usptoenews.gov" {
type slave;
file "secondaries/db.usptoenews";
masters { 10.240.6.50; };
};
________________________________
From: Lear, Karen (Evolver)
Sent: Wednesday, March 31, 2010 7:25 AM
To: Sten Carlsen; [email protected]
Subject: RE: Zone transfer issues on new domain
I added it to the named.conf on the slave. Shouldn't it create its own
db.usptoenews file under the secondaries directory?
________________________________
From: [email protected]
[[email protected]] On Behalf Of Sten
Carlsen [[email protected]]
Sent: Tuesday, March 30, 2010 9:26 PM
To: [email protected]
Subject: Re: Zone transfer issues on new domain
Did you add it to the slaves configuration? It does not get automagically
added; so the slave gets a notify on a zone it can not serve as it is not in
its config.
On 31/03/10 2:14, Lear, Karen (Evolver) wrote:
Can you tell me why I’m getting the message below on my slave server after
adding a master zone on the master server for usptoenews.gov:
[kl...@dns2 logs]$ grep enews activity.log
30-Mar-2010 17:17:45.484 notify: notice: client 10.240.6.50#10738: received
notify for zone 'usptoenews.gov': TSIG 'ns1-ns2.uspto.gov': not authoritative
30-Mar-2010 17:22:47.335 notify: notice: client 10.240.6.50#62593: received
notify for zone 'usptoenews.gov': TSIG 'ns1-ns2.uspto.gov': not authoritative
email: [email protected]<mailto:[email protected]>
_______________________________________________
bind-users mailing list
[email protected]<mailto:[email protected]>
https://lists.isc.org/mailman/listinfo/bind-users
--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
_______________________________________________
bind-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/bind-users
