DNS not working, Ping works fine

[mattmc97]

Hello all.

I have just switched over my work network from public IP addresses to a private range 192.168.x.x and now I cannot get DNS to allow internet access to the connected computers connected to the server. I can get on the internet from the server and I can ping the numerical value of Yahoo from the connected computers, so it seems to be a DNS issue.

I also used NsLookup and it gave me an error saying request timed out - Can't find server name for 192.168.208.1

On Windows 2000 server event log, I get a NETLOGON error in my event viewer that states:

Dynamic registration or deregistration of one or more DNS records failed because no DNS servers are available.

It was working on Wednesday but I rebooted the server this morning because we had some computers that would not connect to Exchange server and now it doesn't work.

I have a windows 2000 server book and it talks about installing zones and it talks about the primary zone but on my server it appears to have the Active Directory Integrated as the current running zone. Which one do I need?

Is there a good website that explains what all this does?

thanks in advance.

mattmc

 

[search66]

http://support.microsoft.com/default.aspx?scid=kb;en-us;259277

Give this a shot.

 

[mattmc97]

thanks for the response, but that did not work.

I stopped and restarted the Net Logon service and it still doesn't work.

any other ideas???

mattmc

 

[aco636]

Does you private DNS server have a public DNS Server set up in the TCP/properties tab?
I presume all clients refer to the private DNS and the then should be refered to the public DNS. Have you considered a proxy server?
Regards ACO

 

[saddatabid]

In your Windows 2000 Server confirm that under Advanced TCP/IP settings your W2K DNS Server'S IP address exists. Also in your DHCP add your local DNS server as primary and other Internet DNS servers as secondary.

At command prompt type:

ipconfig /all

examine this.

STEP 1

ipconfig /flushdns (clears dns cache)
ipconfig /registerdns (updates dns records)

now ping servername.mydomain.com (FQDN)

Is this okay? And if so ping FQDN from clients. If need be try step 1.

Examine Event Viewer > DNS and report any errors with EventIDs.

Let me know how you get on.

 

[saddatabid]

mattmc97,

When you ping a workstation you're not actually using DNS but instead you use broadcast. for example if i ping a workstation named alpha then i am sending a broadcast on the network (to a switch) for a response from alpha. However, if i ping alpha.mydomain.com then i am definitely using DNS. I have read this in an MCSE book some time ago.

 

[zoeythecat]

Just to add to Saddatabid comments:

(1) Check the TCP/IP Properties, DNS Tab on all your
servers. You need to make sure you have the correct
IP Address of your DNS Server. If the IP Address
has changed then you need to change the IP Address
here. The main DNS Server needs to be pointing to
itself. The rest of your servers need to be
pointing to this same IP Address
(2) Check the TCP/IP DNS Properties on the rest of your
servers
(3) In DHCP check the 006 and 015 DNS options. Make
sure 006 has the correct DNS IP Address
(4) To resolve the issue with workstations connecting
to Internet open up your DNS Server, go to the
properties of the server name and check the
"Forwarders" tab. You need to have the IP
Address of your ISP to allow your clients to
access the Internet.
(5) If your MX record has changed you need to update
this in DNS also.
(6) After doing these steps run the NSLOOKUP on
each of your servers to make sure DNS looks good.

 

[bguerra904]

I have seen and done myself where you install DNS as a root server. What this means is your DNS server believes that it is the ultimate athority for all DNS requests. If it doesn't know the answer then it thinks it doesn't exist. You can check for this by find a single dot in your DNS console.

If your issue has been solved please post your solution for others.

 

[geocodyrgia]

Id say zoey hoit the nail on the head. $20 says its your forwarders....

Chad

 

[mattmc97]

Thanks everyone for the replies.

It may have been several things.

1. I did not have my domain server pointing to itself.

2. I did not have the forwarders set to forward to external IPs in DNS.

3. I did not have the four _mscds, _sites,_tcp,_udp folders under my domain under forward lookup zone for my active directory. (which was causing other errors I believe)

4. It appears that the only computers having problems were the XP where they were automatically detecting the gateway and DNS server. I left the "obtain Ip from server" alone but entered my gateway and dns server and all is working now!

thanks.

mattmc