Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
I'm hoping someone knows an answer for the cause of this... I've read the problem in various forums and even on this newsgroup, yet noone seems to have resolved it, or they didn't say they did!
In two instances, I have identical setups that consist of the following:
Windows Server 2003 machine acting as the PDC doing DHCP and DNS (AD Integrated).
Occasionally (more often than not, at least 4 times in three days) the DNS server just stops working entirely. There are two ways to get it working again: 1) restart the PIX. 2) Restart DNS.
Either one will fix the issue and it will resolve once again.
The PIX is a 515E running 6.3(5) -- so I'm leaning away from it being an EDNS0 problem (udp pkts larger than 512bytes). I've read of various people having the same problem with DNS hosing up randomly... has ANYONE found a fix for this yet?
What does the DNS event viewer say?
Looks like you have some kind of config conflict between the pix and ms dns. Pix is your gateway right?Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.
0 
Are the workstations pointed to the gateway for dns or your server?
seems strange rebooting the gateway would fix resolution. That makes me think its doing the resolution not your dns server.
who is providing dhcp if doing dhcp?
Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.
0
The DC is also doing dhcp. it's acting as the pdc, dhcp server, dns server AND exchange server.
All workstations are pointed properly at the dns server for resolution. It's an odd situation. I can paste some configs later in the evening tomorrow for review. But the configs should be fine... :(
0
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.25.66
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.25.1
DHCP Server . . . . . . . . . . . : 192.168.25.5
DNS Servers . . . . . . . . . . . : 192.168.25.525.1 would be the PIX, 25.5 would be the PDC, DHCP, DNS and Exchange server.
0
Looks perfect.
How are you determining its name resolution? Wksts stop connecting/logging in?
When this happens can you ping the server and/or gateway?
Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.
0
Server and gateway are pingable, yes. It seems to be only outside resolution that stops working. We are leaning towards the possibility of it being an error with the PIX, and have opened a case with CISCO and are logging all of the logs on the PIX with a syslog daemon. We are currently only logging in debug mode, which will only give us errors and specific information about circuit build/tear-down. Perhaps we will see the error in there. I was hoping someone would know what the issue is as this seems to have happened to quite a few people. I've found about five posts in the past few months about this on here, all still remaining a mystery.
0
We are having the same issue on our W2K3 Servers with DNS AD Integrated with DHCP installed. Any given time one of the servers DNS just stops responding although the service shows still running. Restarting the server service fixes the problem.
Adell
0
Hello Adell,
Did you ever get this resolved? I have the same issue on a W2K3 server where the DNS stops working but there are no events in the logs. If I restart the DNS service it will work for a nother week.
-Dan
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
