DNS Receiving NXDOMAIN

ep7network0819 · 05-15-2016, 03:30 PM

Hi everyone,

I recently made some minor changes to my forward and reverse lookup zones. I deleted old workstations that are no longer on my network.

I only have one master DNS server, and four other servers on the network.

When I type named-checkzone cseproject.net /var/named/forward.test
I receive: zone cseproject.net OK.

When I type named-checkzone cseproject.net /var/named/reverse.test
I receive: zone cseproject.net OK.

I type dig ns1.cseproject.net and I receive no error.

But, when I type dig -x <MyIPaddress>, I receive status: NXDOMAIN.
NXDOMAIN means that a domain does not exist. But, when I type dnsdomainname it shows my domain name cseproject.net. Whats going on, how can I fix this. I should be able to type dig -x <MyIPaddress> and I should receive no error as my status.

How can I fix this issue, or em I making an issue out of nothing?
The domain name isn't available to the Internet, my domain is only available in my intranet. Not sure if that's causing the NXDOMAIN error.

forward zone:
png image is attached.

reverse zone:
png image is attached.

Thanks for taking the time to read this thread.

bathory · 05-16-2016, 12:48 AM

Hi,

From the reverse zone file attached image, I see that you miss the trailing dots in the 4 PTR resords.
You should use:

Code:

<snip>
200 IN PTR ns1.cseproject.net.
201 IN PTR hardian.cseproject.net.
202 IN PTR www.cseproject.net.
203 IN PTR maiil.cseproject.net.

Note also that you you don't need the A records in reverse zone zonefile and the line

Quote:

@ IN PTR cseproject.net

Regrads

Ellendhel · 05-16-2016, 12:30 PM

Quote:

But, when I type dig -x <MyIPaddress>, I receive status: NXDOMAIN.
NXDOMAIN means that a domain does not exist. But, when I type dnsdomainname it shows my domain name cseproject.net.

dnsdomainname is getting is information from the system itself, so if your host is properly configured you will get the correct domain name, as expected.

dig send a query to one of the DNS servers listed in /etc/resolv.conf. I would recommend to check the content of that file first. On a system running a DNS server, the file should list 127.0.0.1 only.

You can also force dig to query a specific server, for instance a server at the IP address 192.168.1.1:

Code:

dig @192.168.1.1 A www.example.net

ep7network0819 · 05-16-2016, 09:45 PM

Hello,

So far, I can successfully run dig @myIP A serverName.cseproject.net and receive no error for status.

I think for now my DNS server is doing its job. I have no DNS issues with other servers on my network.
Going to look into this further!! thanks for everyone's advise.