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 nameserver account xx.xx.238.2 ns1.domain.net <an account name> (I use "internal" as accountname) In my experience the ns1.domain.net needs to present as an NS-rr for the domain to be transferred. Good luck. Ton Mark Constable schreef: > 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 error. > > Dec 18 04:51:14 us pdns[32360]: Received NOTIFY > for domain.net from xx.xx.238.7 which is not a master > > ns1.domain.net = xx.xx.238.2 > domain.net real IP = xx.xx.238.7 > pdns slave IP = xx.xx.153.103 > > Any suggestions how to work around this ? > > allow-axfr-ips=xx.xx.238.7 xx.xx.132.7 xx.xx.248.2 > allow-recursion=127.0.0.1 > config-dir=/etc/powerdns > daemon=yes > disable-axfr=no > gsqlite-database=/home/a/dns.sqlite > guardian=yes > include=/etc/powerdns/pdns.d > launch=gsqlite > lazy-recursion=yes > local-address=xx.xx.153.103 > local-port=53 > log-dns-details=yes > log-failed-updates=yes > logfile=/var/log/pdns.log > loglevel=99 > module-dir=/usr/lib/powerdns > query-logging=yes > setgid=pdns > setuid=pdns > slave-cycle-interval=60 > slave=yes > socket-dir=/var/run > use-logfile=yes > version-string=powerdns > webserver-address=xx.xx.153.103 > webserver-password=xxxxx > webserver-port=9999 > webserver=yes > wildcards=yes > > --markc > _______________________________________________ > Pdns-users mailing list > [email protected] > http://mailman.powerdns.com/mailman/listinfo/pdns-users > _______________________________________________ Pdns-users mailing list [email protected] http://mailman.powerdns.com/mailman/listinfo/pdns-users
