none
Windows Server 2008R2 DNS Problems

    Question

  • I have a preexisting 2003 DNS and AD server. I am attempting to migrate everything to a newer 2008 server. I have already installed DNS and AD on the new machine and successfully transferred the roles. Both servers are happy, the DNS zones look the same and the AD looks the same, however, when I disable the DNS on the old 2003 server, the new DNS will not work. Computers trying to visit websites will say the server doesn't have a DNS entry. I have checked and all connecting clients are looking to the new server for DNS.

    Any help would be appreciated!

    Monday, July 01, 2013 8:47 PM

Answers

  • We found that we were able to ping DNS names and get a response, but the browser will not display them. After some searching we discovered some suggesting to disable eDNS, but after doing so, the problem persists.
    Tuesday, July 02, 2013 3:40 PM

All replies

  • Hello,

    please post an unedited ipconfig /all from ALL DC/DNS servers and one client with problems, so we can verify some settings.

    Have you configured the FORWARDERS on the new DNS server to the ISPs DNS server?


    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

    Tuesday, July 02, 2013 10:55 AM
  • Existing DNS Server 2003:


    Windows IP Configuration



       Host Name . . . . . . . . . . . . : delta2

       Primary Dns Suffix  . . . . . . . : Frontier.local

       Node Type . . . . . . . . . . . . : Hybrid

       IP Routing Enabled. . . . . . . . : No

       WINS Proxy Enabled. . . . . . . . : No

       DNS Suffix Search List. . . . . . : Frontier.local



    Ethernet adapter Local Area Connection:



       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller

       Physical Address. . . . . . . . . : 90-E6-BA-8C-1C-08

       DHCP Enabled. . . . . . . . . . . : No

       IP Address. . . . . . . . . . . . : 172.16.0.10

       Subnet Mask . . . . . . . . . . . : 255.255.0.0

       Default Gateway . . . . . . . . . : 172.16.2.2

       DNS Servers . . . . . . . . . . . : 127.0.0.1

    New DNS Server 2008R2:

    Windows IP Configuration

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

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Physical Address. . . . . . . . . : 90-E6-BA-8C-1B-85
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 172.16.0.3(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . : 172.16.2.2
       DNS Servers . . . . . . . . . . . : 172.16.0.3
                                           127.0.0.1
       Primary WINS Server . . . . . . . : 172.16.0.3
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{78E76BC8-5BAF-4F73-8FFE-C7FA9FEBD4C7}:

       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 Local Area Connection* 11:

       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

    Client Computer Windows 7:

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Video-PC
       Primary Dns Suffix  . . . . . . . : Frontier.local
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : Frontier.local

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) 82567V-2 Gigabit Network Connection
       Physical Address. . . . . . . . . : 20-CF-30-75-CB-33
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::e885:a5a4:9540:8e87%10(Preferred)
       IPv4 Address. . . . . . . . . . . : 172.16.1.74(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Lease Obtained. . . . . . . . . . : Tuesday, June 25, 2013 3:52:23 PM
       Lease Expires . . . . . . . . . . : Wednesday, July 10, 2013 8:25:18 PM
       Default Gateway . . . . . . . . . : 172.16.2.2
       DHCP Server . . . . . . . . . . . : 172.16.0.10
       DHCPv6 IAID . . . . . . . . . . . : 237031216
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-92-B2-CE-20-CF-30-75-CB-33
       DNS Servers . . . . . . . . . . . : 172.16.0.3
                                           172.16.0.10
       Primary WINS Server . . . . . . . : 172.16.0.3
       Secondary WINS Server . . . . . . : 172.16.0.10
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{381E2E4C-004D-470A-8F8E-EC322662D030}:

       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 Teredo Tunneling Pseudo-Interface:

       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

    Yes, we have configured the forwarders on the new DNS server.

    Tuesday, July 02, 2013 3:35 PM
  • We found that we were able to ping DNS names and get a response, but the browser will not display them. After some searching we discovered some suggesting to disable eDNS, but after doing so, the problem persists.
    Tuesday, July 02, 2013 3:40 PM
  • Hello,

    on the new DC/DNS I see only its own ip address on the NIC. Did you use this configuration also during promotion from the new DC? Was DNS server role already installed then? If NOT then you can of course NOT use itself as DNS server, you should have used ONLY the existing domain DNS server on the NIC until the new DC/DNS has full replicated.

    So all domain machines are listed in the forward lookup zone from the new DNS server? Please remove the loopback ip address on the Windows server 2003 DC 127.0.0.1 as preferred, instead use the real ip address. Also add the old DNS server on the new DC as second and the loopback ip address as 3rd.

    Then run ipconfig /flushdns and ipconfig /registerdns and restart the netlogon service.


    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

    • Proposed as answer by Patris_70 Wednesday, July 03, 2013 1:55 PM
    Tuesday, July 02, 2013 6:14 PM
  • I was unsure what configuration I used during the promotion, so I started fresh. I reinstalled windows, set the DNS to the existing server, installed AD and DNS, transferred the roles, and when it was all finished, I set the primary DNS as it's real IP, the second as the existing DNS, and the third as the loopback IP. All domain machines are listed in the forward lookup zone. Even after all this, it will not run correctly. The client can ping DNS names and recognizes the new server as the DNS, but the browser will not resolve.

    Here is the new ipconfig /all from the new server:


    Windows IP Configuration

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

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Physical Address. . . . . . . . . : 90-E6-BA-8C-1B-85
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::59f0:d42e:cf18:69d7%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 172.16.0.3(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . : 172.16.2.2
       DHCPv6 IAID . . . . . . . . . . . : 244377274
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-64-FA-1B-90-E6-BA-8C-1B-85
       DNS Servers . . . . . . . . . . . : ::1
                                           172.16.0.3
                                           172.16.0.10
                                           127.0.0.1
       Primary WINS Server . . . . . . . : 172.16.0.10
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{D85CC2CF-B74F-468B-8398-81F235B6B841}:

       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 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

    Wednesday, July 03, 2013 4:52 PM
  • It even allows me to search Google! but no other sites will work.
    Wednesday, July 03, 2013 4:59 PM
  • Hi,

    If it allows you to search Google, then there are less chances that this can be a DNS Issue, it could be a possible browser issue.

    Try updating latest updates for your browser and try again.

    or  Try a different browser.

    Hope that helps :)


    Vikky

    Wednesday, July 03, 2013 5:40 PM
  • It's definitely not a browser issue as it happens on any client. Also, any other site besides Google gives a DNS error saying there is no DNS entry.
    Wednesday, July 03, 2013 5:57 PM
  • Hello,

    what does "but the browser will not resolve" mean?

    Have you configured the FORWARDERS to the ISPs DNS server on the DNS server properties in the DNS management console?


    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

    Wednesday, July 03, 2013 6:09 PM
  • It means the browser will do nothing for a while and then displays a DNS error saying that there is no DNS entry for the name provided.

    And yes, I have configured the forwarders.

    Wednesday, July 03, 2013 6:24 PM
  • Bump...any one have any idea whats going on?
    Friday, July 05, 2013 7:46 PM
  • hi GrowingDark

    Please check this:

    1 - Test connection from your server to external DNS

    2- windows firewall is enable?

    regards

    Friday, July 05, 2013 10:34 PM