none
Internet not working after migrating DNS 2003 server to 2016 RRS feed

  • Question

  • HI Friends,

    I have recently migrated from from 2003 SBS to 2016 std edition. 

    Migration of FSMO roles completed. Replication also completed but it seem DNS is not working properly on new server. 

    DNS for local infrastructure is working but for public ip and internet it seems not to be working. 

    DNS will only work if the IP address of the old dns server is mentioned in the forwarders IP address in new DNS server properties.

    i tried by using ISP DNS IP Address in forwarders but still the same issue. 

    Any kind of advise would be appreciated. 

    Thanks,

    Tuesday, December 4, 2018 5:41 AM

All replies

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

     

     



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

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

    Tuesday, December 4, 2018 3:12 PM
  • Hi Patrick,

    Here is output for the same.

    C:\Users\administrator.WEA>ipconfig /all

    Windows IP Configuration

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

    Ethernet adapter Ethernet 2:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) I350 Gigabit Network Connection #2
       Physical Address. . . . . . . . . : 6C-92-BF-0C-02-7D
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Ethernet:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) I350 Gigabit Network Connection
       Physical Address. . . . . . . . . : 6C-92-BF-0C-02-7C
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.1.61(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 192.168.1.61
       NetBIOS over Tcpip. . . . . . . . : Enabled

    i can see that all the clients have DNS ip address as 192.168.1.61 but internet will not work if i will stop the dns service on our old server or i remove the IP address of old server in forwarder in DNS setting in new server.

    Thanks,
    NK

    Tuesday, December 4, 2018 10:48 PM
  • I'd check the problem client has the static address of domain controller listed for DNS and no others such as router or public DNS. Also confirm the gateway is correct. By default internet queries are passed on to the 13 default root hint servers or optionally forwarders. If problems persist then please run;

    • Dcdiag /v /c /d /e /s:DCName >c:\dcdiag.log
      (please replace DCName with your domain controller's netbios name)
    • repadmin /showrepl >C:\repl.txt
    • ipconfig /all > C:\dc1.txt
    • ipconfig /all > C:\dc2.txt
    • ipconfig /all > C:\workstation.txt

    then put files up on OneDrive and share a link.

     

     

     

     



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

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



    Tuesday, December 4, 2018 10:51 PM
  • Hi Dave,

    All the information will be publicly available, can i PM you the link. 

    Thanks

    Wednesday, December 5, 2018 12:08 AM
  • These forums do not have any method of direct messaging. You can post the text of a OneDrive link here. There's nothing in the files of a security issue but I can let you know when I have them so you can remove link.

     

     



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

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


    Wednesday, December 5, 2018 12:17 AM
  • Please use below link to download, please let me know so that i can remove the link. 
    Wednesday, December 5, 2018 12:37 AM
  • No link?

     

     



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

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

    Wednesday, December 5, 2018 12:40 AM


    • Edited by nk3095 Wednesday, December 5, 2018 1:07 AM
    Wednesday, December 5, 2018 12:40 AM
  • got it

     

     



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

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

    Wednesday, December 5, 2018 12:42 AM
  • What was the ipconfig /all posted above for??? no reference to 192.168.1.61 anywhere?? Confusion..........

    Missing the ipconfig /all for the 2003 and 2016 servers

    I'd check the 2016 (192.168.1.51) DC has correct gateway. All but one root hint are valid but you can also try adding 8.8.8.8 as forwarder. Does internet work on 2016? Can you ping / tracert 8.8.8.8 ? 2016 system event log clean?

     

     



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

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

    Wednesday, December 5, 2018 1:10 AM
  • I dont want the ip to visible publicly that is why i put the different ip. let me check if it works with 8.8.8.8. Internet does not work on 2016 if i remove forwarder ip which is for 2003 server. 


    Wednesday, December 5, 2018 1:18 AM
  • when i enter 8.8.8.8, it give message as a time out occurred during validation
    Wednesday, December 5, 2018 1:20 AM
  • 2016 does not have forwarder configured unless the file was not recent or up to date. 

     

     



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

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

    Wednesday, December 5, 2018 1:22 AM
  • check results of;

    ping 8.8.8.8

    tracert 8.8.8.8

     

     



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

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

    Wednesday, December 5, 2018 1:22 AM
  • ping and tracert both works. 

    Microsoft Windows [Version 10.0.14393]
    (c) 2016 Microsoft Corporation. All rights reserved.

    tracert 8.8.8.8

    Tracing route to google-public-dns-a.google.com [8.8.8.8]
    over a maximum of 30 hops:

      
      2    18 ms    18 ms    18 ms  gw1.vic.asp.telstra.net [203.45.255.1]
      3    21 ms    21 ms    21 ms  bundle-ether3-100.win-core10.melbourne.telstra.net [203.50.80.129]
      4    32 ms    31 ms    31 ms  bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
      5    30 ms    29 ms    29 ms  bundle-ether1.ken-edge903.sydney.telstra.net [203.50.11.173]
      6    30 ms    30 ms    30 ms  72.14.212.22
      7     *        *        *     Request timed out.
      8    33 ms    37 ms    33 ms  209.85.243.144
      9    31 ms    31 ms    31 ms  209.85.244.173
     10    31 ms    31 ms    31 ms  google-public-dns-a.google.com [8.8.8.8]

    Trace complete.



    • Edited by nk3095 Wednesday, December 5, 2018 1:30 AM
    Wednesday, December 5, 2018 1:27 AM
  • If the system event log is clean then I'd stand up a new 2016 as a test, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to verify health, when all is good you can decommission / demote old one.

     

     



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

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

    Wednesday, December 5, 2018 1:30 AM
  • This is what i just did, earlier we had 2003 sbs. i installed new 2016 std edition, patched it, activated and then join to existing domain. promoted it and migrated all fsmo roles. but as i noticed dns issue i am stuck, i can not decommission 2003 server until dns issue is fixed. 
    Wednesday, December 5, 2018 1:37 AM
  • Understood, If the system event log is clean then I'd transfer roles back and rebuild it. DNS is broken.

     

     



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

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

    Wednesday, December 5, 2018 1:41 AM
  • i will try that also, thank for your support. Really appreciate.
    Wednesday, December 5, 2018 1:43 AM
  • Sounds good, you're welcome. Things like this happen once in a blue moon. If you clean install and patch fully things should go smooth next time around.

     

     



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

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

    Wednesday, December 5, 2018 1:49 AM
  • Hi Dave,

    i would like to inform you that the issue is resolved now. Actually the issue was due to firewall. The firewall was configured to allow DNS communication for outside for old server only. once i configured it for new server the issue resolved.

    Thanks

    Thursday, January 17, 2019 12:07 AM
  • Glad to hear it's sorted.

     

    (please don't forget to mark helpful replies as answer)

     

     



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

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

    Thursday, January 17, 2019 12:16 AM