• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1221
  • Last Modified:

CompanyWeb not resolving

Hi,
I have just installed an SBS 2003 Server, and DNS appears to be working perfectly, apart from the fact that companyweb often does not resolve. It does for 20 minutes, then won't for an hour, and so on and so forth.
During the times that its down, it cannot even be pinged.
The DNS set up has a CNAME record that points back to servername.domain.local, which I believe is correct.
Any ideas?
0
PeteKaegi
Asked:
PeteKaegi
  • 6
  • 3
  • 3
1 Solution
 
PeteKaegiAuthor Commented:
PS at the times it doesn't resolve, it doesn't even resolve on the server itself.
0
 
harris_cCommented:
Try hardcoding the IP

hec",)
0
 
PeteKaegiAuthor Commented:
In the CNAME?

I actually did try adding an entry to the HOST table, just out of interest, and on the server at least, it solved the issue. But I'd prefer to understand why it might be happening, if possible, and solve it correctly...
0
Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

 
btdownloads7Commented:
You shoudl check the server logs to see what's happening during the times that it won't accept connections. You should also try to physically log into the server when it seems to be down and try to get online -- maybe the server is actually losing a connection.

If the server seems to have no problems, open the command prompt on any client maching, and run "ipconfig /all". See what DNS servers are listed and in which order -- it may be that the DHCP settings are messed up and are feeding the wrong DNS server to the clients.
0
 
PeteKaegiAuthor Commented:
Thanks for your responses.

The server is definitely "up" at the times when the companyweb is down.

As for DHCP, the DNS settings on the client are correct. The primary DNS server is the IP of server itself, with secondary being the IP of the router (this is how I've done it in 20 other SBS sites). The clients resolve on the domain perfectly. Again, just out of interest, I removed the secondary DNS server (router IP), but it made no difference.

Let me reiterate that only the "companyweb"  cannot be pinged intermittently; All other hosts on the network can be pinged/resolved perfectly, including the server itself (apart from using CNAME companyweb).

0
 
btdownloads7Commented:
Just to clarify, when you can't ping "companyweb", you can still ping "servername.domain.local", correct?

and when you do ping "companyweb" ,what IP adress does it say it's pinging? please check both when "companyweb" is resolving and when it's not.
0
 
PeteKaegiAuthor Commented:
Yes, that's correct, when I CAN'T ping "companyweb", I can still ping "servername.domain.local"

When companyweb can be pinged, it replies from 192.168.100.121, which is actually the server's RRAS address (the primary IP is 192.168.100.1). But RRAS was added after this issue began, so I don't think its implicated.

When companyweb can't be pinged, it doesn't resolve at all, so there is no IP address to mention.
0
 
btdownloads7Commented:
Are there any other CNAME records defined in DNS? Can you ping any of those when "comanyweb" is down?
0
 
harris_cCommented:
"I actually did try adding an entry to the HOST table, just out of interest, and on the server at least, it solved the issue. But I'd prefer to understand why it might be happening, if possible, and solve it correctly..."

It seems that it fails to resolve the DNS.  Can you try flushing the DNS at the server?  

Sometimes the error is caused by some servers using the same IP.

Can you also try    tracert during up and down.

hec",)
0
 
PeteKaegiAuthor Commented:
Looks I may have resolved the issue, will monitor overnight and let you know.
0
 
harris_cCommented:
What did you do?
0
 
PeteKaegiAuthor Commented:
Hi,

Changing the DHCP to give the DC out as the only DNS server to clients seemed to resolve the issue. Its strange, because as I said, I have always had the router as a secondary DNS.

Thanks for your suggestions.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 6
  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now