DNS Issue on 2003 DC

Dell / Poweredge 1600sc
January 10, 2011 at 06:27:42
Specs: Server 2K3
Hi all,

I'm running two servers, both 2003 R2 one is a

(A) File and Print server 192.168.1.100

(B) AD, DNS, DHCP 192.168.1.2

Gateway is 192.168.1.1

Server A is also a backup DNS server.

We had a power cut over xmas and I have been having issues with DNS ever since.

Server A is fine. It's pointing to itself for DNS, and I can ping loopback, gateway, external.

Server B is the problem. This is the primary DNS server on our network, and is having connectivity issues. Cannot ping the gateway, or anything external, but can ping internal machines. Recursive queries are failing in tests, and nslookup is saying ''Can't find server name for address 192.168.1.2''.

I have tried opendns to get out, but no luck. Can anyone suggest some troubleshooting steps to get this sorted?

Bosey


See More: DNS Issue on 2003 DC

Report •

#1
January 10, 2011 at 07:58:27
post the results of an ipconfig /all from server b for review

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#2
January 10, 2011 at 08:12:02
Windows IP Configuration

Host Name . . . . . . . . . . . . : moatebs2
Primary Dns Suffix . . . . . . . : MBC.IT
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : MBC.IT

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : mbc.it
Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connectio
n
Physical Address. . . . . . . . . : 00-30-48-B8-34-B9
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.2
192.168.1.1

Bosey


Report •

#3
January 10, 2011 at 12:20:56
"WINS Proxy Enabled. . . . . . . . : Yes"

normally set to no. why set to yes?

Recommend not listing gateway as a dns server.

"Cannot ping the gateway, or anything external"
This would indicate a firewall issue if you can't ping the gateway ip

External can mean you don't have dns properly configured. ISP dns ips listed in the forwarders [not to be confused with forward lookup zone]?

From server b do a tracert yahoo.com and post the results

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

Related Solutions

#4
January 11, 2011 at 02:33:54
I believe I have found the problem here, when I came in this morning there was an IP conflict message at welcome screen. I believe one of our 200 machines or 50 external laptops have the same static IP as server B..

Bosey


Report •

Ask Question