none
messed up my DNS by adding IP to * (All Others) record

    Question

  • I recently added the numeric IP address of my www. to my DNS at  Network Solutions in the * (All Others) A record. I usually keep this blank but figured it was harmless as I already have A records and hostnames for all my public facing servers in the DNS table. I should also mention that I have split zone DNS, same domain name inside my Windows Server DNS as hosted servers in the Network Solutions DNS.

    Immediately after I put the www. IP in the * (All others) record my Remote Desktop users started to call in that they could connect to my Terminal Servers but could not authenticate. I also found that when I would ping servers on my local network at the Terminal Server (muti-homed to my local network and to the public IP address), the ping results were trying to resolve to the public IP of the www. which I had entered in the * (All Others) record. So I removed that and everything soon cleared up. What happened? It seems like that 'innocent' entry wreaked havoc with the DNS resolution to the Terminal Servers and from the Terminal Server but I can't figure out why.


    • Edited by Lake Group Friday, November 08, 2013 9:12 PM spelling
    Friday, November 08, 2013 9:12 PM

All replies

  • Please post unedited ipconfig /all of domain controller and problem client.

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

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

    Friday, November 08, 2013 9:56 PM
  • Hi,

    According to your description, my understanding is that after you added that A record in DNS server, the remote desktop users could not authenticatie. If I had misunderstood anything, please feel free to let me know.

    In these scenario, would you please also post the different results of pinging the server before and after you added the A record?

    Best regards,

    Susie

    Monday, November 11, 2013 8:25 AM
  • Domain Controller ipconfig /all
    Windows IP Configuration

       Host Name . . . . . . . . . . . . : DOMAINCONTROLLER
       Primary Dns Suffix  . . . . . . . : mydomain.com
       Node Type . . . . . . . . . . . . : Unknown
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : mydomain.com

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Server Adapter
       Physical Address. . . . . . . . . : 00-04-23-C4-21-D1
       DHCP Enabled. . . . . . . . . . . : No
       IP Address. . . . . . . . . . . . : 172.16.1.100
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . : 172.16.1.113
       DNS Servers . . . . . . . . . . . : 172.16.1.100
                                           172.16.1.102
    Terminal Server ipconfig /all
    Windows IP Configuration

       Host Name . . . . . . . . . . . . : TERMINALSERVER
       Primary Dns Suffix  . . . . . . . : mydomain.com
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : mydomain.com

    Ethernet adapter Internet Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) PRO/1000 PT Server Adapter #2
       Physical Address. . . . . . . . . : 00-1B-21-AF-84-CE
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::b0aa:4fa6:3b92:1830%23(Preferred)
       IPv4 Address. . . . . . . . . . . : 69.74.108.5(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.248
       Default Gateway . . . . . . . . . : 69.74.108.1
       DHCPv6 IAID . . . . . . . . . . . : 469768993
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-23-DA-16-00-1B-21-AF-82-8C
       DNS Servers . . . . . . . . . . . : 167.206.112.138
                                           167.206.7.4
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Ethernet adapter Local Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) PRO/1000 PT Server Adapter
       Physical Address. . . . . . . . . : 00-1B-21-AF-82-8C
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::44e6:e7d3:9f34:f2f6%22(Preferred)
       IPv4 Address. . . . . . . . . . . : 172.16.1.103(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 419437345
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-23-DA-16-00-1B-21-AF-82-8C
       DNS Servers . . . . . . . . . . . : 172.16.1.100
                                           172.16.1.102
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{973B9E25-AAD3-48FC-A113-3F532B7DF5CC}:

       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 isatap.{84D77B51-6A71-405F-A2A9-EF8F84517D2E}:

       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 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:454a:6c05::454a:6c05(Preferred)
       Default Gateway . . . . . . . . . : 2002:c058:6301::1
                                           2002:c058:6301::c058:6301
       DNS Servers . . . . . . . . . . . : 167.206.112.138
                                           167.206.7.4
       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

    Monday, November 11, 2013 6:14 PM
  • Why is the terminal server multi-homed? This seems the most likely cause of these problems.

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

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

    Monday, November 11, 2013 7:06 PM
  • The public IP is there to allow connections from outside the corporate network. The local IP allows connections to the servers and applications on the corporate network.
    Monday, November 11, 2013 8:29 PM
  • I'd consider doing that in a router rather than multi-homing the server.

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

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

    Tuesday, November 12, 2013 12:17 AM
  • OK understood re: the router. Is there any accounting for what would have cause DNS to get messed up by this action? I have always thought that assigning the ip of my www server to All Others would not have any impact on my local segment and its ability to ping within the local segment but apparently it did. I guess I can't understand why the local Microsoft DNS did not receive priority for the ping of a computer on my domain. Instead it tried to go out to the internet and pick up the Network Solutions DNS.
    Tuesday, November 12, 2013 5:58 PM
  • Its difficult to say for sure but multi-homing causes some really strange results.

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

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

    Wednesday, November 13, 2013 1:30 AM