DNS Service not working all the time

NetAX · 08-04-2004, 02:32 PM

Hi, this is my problem. clients cannot persistently type"nslookup myserver.net, ns1,myserver.net, ns2.myserver.net and get a proper reply. It returns with a reply saying domain not found. I leave the computers on for a while and when i return and try the command again it replies with the servername and ip address. I have no idea why it keeps doing that.

This is my /etc/named.conf file:

Code:

//-----MYSERVER.NET--------------------
zone "myserver.net" in
{
        type master;
        file "myserver.net.zone";
};


zone "ns1.myserver.net" in
{
        type master;
        file "ns1.myserver.net.zone";
};

zone "ns2.myserver.net" in
{
        type master;
        file "ns2.myserver.net.zone";

};
zone "4.16.172.in-addr.arpa" in
{
        type master;
        file "172.16.4.zone";
};

zone "31.16.172.in-addr.arpa" in
{
        type master;
        file "172.16.31.zone";
        forwarders {172.16.4.253;};
};
//--------------------------------

My myserver.net.zone file just contains the names of the 3 nameservers and the addresses myserver.net listens on.

This is my ns1.myserver.net/ns2.myserver.net file(IP addresses different in both files):

Code:

$TTL 1W
@               IN SOA  @   root (
                                42              ; serial (d. adams)
                                2D              ; refresh
                                4H              ; retry
                                6W              ; expiry
                                1W )            ; minimum


                IN NS           ns1.myserver.net.
                IN NS           ns2.myserver.net.
                IN A            172.16.4.253

this is one of reverse address file:

Code:

$TTL 1W
@               IN SOA          myserver.net.  root.myserver.net. (
                                42              ; serial (d. adams)
                                2D              ; refresh
                                4H              ; retry
                                6W              ; expiry
                                1W )            ; minimum


                   IN NS           @
253             IN PTR          myserver.net.

clients can ping the server names but cannot do nslookup.
I hope somebody can help me out with this problem.

NetAX · 08-05-2004, 12:30 PM

Nevermind. I found out the problem was from a misconfigured /etc/resolv.conf fle.

BrianWGray · 08-05-2004, 01:45 PM

so just out of curiousity what was it in the .conf that caused the spuratic operation?

NetAX · 08-05-2004, 04:14 PM

Code:

search myserver.net
#try ns1.myserver.net
nameserver 172.16.4.253
#then try ns2.myserver.net
nameserver 172.20.31.255
#finally dm1.w2200.myserver.net
nameserver 192.168.1.1





#nameserver 172.16.4.253
#nameserver 172.16.31.255
#nameserver 192.168.1.1
#search ns1.myserver.net ns2.myserver.net dm1.w2200.myserver.net

For some reason it didnt like the way it was written. The commented section is where i found the problem. The top section shows the changes i made in the file. Next to nothing changed in the way I wrote it, just the format.

By the way the commented version was written from the YaST GUI.