DNS works but nslookup times out.

[paristotle]

I just installed it today a server 2012r2 server today. I went through the ADS server role installation like I’ve done before. It installed the DNS role as well. Then I installed the DHCP service. The problem was that somehow two DNS servers were created, one with the server_name and the other with the server_name.domainName. Anyway I thought it was strange so I deleted one and it kept coming back after a reboot. All the while nslookup on the server was timing out.

After tearing my hair out for a while I decided to remove ADS, DNS, and DHCP and try it all again. Seems to have gone much smoother the second time around but still nslookup times out. I do get name resolution of internet resources when I work on client computers and resolution on the server must be working because I do have internet access with it but nslookup still times out. Curious fact too no PTR records created by DHCP either.

 

[paristotle]

I forgot to mention that I ran that under the 'Monitoring' tab of the DNS server properties I ran the both tests and they both passed.

 

[YeOldeStonecat]

Can you fire up DNSMGMT.MSC and change to advanced view, expand forward 'n reverse zones..and post a screenie?
Did you setup the Forwarding in the Forwarders tab?
What are the TCP/IP v4 properties of this server?
Event viewer errors?
DNS Server service started?

 

[paristotle]

Thanks for your reply. Here is the screen shot.
The TCP/IP details are as follows.

• static IP address on our local lan
• - 24 bit mask
• - gateway is our router
• - DNS is static. For troubleshooting reasons I tried the following.
  
  • I started with my standard setup which is to use 127.0.0.1 for the DNS server's NIC
  • Then I tried using the actual address of the server instead of 127.0.0.1
  • Currently the DNS server has the ISP's NS info for DNS in IPv4.

The DNS service is confirmed started. When I do an NSLOOKUP from a client and specify my server address the resolution works. Just doesn't work from the server itself
Event ID shows a couple of error 4013, at the time I setup the service, but that usually seems to happen when the service first gets setup . It doesn't reoccur again.
Since my last post I updated the credential in DHCP server so that it can create the PTR recrods in DNS but it didn't work. New clients are added but the corresponding records aren't created.

 

[YeOldeStonecat]

• • Currently the DNS server has the ISP's NS info for DNS in IPv4.

Yeah you definitely don't want that...active directory 'n internal DNS will not work with that.
Clients are using the DC's IP as their one and only DNS, right? Not the routers LAN IP or the ISPs DNS or Google DNS...right?

Can you post a screenie of dnsmgmt.msc with forward 'n reverse zones expanded?

 

[paristotle]

Yup clients are currently using the internal DNS for resolution. (I'll be changing back the DNS info in the NS nic to 127.0.0.1

when I figure all this out)
Here is the screen shot. Forward looks fine. Reverse doesn't look right

 

[YeOldeStonecat]

Wrong attachment..that's some BOM/Quote you're working on.

 

[paristotle]

Wow....that's embarrassing. Thanks for the heads up

 

[YeOldeStonecat]

Huh...haven't seen that. Don't see how it could cause a problem either...but...yeah, usually it's just the shortened host name of the server in there. Lemme fire it up on a new fresh '12r2 server I've done....