Redhat 7.2 DNS server times out client requests, but appears to be running fine....

Using a Redhat 7.2 Linux box running bind 9.2.1 that I used to run a secondary DNS server on, but it is no longer responding to queries, although I see log file information recording that the queries were made.  I always get "connection timed out; no servers could be reached" or "DNS required timed out" on the client computer using either nslookup, dig, or host.  I'm trying queries from localhost, and a computer on the same network, so a firewall should not be an issue.

Any ideas what I am doing wrong?

Here is my /etc/resolve.conf

nameserver 0.0.0.0

Here is my /etc/named.conf

options {
        directory "/var/named";
        /*
         * If there is a firewall between you and nameservers you want
         * to talk to, you might need to uncomment the query-source
         * directive below.  Previous versions of BIND always asked
         * questions using port 53, but BIND 8.1 uses an unprivileged
         * port by default.
         */
        // query-source address * port 53;
};

//
// a caching only nameserver config
//
controls {
        inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};

logging {
        channel namedlog {
                file "/var/log/named.log" versions 5 size 2m;
                print-time yes;
                print-category yes;
        };
        category "default" { namedlog; };
        category "general" { namedlog; };
        category "database" { namedlog; };
        category "security" { namedlog; };
        category "config" { namedlog; };
        category "resolver" { namedlog; };
        category "client" { namedlog; };
        category "unmatched" { namedlog; };
        category "queries" { namedlog; };
};

zone "." IN {
        type hint;
        file "named.ca";
};

zone "localhost" IN {
        type master;
        file "localhost.zone";
        allow-update { none; };
};

zone "0.0.127.in-addr.arpa" IN {
        type master;
        file "named.local";
        allow-update { none; };
};

zone "0.168.192.in-addr.arpa" IN {
        type master;
        file "named.0.168.192";
        allow-update { none; };
};

zone "200.113.216.in-addr.arpa" IN {
        type master;
        file "named.200.113.216";
        allow-update { none; };
};

include "/etc/rndc.key";
vancetechAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jlevieCommented:
If this DNS server is behind a firewall you need to uncomment the query -source directive in the options section.

And your resolv.conf on the DNS server should look like:

search mydomain.tld
nameserver 127.0.0.1

Your named.conf defines reverse zones, but it is missing a zone file for your domain. I presume from what named.conf contains that your reference to it being a "secondary DNS server" means that it is a caching server since neither of the local data zones (0.168.192.in-addr.arpa & 200.113.216.in-addr.arpa) are of type slave and you don't define any masters.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
vancetechAuthor Commented:
jlevie,

Thanks for your response.  I had omitted the slave zones from the named.conf file above as there are a good number of them to fill up the screen.

My first problem was that zone transfers were not updating from the primary and I received "failure trying master: timed out" and "retry limit for master: exceeded" error messages in my log files.  Now, the server is unable to load the zones because they have all expired and are unable to contact the primary.

I'm going back to my original question, http://www.experts-exchange.com/Networking/Linux_Networking/Q_20795139.html
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.