locked
Server 2008 DNS Issue with remote site. RRS feed

  • Question

  • Hey Guys

    Was wondering if you could help me out.

    Having issues with a connection between our HQ and a site.

    We are connected together via Metro Ethernet VPN Tunnel.

    We have 2 servers at HQ 1 being our DC and other our App server both running Server 2008.

    We have an issue where our remote site loses DNS connectivity to our App server though not to our DC.

    We can ping the app server via IP and also connect to it via IP but not by name.

    The remote site can access all websites and still browse the fileshare on our DC but our App server cannot be reached by name. 

    This happens intermittently then returns with no issue. It becomes reachable by name but then shortly is no longer reachable by name but only by IP.

     

    Are you guys able to help with some advice ?

     


    Monday, August 1, 2011 4:32 AM

Answers

  • Hi,

     

    Thank you for your post.

     

    Please also verify that if your client can contact your DNS server when your issue happens. To verify whether a client has basic TCP/IP access to the DNS server, first try pinging your DNS server by its IP address.

     

    If you could not ping your DNS server, it indicates that the source of the problem is more likely a network connectivity problem between the client and the DNS servers.

     

    If the DNS client can ping the DNS server computer, please also verify that the DNS server is started and able to listen for and respond to client requests. Try using the nslookup command to test whether your server can respond to DNS clients.

     

    Best Regards,

    James

    Tuesday, August 2, 2011 6:03 AM

All replies

  • When yo state that it is reachable by name, do you mean single label (ie "hostname") or FQDN (ie "hostname.domain.tld"). Start by using the FQDN as the sinlge lable might rely on netbios, which is by default limited to one subnet.

    Are both sites using the same dns? if so, test the latency between the sites (use ping -t). If it is AD integrated, check your replication, otherwise check your forwarder, stub zone and/or zone transfer if applicable.

    Use nslookup to troubleshoot dns: it allow you to connect to any dns server and query it for any record.

     

    For better troubleshooting hints, please post an ipconfig /all output from your DC and 2 clients (one in each site)

     


    MCP/MCSA/MCTS/MCITP
    Monday, August 1, 2011 6:25 AM
  • Please let us know the detailed DNS configuration of remote office. Make sure DNS A record is registered correctly for APP server. 

     

    Thanks


    This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, August 1, 2011 6:57 AM
  • On the local DNS server create A records for the app servers in the HQ.

    Thanks

     

     

    Monday, August 1, 2011 8:04 AM
  • Hello,

    We have 2 servers at HQ 1 being our DC and other our App server both running Server 2008.

    Note that it is recommended to have at least two DC / DNS / GC servers per domain.

    We have an issue where our remote site loses DNS connectivity to our App server though not to our DC.

    What do you mean by that?

    We can ping the app server via IP and also connect to it via IP but not by name.

    Then you have a DNS name update / resolution problem.

    Please make sure that your application server is pointing to your DC as primary DNS server. Once done, run ipconfig /registerdns and restart netlogon on it. After that, check that its A record had been created / updated with the correct IP address.

    For the client computers, make sure that they are pointing to your DC as primary DNS server.

     


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

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

    Monday, August 1, 2011 8:41 AM
  • Hey Guys

     

    Thanks for the reply.

     

    A little more info :

     

    We are running a Single domain. Our second site is connected via VPN tunnel.

    Both sites run on a separate subnet both using 255.255.255.0 mask.

    That remote client PC's at the remote site lose name resolution (DNS) to 1 of our servers at any random time and can only access it by IP. Then shortly it is restored by itself.

    The config is fine on that server as it looks to our DC as its primary DNS server.

    All our client PC's are configured for DHCP and pick up all settings fine.

     

    If you need more info let me know.

     

    Thanks for your help guys.

     



    Monday, August 1, 2011 11:25 PM
  • Hi,

     

    Thank you for your post.

     

    Please also verify that if your client can contact your DNS server when your issue happens. To verify whether a client has basic TCP/IP access to the DNS server, first try pinging your DNS server by its IP address.

     

    If you could not ping your DNS server, it indicates that the source of the problem is more likely a network connectivity problem between the client and the DNS servers.

     

    If the DNS client can ping the DNS server computer, please also verify that the DNS server is started and able to listen for and respond to client requests. Try using the nslookup command to test whether your server can respond to DNS clients.

     

    Best Regards,

    James

    Tuesday, August 2, 2011 6:03 AM
  • Hi,

    you should verify the stability of the vpn connection. You don not mention how it set up, but if it losses connection and redials, that would explain intermittent issues.


    MCP/MCSA/MCTS/MCITP
    Tuesday, August 2, 2011 7:00 AM