-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Charles Curley wrote: >> I'd take a stab at SELinux being the cause. Do you have that >> running in Enforcing mode on either box by chance? > > Nope, selinux is disabled on both boxes. Damn. So much for the easy scapegoat. Okay, you made me curious enough to google a little so I can ask you better questions and make other suggestions... (Bear in ind though that it's been a while since I setup BIND to do this so I'm rusty.) You probably want have the secondary server setup to use the slaves subdirectory, which will be writable by the named daemon. Change your secondary to: file "slaves/localdomain"; That's one solution I found for someone having the same problem and it makes sense, as right now your secondary is trying to write the localdomain file to /var/named, which it won't have permission to write to by default. - -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp ====================================================================== Relying on government to protect your privacy is like asking a peeping tom to install your window blinds. -- John Barlow, co-founder of EFF -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iG0EARECAC0FAkSp5YAmGGh0dHA6Ly93d3cucG9ib3guY29tL350bXovcGdwL3Rt ei5hc2MACgkQuv+09NZUB1qS8wCg5RN+2Pbh0SONNWSLKEhPlyEeZ9IAmwcID4fl bofAX0zce2ch387n3WH0 =K8nj -----END PGP SIGNATURE-----