Bind Bad transfer

Bind bad zone transfer request Re: bind9 returns "bad zone transfer request domain.com/IN: non-authoritative zone (NOTAUTH)" Resolution: stop, restart all bind instances 03/09/2006 This is just a quick note about one possible reason you may receive this error. If you create a new zone, then attempt to transfer to other machines, and get an error like this in the log - check that you do not have more than one instance of bind (named) running. In my case I somehow managed to end up with 2 instances running - so every time I re-applied my changes one instance accepted the changes but the other did not. The slaves were apparently contacting the one that did not have the new zone. Use your appropriate version of ps to get a list of processes matching named. For me, this seems to work: ps aexg | grep named Better yet, if you have Webmin, use its "running processes" module and search the page for the word "named". If you find this helpful, please take a moment to drop me a message using the form below. Good luck!

Comments

Date :  9/7/2010 6:28:00 AM Name :  Dragon Comments :  Great! Four years later this helped me! I would have never thought of checking for two copies of bind running, and on a production machine one usually uses ''restart'' for the bind process. And, of course, the second copy wouldn''t even stop with ''stop'' and must be killed manually :) Thanks!

Date :  1/18/2010 4:01:25 AM Name :  Beda Comments :  It w''d be better if u gave these in a more simplified manner than this. But still has been of help. Thanks a lot.

Date :  4/4/2008 12:49:46 AM Name :  skirmisher Comments :  i wish i had found this 5 hours ago! thanks.

Date :  1/16/2008 10:51:43 AM Name :  Drew Comments :  thanks, I ran into this myself and this saved me some time.

Date :  9/15/2007 6:41:43 AM Name :  ron Comments :  thanks a lot, sometimes solutions can be so easy ;) just wish i had found this 1 hr ago ;) regards ron