file "secondaries/db.usptoenews";
masters { 10.240.6.50; };
};
From: Lear, Karen (Evolver)
Sent: Wednesday, March 31, 2010 7:25 AM
To: Sten Carlsen; bind-users@lists.isc.org
Subject: RE: Zone transfer issues on new domain
I added it to the named.co
t: Wednesday, March 31, 2010 7:25 AM
> To: Sten Carlsen; bind-users@lists.isc.org
> 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?
> __
010 7:25 AM
To: Sten Carlsen; bind-users@lists.isc.org
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: bind-users-bounces+karen.lea
Sten
Carlsen [st...@s-carlsen.dk]
Sent: Tuesday, March 30, 2010 9:26 PM
To: bind-users@lists.isc.org
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
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
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 '
6 matches
Mail list logo