On Tue, Dec 18, 2007 at 11:50:51PM +1000, Mark Constable wrote:
> On Tuesday 18 December 2007 22:38:03 you wrote:
> > it may or may not help, but check
> > query-source address xx port 53;
> > notify-source xx;
> > transfer-source xx;
>
> Thanks for that hint. I tried both
On Tuesday 18 December 2007 22:38:03 you wrote:
> it may or may not help, but check
> query-source address xx port 53;
> notify-source xx;
> transfer-source xx;
Thanks for that hint. I tried both of these on the master
ns1.domain.net bind9 server...
query-source address
I forgot to mention the version of pdns was 2.9.20 but I
just compiled a 2.9.21 version that includes the sqlite3
backend. And these are the domain.net records...
INSERT INTO "domains" VALUES(7, 'domain.net.', NULL, NULL, 'NATIVE', NULL,
NULL);
INSERT INTO "records" VALUES(63, 6, '4.238.xx.xx.in-
Hi Mark,
I use pdns as a primary as well but this shouldn't matter for the slave
as they have a similar configuration.
What I need to do to allow automatic creation of slave zones is add an
entry into the supermasters table:
ip nameserveraccount
xx.xx.238.2 ns1.do
My pdns is a slave for a remote bind9 master on a Debian
lenny server and it's source address is different to what
the ns1.domain.net nameserver IP. I added "query-source
xx.xx.238.2;" to the remote nameserver setting (not sure
if that would help anyway) but the local pdns slave still
provides this
