Re: Some DNS server names will not resolve using internal servers
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Mon, 27 Nov 2006 14:31:48 -0600
"Brillmike" <brillmike@xxxxxxxxx> wrote in message
news:A5F49CB3-FA14-4EFA-8C96-F587A2788AC2@xxxxxxxxxxxxxxxx
We have two W2003 AD/DNS server replicating. From our client XP machines I
can go to support.microsoft.com but not WWW.microsoft.com. I can go to
WWW.gsionline.com but not LOGON.gsionline.com. We use forwarding so all
internal machines are pointing to our internal DNS server. We do not seem
to
have any issue with any other server names, just WWW for microsft.com and
LOGON for gsionline.com.
Ok, then somewhere those (2) records are being
overridden or picked up (hosts file, explicit zones,
trojan/virus, etc.)
What to do?
When you face such issues the first thing to do is
to test each DNS server involved EXPLICITLY
(from the clients):
nslookup www.Microsoft.com ISP.DNS.Server.IP
nslookup www.Microsoft.com Internal.DNS.Server.IP
(Do the first one for EACH and EVERY internal DNS
server.)
If both of these work, then likely you have something
(screwy) in a local Hosts file (%systemroot%\system32\
drives\etc\hosts). Such MIGHT be put there by a
malicious program or user who hates MS.
BTW: if i set the client to bypass the local DNS servers and resolve to
the
DNS server we forward lookup to, then i can resolve the addresses.
You must never do this (except for test purposes) --
internal machines must use STRICTLY the internal
DNS servers which can resolve both internal and
external names.
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
Thanks, Mike
.
- Follow-Ups:
- Prev by Date: Re: server2003 doesnt Contact Alternate DNS server
- Next by Date: Re: Cannot ping but can browse!
- Previous by thread: DNS Configuration
- Next by thread: Re: Some DNS server names will not resolve using internal servers
- Index(es):
Relevant Pages
|
|
