Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Server location move.  DC DNS no longer working

Posted on 2012-12-28
7
Medium Priority
?
271 Views
Last Modified: 2013-12-01
I have a tough issue.  I have a existing DC that is part of a WAN, and was moved to a new office.  It can no longer see the internet.  The firewall (Cisco ASA-5505) was changed to use the new internet provider IP, but the server (DC) can't see past the firewall.  DNS was configured on this DC years ago and has been working as it should.  I have not reconfigured the Site to Site VPN connection to the other offices yet, but this shouldn't be an issue, as they have been offline before.

The internal firewall (gateway) IP address didn't change (10.0.14.4).  Server IP is 10.0.14.2.   I deleted the forwarders and readded.  I added new ones from openDNS.  I cleared cache, and restarted the DNS services.  Rebooted the server.  Changed the ports on the switch.

I can see the internet from the PC's when I manually enter a DNS address outside the network.  ie. 4.2.2.2 or 8.8.8.8.  When I use the DNS address of the server (DC) it fails.  With the internal DNS address in place, I can resolve internal DNS names, but not external ones.  I can ping the server using the IP and DNS name from the PC's  

When I use the NSlookup I get "timed-out"

Default Server:  dc01.domain.local (local DC)
Address:  10.0.14.2 (correct IP)

> google.com
Server:  dc01.domain.local
Address:  10.0.14.2

DNS request timed out.
    timeout was 2 seconds.
*** Request to dc01.domain.local timed-out


Server is:

Windows 2003 R2 SP2.  4 GIG ram.

I did a route print and the results are below.

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 1d 09 ef f3 00 ...... Broadcom NetXtreme Gigabit Ethernet
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0        10.0.14.4        10.0.14.2     10
        10.0.14.0    255.255.255.0        10.0.14.2        10.0.14.2     10
        10.0.14.2  255.255.255.255        127.0.0.1        127.0.0.1     10
   10.255.255.255  255.255.255.255        10.0.14.2        10.0.14.2     10
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
        224.0.0.0        240.0.0.0        10.0.14.2        10.0.14.2     10
  255.255.255.255  255.255.255.255        10.0.14.2        10.0.14.2      1
Default Gateway:         10.0.14.4
===========================================================================
Persistent Routes:
  None

Thank you in advance for any help rendered!
2012-12-28---PPDWV-DC01-Forwarde.PNG
0
Comment
Question by:JackAitken
7 Comments
 
LVL 13

Accepted Solution

by:
upalakshitha earned 668 total points
ID: 38728494
can you ping to gateway ip from server?
Server internet traffic may block at firewal. Isn't it ?
0
 

Author Comment

by:JackAitken
ID: 38728510
I can ping the firewall from the server.  No firewall rules that block outgoing traffic.
0
 
LVL 4

Assisted Solution

by:Haslerct
Haslerct earned 668 total points
ID: 38728916
To narrow down the issue I suggest do a quick test:
1. On your dc, change the DNS direct to the external dns server.
2. Do a DNS query test to external domain (eg: google.com) and see it is able to resolved it.
0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 

Author Comment

by:JackAitken
ID: 38729508
Changed the DNS to 4.2.2.2 and it doesn't resolve it.  I also tried using the IP address of a web site and it was not able to connect.

I can connect to the firewall and edit or view the settings from the server.
0
 
LVL 4

Expert Comment

by:Haslerct
ID: 38730500
If your gateway set correctly and still able to resolve DNS and not able to connect using IP, it is quite clear that something is blocking it. Check the fw rule and routing. Do a tracert and see if it route correctly and stop where.
0
 
LVL 27

Assisted Solution

by:DrDave242
DrDave242 earned 664 total points
ID: 38733142
Pick an IP address on the other side of the router (like 8.8.8.8 or 4.2.2.2) that you are able to successfully ping from a client, and see if you can ping it from the server.  Also, use a client to resolve the IP address of a site you can browse to, and see if you can browse to that IP address from the server.  These tests will help determine whether all traffic from the server to the outside is being blocked somewhere, or if only DNS traffic is affected.
0
 

Author Comment

by:JackAitken
ID: 39687864
I ended up replacing the server and firewall.  Couldn't figure out why it wouldn't connect
0

Featured Post

Lessons on Wi-Fi & Recommendations on KRACK

Simplicity and security can be a difficult  balance for any business to tackle. Join us on December 6th for a look at your company's biggest security gap. We will also address the most recent attack, "KRACK" and provide recommendations on how to secure your Wi-Fi network today!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

IF you are either unfamiliar with rootkits, or want to know more about them, read on ....
In this article, the configuration steps in Zabbix to monitor devices via SNMP will be discussed with some real examples on Cisco Router/Switch, Catalyst Switch, NAS Synology device.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …

876 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question