Avatar of JackAitken
JackAitken
Flag for United States of America asked on

Server location move. DC DNS no longer working

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
Windows OSNetwork OperationsDNS

Avatar of undefined
Last Comment
JackAitken

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Imal Upalakshitha

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
JackAitken

ASKER
I can ping the firewall from the server.  No firewall rules that block outgoing traffic.
SOLUTION
Haslerct

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
JackAitken

ASKER
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.
Haslerct

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.
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
SOLUTION
DrDave242

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
JackAitken

ASKER
I ended up replacing the server and firewall.  Couldn't figure out why it wouldn't connect