our NS was running many thousands of zones..primary NS.
ony guy mistakenly ran /scripts/makesecondary on this server which turned everything in named.conf into "slave" zones.. few hrs later we see the name server was down.
i've fixed named.conf so all Zone entries are back to master
i've restarted named and now after few hours of reloading.... went thru different phases (Serial , notify, received notify) ...now these msgs in /var/log/messages seem to stop and rndc status reports itself as "up and running"...
however, any query to it timeouts as ;
;; connection timed out; no servers could be reached
i've turned rndc querylog on and its bit weird cos it seem to log the queries into /var/log/messages.... but when i query it from various places via nslookup it never respond.
theres apf/iptables firewall but have disabled that and had no luck.
additional info / some possibilities:
i didnt change rndckey when i was restoring named.conf... maybe changeing it will help (/scipts/fixndc), just want to avoid any further restarts if we can.
IF YOU HAVE ANY IDEA WHAT IS GOING ON OR HAVE BIG DNS EXPERIENCE, PLEASE PM ME YOUR IM'S, PREFERABLE ICQ / AIM AND I'LL MSG U IN MINUTES.
AssistanZ - Beyond Boundaries... Cloudstack Consultancy / 24x7 Web Hosting Support / 24x7 Server Management / Infrastructure Management Services Web & Mobile Apps Development / Web Designing Services / Php, Grails, Java Development