none
ERROR: NO DNS servers for IPV6 stack was found

    Question

  • Hi Everyone

    We have recently performed an upgrade for a customer from Windows server 2003 \ Exchange 2003 to Server 2008 R2 with Exchange 2010 and have encountered numerous issues all which seem to revolve around DNS / IPv6.

    Their infrastructure has...

    2 x server 2008 R2 Domain controllers both running AD Integrated DNS

    1 x server 2008 R2 with Exchange 2010 Server holding all Exchange roles

    There are other 2008 R2 servers on the network including an RDS Server, SQL Server, Double-take VRA Server plus more but the servers listed above are the servers where we see the primary issues.

    Over the past few weeks we have seen the exchange 2010 server lose connection to the domain controllers suggesting they are no longer contactable, this is an issue we have raised in the correct forum but I beleive the symptoms of this fall back to DNS / IPv6.

    When running dcdiag.exe /V /C /D /E /s:wrexham.local we see a number of IPv6 AAAA records are missing from key locations and also the error message in the title ERROR: NO DNS servers for IPV6 stack was found.

    As this is primarily a question relating to DNS / IPv6 I will give the details of the Domain controllers only - the reference to exchange was an example of issues we see, below are the ipconfig / all outputs for both domain controllers followed by the latest dcdiag output with the /E so that both DC's are included.

    I have researched the ERROR: NO DNS servers for IPV6 stack was found issue as much as possible reading every link I have found but non present any useful information except to switch of IPv6 which I really do not want to do so any help would very much appreciated.

    For Further information We do not seem to be getting many DNS errors, we seem to get 1 or 2 errors a day which relate to an IPv6 address which I do not recognise could not be resolved, apart from this logs on all servers seem to be extremely clean which is also slightly concerning as these problems when they occur are quite severe and I would expect more in the logs than I am currently seeing.

    IPCONFIG / ALL - CCLFILE1

    Windows IP Configuration

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

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : vmxnet3 Ethernet Adapter
       Physical Address. . . . . . . . . : 00-0C-29-7E-8C-18
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::910d:d6ca:c0f1:c556%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 128.0.0.12(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 128.0.0.254
       DHCPv6 IAID . . . . . . . . . . . : 234884137
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-45-DF-86-00-0C-29-7E-8C-1

       DNS Servers . . . . . . . . . . . : 128.0.0.12
                                           128.0.0.17
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{49B04247-EDA6-4294-A3FF-35A4313E6B7E}:

       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 6TO4 Adapter:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft 6to4 Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2002:8000:c::8000:c(Preferred)
       Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
       DNS Servers . . . . . . . . . . . : 128.0.0.12
                                           128.0.0.17
       NetBIOS over Tcpip. . . . . . . . : Disabled

    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

    IP CONFIG /ALL - CCLBACKUP

    Windows IP Configuration

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

    Ethernet adapter Local Area Connection 4:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : HP NC382i DP Multifunction Gigabit Server
     Adapter #56
       Physical Address. . . . . . . . . : 9C-8E-99-1A-9F-88
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Local Area Connection 3:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : HP NC382i DP Multifunction Gigabit Server
     Adapter #51
       Physical Address. . . . . . . . . : 9C-8E-99-1A-9F-92
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::bd4d:193a:c747:d440%15(Preferred)
       IPv4 Address. . . . . . . . . . . : 128.0.0.17(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . : 128.0.0.254
       DHCPv6 IAID . . . . . . . . . . . : 379358873
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-FC-60-5A-9C-8E-99-1A-9F-90

       DNS Servers . . . . . . . . . . . : 128.0.0.17
                                           128.0.0.12
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection 2:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : HP NC382i DP Multifunction Gigabit Server
     Adapter #45
       Physical Address. . . . . . . . . : 9C-8E-99-1A-9F-8A
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    PPP adapter RAS (Dial In) Interface:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : RAS (Dial In) Interface
       Physical Address. . . . . . . . . :
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 128.0.0.108(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.255
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{C06AA226-D2FF-41FC-850C-9A58AE63FDE0}:

       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.{6E06F030-7526-11D2-BAF4-00600815A4BD}:

       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 6TO4 Adapter:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft 6to4 Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2002:8000:11::8000:11(Preferred)
       IPv6 Address. . . . . . . . . . . : 2002:8000:6c::8000:6c(Preferred)
       Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
       NetBIOS over Tcpip. . . . . . . . : Disabled

    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

    Tunnel adapter isatap.{6A2A5A10-2D47-4D36-8768-EF92B3511CF0}:

       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

    Tunnel adapter isatap.{F3317BEB-E3DC-469C-80A9-7AD7ACEC5C57}:

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

    Tunnel adapter isatap.{8B2C785F-9639-4197-AD6E-C714AC327ADC}:

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

    DCDIAG Output

    Is too large to post here, please ask and I will post required info

    Thursday, December 01, 2011 4:56 PM

Answers

  • I think the issue lies with multihoming CCLBACKUP.  A multihomed DC, is a DC with mulitple NICs, multiple IPs, and/or RRAS installed.

    The non-used interfaces need to be disabled in Windows, not simply unplug them, otherwise as being active and set to DHCP, they are self configuring with an APIPA (169.254.x.x), which is registering into DNS that way, and will cause problems with AD.

    CCLBACKUP, a domain controller, having too many interfaces and RRAS installed. Ethernet adapter Local Area Connection 4 is disconnected, but is not disabled, and it's set for DHCP, therefore I'm willing to bet you'll find 169.254.x.x records in DNS.

    Ethernet adapter Local Area Connection 2 is diconnected as well.

    Both Local Area Connection 2 & Local Area Connection 4 need to be disabled.

    After you disable them, run an ipconfig /resgisterdns, and restart the netlogon service.

    What worries me is RRAS is installed, which makes it difficult to properly configure the DC to not register the dialin interfaces. If internal workstations, or even other DCs try to resolve this DC, it *may* get a 169.254 or one of the PPP addresses, and the workstation, server or other DC won't be able to connect.

    Note - this is not an IPv6 issue.

    Please disable the additional interfaces, run the commands above, then re-run a dcdiag /v, and run a repadmin /showrepls, and upload them to http://skydrive.live.com (it's free), provide us the link to the files.

     

    In the meantime, read more on multihoming a DC and what it does:

    Multihomed DCs (with more than one unteamed NIC or multiple IPs) with DNS, RRAS, iSCSI, and/or PPPoE adapters - A multihomed DC is not a recommended configuration, however there are ways to configure such a DC to work properly. http://msmvps.com/blogs/acefekay/archive/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters.aspx

     

    Thanks,
    Ace

     


    Ace Fekay
    MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

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

    FaceBook Twitter LinkedIn
    • Proposed as answer by Tiger Li Wednesday, December 07, 2011 12:52 AM
    • Marked as answer by Tiger Li Thursday, December 08, 2011 1:44 PM
    Friday, December 02, 2011 5:13 AM

All replies

  • I think the issue lies with multihoming CCLBACKUP.  A multihomed DC, is a DC with mulitple NICs, multiple IPs, and/or RRAS installed.

    The non-used interfaces need to be disabled in Windows, not simply unplug them, otherwise as being active and set to DHCP, they are self configuring with an APIPA (169.254.x.x), which is registering into DNS that way, and will cause problems with AD.

    CCLBACKUP, a domain controller, having too many interfaces and RRAS installed. Ethernet adapter Local Area Connection 4 is disconnected, but is not disabled, and it's set for DHCP, therefore I'm willing to bet you'll find 169.254.x.x records in DNS.

    Ethernet adapter Local Area Connection 2 is diconnected as well.

    Both Local Area Connection 2 & Local Area Connection 4 need to be disabled.

    After you disable them, run an ipconfig /resgisterdns, and restart the netlogon service.

    What worries me is RRAS is installed, which makes it difficult to properly configure the DC to not register the dialin interfaces. If internal workstations, or even other DCs try to resolve this DC, it *may* get a 169.254 or one of the PPP addresses, and the workstation, server or other DC won't be able to connect.

    Note - this is not an IPv6 issue.

    Please disable the additional interfaces, run the commands above, then re-run a dcdiag /v, and run a repadmin /showrepls, and upload them to http://skydrive.live.com (it's free), provide us the link to the files.

     

    In the meantime, read more on multihoming a DC and what it does:

    Multihomed DCs (with more than one unteamed NIC or multiple IPs) with DNS, RRAS, iSCSI, and/or PPPoE adapters - A multihomed DC is not a recommended configuration, however there are ways to configure such a DC to work properly. http://msmvps.com/blogs/acefekay/archive/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters.aspx

     

    Thanks,
    Ace

     


    Ace Fekay
    MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

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

    FaceBook Twitter LinkedIn
    • Proposed as answer by Tiger Li Wednesday, December 07, 2011 12:52 AM
    • Marked as answer by Tiger Li Thursday, December 08, 2011 1:44 PM
    Friday, December 02, 2011 5:13 AM
  • Hi Ace

    Thanks for the response, I have already begun working through your notes, NIC's have been disabled and I am currently reviewing DNS for any icorrectly registered IP addresses such as the 169 auto assigned addresses. We did have issues a few days ago with the RRAS IP address 128.0.0.108 being registered, however one of my collegues made a registry change to stop the RRAS Adapter from Registering itself in DNS. We expected this to fix the issue but as per the above question we still see issues.

    Once I have finished reviewing DNS I will rerun DCDiag and repadmin and upload to the above site,

    Thanks John

    Friday, December 02, 2011 9:59 AM
  • John,

    Any updates on this issue?

    Ace

     


    Ace Fekay
    MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

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

    FaceBook Twitter LinkedIn
    Wednesday, December 07, 2011 2:48 AM