Usr/sbin/rndc Status Failed Warning Key File

To the best of my knoweledge, bind9 or or either centos (either or) whatever seems to like running in CHROOT jail. If you are not farmiliar with this its a pretty simple concept. It actually runs out of /var/named/chroot/var/named/.My point is when I install bind on any 'newer' system like bind9 on centos 5+ or the like as I was trying to elaborate above, I use this:code# yum install bind-chroot/codeand it works like a charm every time for me, using centos 5.2. Of course, then, named.conf is also then no longer located in /etc/named.conf either. In fact, it doesn't even create one.

Usr/sbin/rndc Status Failed Warning Key File Software

So I would really suggest taking it one step at a time and getting your local view, then internal view, then external view working all tested first before moving to the next step. Looking at the logs, trouble shooting and what not to help out what might be the problem. I would be happy to send you a copy of my named.conf.Be warned though, there has been much improvements. I have seen posts where a senior member swore to the death that you HAVE to add your ISP dns servers to your /etc/resolv.conf or it won't work, but if you set it up correctly, then the localhost authoritive nameserver for your domain should then go up and out to find the answer (i.e. Ping yahoo.com) and come back fine.I wanted to throw that bit in there after seeing that post as you should only have your domain i.e.codedomain yourdomain.comnameserver 127.0.0.1/codeBut bind/named whatever will not let you out (resolv any other hosts like google or yahoo or ANYTHING) if you don't have your named.conf setup correctly. Mine has finally got working like a charm.

BTW, i stated it doesn't run in /etc/named.conf when you install how I stated, If you runcode# service named start/codeIt should give you an error about where it cannot find the named.conf, and then you will know exactly where its looking for it, of course. Post be back if you need help. I have spent quite a bit of time with DNS servers.