DNS lookup is failing

  • Thread starter Thread starter Paul
  • Start date Start date
P

Paul

I am using a WINDOWS 2000 server as our DNS server for
both active directory and Internet name resolution.
Everything works fine except that late last week Browser
request to WWW.MSN.COM or WWW.MSNBC.COM or HOTMAIL
stopped working. Ever other site is reachable except
these. When I ping www.msn.com the returned address is
127.0.0.1! Loopback address! I have set a PC to use a
public DNS server and these address are then reachable
from inside the LAN but when using our DNS server these
address are unreachable. Any ideas on how to resolve this?

Thanks
Paul
 
Are you using forwarders on your W2k DNS server, with all clients & servers
pointing only to that server's IP address for DNS?

Do you have a good firewall in place to protect your network, run Windows
Update regularly on server & workstations, good antivirus on the server and
workstations? The fact that you're getting a reply from the internal
loopback adapter IP address is a bit worrisome -
 
P> Any ideas on how to resolve this?

Yes. Either keep up with the service packs or manually turn on the "Secure
cache against pollution" option.
 
In
Paul said:
I am using a WINDOWS 2000 server as our DNS server for
both active directory and Internet name resolution.
Everything works fine except that late last week Browser
request to WWW.MSN.COM or WWW.MSNBC.COM or HOTMAIL
stopped working. Ever other site is reachable except
these. When I ping www.msn.com the returned address is
127.0.0.1! Loopback address! I have set a PC to use a
public DNS server and these address are then reachable
from inside the LAN but when using our DNS server these
address are unreachable. Any ideas on how to resolve this?

Thanks
Paul
Click to expand...


Can we see what's in your HOSTS file?

Thanks.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
unlikely to be a hosts file issue, since seems to work fine with pointing
against public DNS Server.
"Ace Fekay [MVP]"
 
In
Krish Sundaresan said:
unlikely to be a hosts file issue, since seems to work fine with
pointing against public DNS Server.
Click to expand...


I was assuming that since I've seen the QHOSTS virus cause that. Then maybe
Secure Cache Against Pollution setting may help. But I am "assuming" the
poster has the machine upto SP4 (which sets that by default).

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
In
Krish Sundaresan said:
unlikely to be a hosts file issue, since seems to work fine with
pointing against public DNS Server.
Click to expand...


If there's a firewall blocking TCP 53, then that may also cause the issue
(assuming that the domains they are trying to get to are returning a
response larger than 500 bytes).


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Please correct me if am wrong, but doesnt cache pollution protection apply
to the DNS Server? I wasnt aware of cache pollution protection for the
client?

"Ace Fekay [MVP]"
 
In
Krish Sundaresan said:
Please correct me if am wrong, but doesnt cache pollution protection
apply to the DNS Server? I wasnt aware of cache pollution protection
for the client?
Click to expand...

Just for DNS. After re-reading my post, I should have separated my thoughts.
I was just thinking that Secure Cache will protect any resolution requests.
As for the client side wtih the QHOSTS virus, antivirus will protect from
that (hopefully if upto date, etc).

Sorry if I skewed that... :-)



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Back
Top