Networks

Ask something
Question Locked

Server 2003 DNS issues

0 helpful
9 replies

by rbelt_74

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am running Server 2003 and have configured DNS to make sure it is working before I make the server a Domain Controller. DNS is set up with reverse look up and added the A host. I can open the web browser and the dns forwards my request to the Public DNS ip addresses so it resolves the names but only on the server. On my workstation if I configure the DNS ip to my server and run NSlookup it can not find the server it says server unknown. I can not browse any sites. I have even gone as far as putting a cross over cable between my workstation and the server. any ideas????

9 replies

by dhanushkapg

Did u configure DNS as forward order. Because some times it would be the reason. and other think u configure root-hint properly. check u can ping to dns server.

This is just because i havent much more experience regarding DNS

by rbelt_74

I have the forwards set.

I can ping the server with the ipaddress

root hints said it could not automatically update them but they are there in the zone.

by dumphrey

on the workstation is not checking the proper domain information for the server.
nslookup
hosta

vs nslookup
hosta.domaina.local

If both machines are in the same domain, nslokup will just work. After that setting up forwarders etc should be a snap.
Try using the server ip in the nslookup instead of its host name. If the reverse dns is correct, it will give you the hostname, and you can safely assume forward resolution will work as well.

by rbelt_74

OK its wroking now but let me clairfy what I had to do for anyone else.

Keep in mind I was just running DNS and not Active Directory.

I uninstalled DNS services

Reinstalled using the install wizard but used the common install and not single component. This installed active directory and DNS at the same time. THis was the whole problem. It really wanted active directory running to work. all is good now.

THank you everyone for your help.

by sgt_shultz

can you ping the gateway? can you browse sites by ip address? can you see any other computers on your network?

by rbelt_74

I can ping the gateway.

nslookup with the ip address of yahoo.com comes back with the same error.

ca't find server name for address 10.1.10.149: Timed out
then the secondary server finds it

nslookup hosta provides the same error.

but if I do this on the server it works.
All services are running on the server except I do not have this server set up as the domain controller or have active directory running yet. I wanted to make sure DNS worked before I made it a domain controller.

by rbelt_74

I can also ping the server name Jaysecs1 and the ip address and I do get replies... I also tested the nslookup from other workstations that also run xp but I get the same time out response from them.

by cg it

if your workstation is set to use your DNS for name resolution and you send a request for a web page such as yahoo.com to your DNS server and it does not forward that request to root hint servers, then you'll get an error.

Check your root hint servers in the forwarders tab in DNS.

If I remember correctly, this is also a problem if you use a FQDN for your network and setup DNS using a FQDN. Microsoft recommends you use a non FQDN for your DNS name when setting up DNS for Active Directory. example use the .local extension rather than .com or .net

This discussion is closed to new replies.