Solved

DNS server not working

Posted on 2013-05-10
5
777 Views
Last Modified: 2013-05-18
I have a Win 2008 R2 server running AD, DHCP and DNS, all of which worked fine when I first set it all up (it's for a new client and they haven't started up the business yet so the server is just sitting in my office where I'm setting it up).
Now however, the DNS doesn't work on the client PC's.

When I run the best practice analyser on the DNS role I get several errors including;
The DNS server 192.168.1.149 on Local Area Connection did not successfully resolve the name _ldap._tcp.gc._msdcs.domain.local.
The DNS server 192.168.1.149 on Local Area Connection did not successfully resolve the name of the address (A) record for this computer.
There's several more, all similar, referring to kerboses recource record, LDAP resource records etc.

There's no reference to any issue in the DNS logs.
The Server itself can connect to the Internet fine, but the clients can't, even though they can connect to the server for domain access and DHCP.

Here's the output from ipconfig /all on the server. Sorry it's long - I included everything in case it's relevant but Ethernet adapter Local Area Connection is the only one I think is relevant (Local Area Connection 3 is Open VPN, and Local Area Connection 2 is the other NIC)

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Server01
   Primary Dns Suffix  . . . . . . . : domain.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : domain.local

Ethernet adapter Local Area Connection 3:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : TAP-Win32 Adapter V9
   Physical Address. . . . . . . . . : 00-FF-F8-D6-71-7E
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::3c65:e003:3450:5a71%16(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.8.0.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.252
   Lease Obtained. . . . . . . . . . : 10 May 2013 11:48:54
   Lease Expires . . . . . . . . . . : 10 May 2014 11:48:53
   Default Gateway . . . . . . . . . :
   DHCP Server . . . . . . . . . . . : 10.8.0.2
   DHCPv6 IAID . . . . . . . . . . . : 385941496
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-B8-4B-8A-00-19-99-F5-47-21

   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connectio
n
   Physical Address. . . . . . . . . : 00-19-99-ED-26-EF
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) 82579LM Gigabit Network Connecti
on
   Physical Address. . . . . . . . . : 00-19-99-F5-47-21
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::1c69:ef21:87e7:eb9a%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.149(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.254
   DHCPv6 IAID . . . . . . . . . . . : 234887577
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-B8-4B-8A-00-19-99-F5-47-21

   DNS Servers . . . . . . . . . . . : ::1
                                       192.168.1.149
                                       127.0.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{5764B63B-78F5-41A8-8FF0-3E85876AF0E5}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{36F243C5-92E0-4F7E-A11C-FE7E1376FB5B}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{F8D6717E-AF5D-4260-A5EC-75B171EC26FD}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
0
Comment
Question by:ThatsTheWayWeGetBy
5 Comments
 
LVL 25

Expert Comment

by:SStory
ID: 39155274
I can only say one thing. Be sure it isn't something to do with IPv6 messing you up.  If you stuff all relies on IPv4--still--your clients might be doing IPv6 DNS requests for AAAA and not getting anywhere.
0
 
LVL 6

Expert Comment

by:mrcannon
ID: 39155334
0
 
LVL 13

Expert Comment

by:Jaihunt
ID: 39155439
Hi

Why Two Network cards enabled in the machines ? One is DHCP enabled(Local Area Connection3) and one is Static IP address(Local Area Connection) In dhcp enabled DNS servers are assigned as IPV6 address and in static IP DNS address pointing to ::1 IPV6 Loop back address. That's why  DNS is not resolving properly. If you are using static IP point it to DNS servers and remove the IPV6. If you are using DHCP check why the DNS servers not configured properly or disable the network card.

Thanks
Jai
0
 

Accepted Solution

by:
ThatsTheWayWeGetBy earned 0 total points
ID: 39160878
Thanks for your replies and attempts to help.

Jai, Local Area connection 3 you're referring to in your answer is actually a VPN, not a real card.

Anyway, I have got the issue sorted now, although I'm not even sure I fully understand what the issue was or how to explain what it was - in a nutshell it was actually a DHCP issue as the router and server were both doing DHCP. I disabled DHCP on the server and all is working fine now.

(All the errors thrown up by the DNS best practise analyser were taken care of with an exception)
0
 

Author Closing Comment

by:ThatsTheWayWeGetBy
ID: 39176857
The other posters would have had no way of know, but the actual problem turned out to be DHCP, not DNS
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
MacBook wifi issues 6 37
slow IIS responses after Microsoft December 2016 patches 3 34
how to export this list 4 38
CENTOS DHCP Server / PXE/TFTP 14 67
There have been a lot of times when we have seen the need to enter a large number of DNS entries in a forward lookup zone. The standard procedure would be to launch the DNS Manager console, create the Zone and start adding new hosts using the New…
Resolve DNS query failed errors for Exchange
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …

813 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now