That's exactly what I was seeing when I tried that: "rndc: 'freeze' failed: not found".
You folks have all been so helpful. Like one of the other posters said, we've done non-dynamic DNS for so long here (years and years) the dynamic DNS, especially when combined with a mainly Windows environment has been a little bit like black magic. And, we're being forced to implement over such a short period of time. It's been a little much to take it all in. ------------------------------------ Joseph A. Borgia, Jr. Sr. UNIX/SAN Engineer Team Rome IT - Rome Research Corporation U.S. Air Force Research Laboratory/Rome Research Site/RIOS COMM: 315-330-3952 DSN: 587-3952 FAX: 315-330-8258 -----Original Message----- From: Chris Thompson [mailto:[email protected]] On Behalf Of Chris Thompson Sent: Friday, June 19, 2009 10:25 AM To: Borgia, Joe A CTR USAF AFMC AFRL/RIOS Cc: Bind Users Mailing List Subject: RE: Dynamic DNS and Slave Servers On Jun 19 2009, Borgia, Joe A CTR USAF AFMC AFRL/RIOS wrote: >Should running a rndc freeze and thaw on the slave server also push the data >from the .jnl files directly to the tables as they do on the master server? > >For some weird reason, running a rndc freeze and thaw on the slave runs >successfully, but it does not push the updates to the zone tables there, and >the .jnl files still exist after it. > >This is unexpected behavior. Not really. Freezing is only meaningful for zones of type master. If you use "rndc freeze [zonename]" and the zone is of type slave, you will get an error message "rndc: 'freeze' failed: not found" (by which it means, not found among the zones of type master). "rndc freeze" without a zone name means "freeze all zones of type master", and so it is always going to "run successfully", even if there aren't any. (I don't actually much like syntax like this, when leaving out an argument has such a wide-ranging effect that might not have been intended. "rndc freezeall", say, would have been a better idea.) -- Chris Thompson Email: [email protected]
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ bind-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/bind-users
