Unable to query DNS

Dear TE,

I have a DNS server with one NIC that is unable to query itself, when DNS is configured it automatically modified the preferred DNS server and uses the loopback address of 127.0.0.1, I had to modify this and have to specifically assign the DNS server.

Configuration wise I believe I have not missed a thing, since this is not the first time I've configured one, the Forward Lookup Zone exists and dynamic update is enabled, but for some reason when nslookup is run on the DNS server it's unable to contact the DNS which itself, same thing happens with client that is using the DNS server.

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

jbaello

FQDN: w2k3en32-s03.soggyrice.local
IP Address: 192.168.1.105 (Static)
NSlookup Result:
*** Can't find server name for address 192.168.1.105: Non-existent domain
Default Server: Unknown
Address: 192.168.1.105

astorrs

Okay now from the nslookup prompt enter "w2k3en32-s03.soggyrice.local" and post the output.

Ahriakin

Do you have a Reverse Lookup Zone? You will need it to resolve IPs to Names (Forward is only for Names to IPs).

GJB

Can't Find Server Name when Starting Nslookup.exe
When starting the Nslookup.exe utility, the following error may occur:

*** Can't find server name for address w.x.y.z: Non-existent domain

This error occurs when there is no PTR record for the name server's IP address. When Nslookup.exe starts, it does a reverse lookup to get the name of the default server. If no PTR data exists, this error message is returned. To correct make sure that a reverse lookup zone exists and contains PTR records for the name servers.

from http://support.microsoft.com/kb/200525/en-us

Sounds like you need a Reverse Zone set up with a PTR record for your DNS/DC

astorrs

Exactly where I was going with it, but I wanted to confirm forward lookups were working as well (although you would assume they would be given the fact everything else on the network is - the last thing this thread needed was any more assumptions

blargoe

Hi,

DNS is working, to avoid that one error in nslookup you have to have reverse lookup zone defined. If you were to continue with your nslookup query, it would work fine.

jbaello

Thank you for the reply, specially you Astorrs :P Reverse Forward Lookup Zone is configured, I am aware that when DCPROMO is executed and DNS is selected to be configured automatically Reverse Forward Lookup Zone is not configured by automatically, so I always make sure that I configure this, like I mentioned A/PTR record successfuly gets updated, this includes NS record for the DNS server.

blargoe

So there is a PTR record Reverse DNS for 105.1.168.192.in-addr.arpa? I can't think of another reason why you'd get that error when you start nslookup.

jbaello

blargoe wrote:

So there is a PTR record Reverse DNS for 105.1.168.192.in-addr.arpa? I can't think of another reason why you'd get that error when you start nslookup.

Yes, I will try to modify the host file and include netbios for DNS server... see if this works... I will also play around TCP/IP Advanced Configuration > DNS...

jbaello

OWA works on this problematic box...

https://webmail.soggyrice.com/owa

Means I am able to use AD accounts that has exchange mailbox... I am sure there is tons of DNS queries back and forth going on with my server except nslookup...

jbaello

jbaello wrote:

astorrs wrote:

I am thinking that Microsoft might need to propagate some information over before this thing can work again, then eventually it would work. I can be wrong, but since "everything" else is working except "nslookup" like I have posted I might say it's a M$ bug.

This thing is working at 1st I modified the host file and added an entry there, but after I deleted the entry to it's original state, it still works so basically I did not do antyhing, I think it's a propagation/update issue that did not working properly...