wierd dns issue

  • Thread starter Thread starter Erik Cominolli
  • Start date Start date
E

Erik Cominolli

PDC has correct dns setup on nic card.
other pc's use pdc as dns server on nic card.
pdc can access all websites ie. microsoft.com
other pc's can get most websites except sites from larger
corporations like microsft, yahoo, symantec.

pdc can see all these. Is this a dns issue?

When I put in the "actual" dns servers into the pc's, pc
can see all websites. What is pdc doing wrong?
 
Erik,

I think that we might need some more information from you. I ass/u/me that
you have a WIN2000 Active Directory environment. You used the term PDC
which typically is a WINNT 4.0 term.

On your Domain Controller, you have in the TCP/IP configuration settings a
unique, static IP Address and the appropriate subnet mask as well as the
default gateway and in the DNS portion ( the bottom half ) you have it
pointing to itself ( that unique, static IP Address ). That should be it.
Please do not have any of your external ISP DNS Server IP Addresses listed
here - or anywhere else for that matter ( except, of course, in the
Forwarders tab in the DNS MMC ).

In your internal DNS ( running on your Domain Controller??? ) you should
make sure that you have a Forward Lookup Zone and a Reverse Lookup Zone (
although the RLZ is most probably not involved with your problem at all -
so if you do not have one do not worry about it for the moment ). The FLZ
should have the four subfolders ( _msdcs, _sites, _tcp and _udp ) underneath
the 'yourdomain.com' zone. Please make sure that this name is spelled
correctly ( probably is ).

Also, you have to make sure that you have deleted the "." zone in the FLZ -
which you clearly have or you would not be able to get out to the Internet.

How are your clients computers receiving their IP Address leases? via DHCP
from the Domain Controller? via DHCP on the Firewall or some other network
device? Are all of your clients receiving correct 'scope' information?
Probably, but look at my last question below.

Have you tried to do an 'ipconfig /all' on your client computers? I am sure
that you have. Make sure that they all have the same subnet mask, dfg and
internal DNS information.

What happens if you do an 'ipconfig /flushdns' on one of the problem client
computers? Are you then able to get to some of those problem web sites?

I am sure that you have looked at all of this already. I just want to make
sure that we have covered the very basics.

Also, what OSes do you have on the client computers? WIN9x, WINNT, WIN2000,
WINXP?

Have you tried nslookup? This is the default DNS troubleshooting tool....

Curious about one of your statements. What do you mean by "when I put in
'actual' DNS Server into the pcs, pcs can see all web sites"?

Cary
 
Back
Top