Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DNS is unable to resolve target name for few websites

Status
Not open for further replies.

UnknownEntity

Technical User
Jun 15, 2006
75
GB
Hi,

I'm having an issue with a particular website "x" loading on a client PC. All other websites work fine in terms of loading. I have tested this website "x" and other machines outside the domain and it works fine.

On the windows 2008 dns server itself I have cleared cache and flushed with ipconfig /flushdns, but when I tracert "x", it reaches the target name? All other .co.uk sites load easily and navigating to "x" website on server loads as well.

Why is it not loading on the client systems? Any help is greatly appreciated. Thx.

Drakul.

 
More information, such as the exact error would be helpful.

From what you have provided, if a tracert is able to establish the final connection then it is probably not a true connectivity / network problem but rather some form of configuration problem. The tracert indicates that ICMP traffic is able to get through but this doesn't mean that higher level protocol traffic will be able to. It sounds like there may be something about the site that the client's browser doesn't like. It could also be that traffic is being blocked by another application on the port that is being used.
 
Thx for reply Noway2,

This is the message I get on a client PC IE web browswer connected to the windows 2k8 AD/DNS server >

"You were looking for "website x" but that domain is not on this server. Apache/2.2.10(fedora) server at hash.vern.com port 80."

I have no idea where this has come from? The windows 2008 DNS server is setup as follows >

Windows 2008 DNS/domain controller SOA is at 10.25.0.2 Primary DNS addy is 127.0.0.1 Secondary DNS addy is 10.25.0.2.

I also have terminal server (10.25.0.3) running DNS with primary DNS as 10.25.0.2 and secondary as 10.25.0.3.

Forward lookup zones for 10.25.0 range for this domain and reverse lookup zone for same range on same domain. Can i give any more data to help?

We dont run apache fedora or anything of the sort, perhaps its pointing to a root server with issues? This is strange, any guidance? Thanks.

Drakul.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top