Got a DNS problem

MattGibson

I feel like I should know this, but I just can't seem to figure this out.

I have two servers, one is named testserver1.domain1.local (is a DNS server) and the other is testserver2.domain1.local (is not a DNS server)

I am trying to run the command ping testserver2 from the testserver1 and it is not resolving. I have disabled NetBIOS and have repeatedly ran ipconfig /flushdns and nbtstat -R (just for good measure)

when I go into the DNS console for domain1.local there is an A resource record for testserver2.... that is why this is making even less sense.

testserver1 IP

192.168.1.2
255.255.255.0
192.168.1.1

DNS - my ISP's DNS

testserver2 IP
192.168.1.3
255.255.255.0
192.168.1.1

DNS - 192.168.1.2


The testserver1 can ping directly to the IP, but it is not resolving the name.

I went to the properties of the testserver1 machine, to the monitoring tab, and did the simple recursive queries. Both passed.

Any ideas?

dynamik

Try setting your DNS server to use itself for DNS and then go to the server properties and put your ISP's DNS server(s) into the forwarder for all other domains.

chmod

A firewall not letting you query the DNS.

Try from the CMD in the non-dns server the following:

-Nslookup
-Server "ip address of your dns server"
-type the name of your machine. Check the output.

Or ipconfig -all and make sure the dns setting are ok.

Alif_Sadida_Ekin

dynamik wrote: »

Try setting your DNS server to use itself for DNS

I agree with this. I see, in your setup, that you configured testserver1's tcp/ip settings to only include your ISP's DNS servers. Change this and put testserver1's ip address in as your primary DNS server.

NetAdmin2436

Same thing goes for your client computer DNS settings. Client PC's should only point to your internal DNS server(s). Only use your ISP DNS as a forwarder on your internal DNS server.

The only time you should really ever point to your ISP DNS in the TCP/IP settings is if you just have a single computer or very small workgroup network.

MattGibson

Thanks for all the replies. They did the trick.

I suppose it should have made sense to me for the server to point to itself for DNS because that is the DNS server that is hosting the A record.

Once I did that, everything worked perfectly. Noobie mistake!

UncleCid

MattGibson wrote: »

Thanks for all the replies. They did the trick.

I suppose it should have made sense to me for the server to point to itself for DNS because that is the DNS server that is hosting the A record.

Once I did that, everything worked perfectly. Noobie mistake!

Pfft. I guess i'm a newbie, too, but I swear I make that mistake everysingle time I setup a DNS server.