Bind slave zone not updating

&1 | sed -n '/transfer/p;/Version/p'=20 retransfer zone [class [view Retransfer a single zone without checking serial number.Version: 9.3.0s20021115 - --=20 M=E5ns Nilsson Systems Specialist 46 KTHNOC MN1334-RIPE We're sysadmins. This legacy document is here only to insure incoming links continue to work. Once configured, it will create slave zones on other servers and configure them to automatically update when changes are made on your Virtualmin server.

||

&1 | sed -n '/transfer/p;/Version/p'=20 retransfer zone [class [view]] Retransfer a single zone without checking serial number.

]]

How can I get this BIND slave to actually refresh its zones off the master without wiping the zone files and start/stopping named in cron? -- Matt config files (with some edits) named.I've tried converting from BIND9 to Power DNS configured as a slave with opendbx/sqlite3, and I'm still not getting any love. The original config was pointing to a BIND master, all I did was do a vi search/replace in its to change the BIND master IP to the Power DNS master IP.

How can I trick the master into not sending SERVFAIL for this demonstration setup? The errors I'm getting in syslog on the powerdns master are: Feb 29 powerdns-dev pdns[13444]: [ID 702911 daemon.warning] Not authoritative for 'hfnmag.com', sending servfail to 10.202.108.22 On the slave side: 29-Feb-2008 .680 general: info: zone hfnmag.com/IN: refresh: unexpected rcode (SERVFAIL) from master 10.202.108.20#53 (source 0.0.0.0#0) I know Power DNS doesn't set authoritative flags, and this box is an eval (dev) server at this point so nobody in whois will ever know about it.

We'll go through the steps here in case you weren't the one to set up those files or if you'd just like a checklist to follow.

Make these changes to your The primary master name server will load the new zone data.

Something is always changing on your network -- new workstations arrive, you finally retire or sell the relic, or you move a host to a different network. First we'll discuss how to make the changes manually. Actually, we recommend that you use a tool to create the zone data files -- we were kidding about that wimp stuff, okay?

Each change means that zone data files must be modified. Or at least use a tool to increment the serial number for you.

Specifically problems are encountered with updating slave zone database files, creating DDNS journal files and updating master zones from journals.

It also manifests itself as named being unable to create custom log files.

If Power DNS is not authoritative, it will send out a servfail - this is intended behaviour.

Tags: , ,