win2k Serv dns/dhcp setup HELP!!!!

**friesr** · December 10th, 2003, 11:03 PM

I am setting up a domain at my house. I have setup dns, dhcp, and ad.

My network is connected to a netgear 614 router. I have disabled dhcp on the router and configured the server as dhcp.

I have added dns fowards to the two isp dns servers.

My xp boxes can pull ip's and see the intranet but they still can not access the internet.

I tried in dhcp options to add router and add the ip address of my router. This added default gateway to my dhcp settings on my clients but still do not have access to the internet.

What am i doing wrong????

**DVNT1** · December 11th, 2003, 09:17 AM

Can the client machines ping an Internet IP address like 216.109.117.66 ?

If yes, can they ping an Internet host name like www.yahoo.com ?

**friesr** · December 11th, 2003, 10:59 AM

Yes, I can ping the internet by ip but not by name. I can access the internet by name from the server. nslookup returns the ip of my server but says non-existant domain. I typed the ls command and it shows the ns. Found something that says that the nslookup problem could have something to do with reverse lookup but I thought reverse lookup was not necessary in my application. Plus, I am not sure how to set it up.

I have the nic in the server static with its own ip address as the dns server and the router as the gateway. The clients pull their ip and get server as it's dns server and the router as the gateway.

I am sure that it is a dns problem but every how to i have read says everything should be working.

**capybara** · December 12th, 2003, 11:17 AM

ttt i cant believe we dont have a fixed for this!

**friesr** · December 12th, 2003, 11:36 AM

Ok, I fixed it but is nothing like what the how to's say to set it up.

This is what I did... I disconnected the wan from the router(active directory kept saying there was a pdc already). Installed everything and authenticated all pc's to the domain.

In DNS, i deleted the root but instead of adding my isp's dns to dns fowarding, I went to dhcp and configured some options. I added router and entered the ip address of my router, and i added dns and entered the ip address of my server and the two ip's of the isp dns servers.

Everything works now with one exception. When i do nslookup, I still get non-existant domain. Does this have to do with reverse lookup? If so, how do i configure reverse lookup I have not found any help on this.

**DVNT1** · December 12th, 2003, 11:41 AM

Sorry, missed your reply to this thread.

Try running ipconfig /flushdns and ipconfig /registerdns

If still a problem, go to the DNS server and test the DNS query there. )DNS MMC, Properties of the DNS server, Monitoring tab, check both boxes the hit Test Now. Does it fail?

Edit - > I missed both replies.

AFAIK, Reverse lookup has nothing to do the the non-existant domain result.

**blubomber** · December 12th, 2003, 11:59 AM

Just to get some more info, when you type in nslookup, does it list the IP of a DNS server or does it come up with the error right away.

Have you done and ipconfig /all from the computer you are trying nslookup from to make sure it is getting all the correct DNS IPs? Have you tried restarting the DNS services on the server?

**friesr** · December 12th, 2003, 12:30 PM

it does list the ip of the dns server. When i run nslookup on the server it come up with local host and the 127.0.0.1 ip. When i run it from a client, i get the ip of the dns but non-existant domain.

When I installed win2k server, and ran the setup to make it the pdc, i set the nic with a static ip 10.10.1.1 and the dns to 127.0.0.1. I did not change this. The clients are dhcp and I had to set up dns in dhcp to send 10.10.1.1 and the two ip's of the ips dns servers for it's dns.

The odd thing i thought was that the I never told the server what the isp's dns servers were and it could access the internet by just adding the default gateway to it's tcp/ip settings but the clients could not access the interent untill i added the dns to the dchp settings and that dns fowarding would not work.

I am at work so I will not be able to do any testing untill i get home this evening.

**blubomber** · December 12th, 2003, 02:22 PM

Ok, the 127.0.0.1 is probably your problem. That IP address is the default windows gives for the NIC cards loop back (some thing lik that).

Your DNS servers IP should be the same as your pdc. 10.10.1.1. In your DHCP settings, change the DNS IP to 10.10.1.1, and in your DNS, keep your ISP's DNS servers as your forwaders. Once you get the changes in you DHCP, go to a client workstation and from the command line do a ipconfig /release, then ipconfig /renew, so that the client can get the new IP addresses. Then do an ipconfig /all to make sure that the DNS IP is the same as your PDC (10.10.1.1).

Then try nslookup. That should fix your problems.

**friesr** · December 12th, 2003, 02:45 PM

the pdc dhcp and dns are on the same machine. I will change that to 10.10.1.1 in the tcp/ip settings.

I did have it set to that but still did not make a difference.

I did origionaly have the server set up with the dns fowards to the isp dns servers.

Here is what i origional had setup:

Router ip is 10.10.1.2
1 server setup with ad, dns, dhcp
3 stations dhcp
1 print server dchp with ip in reserve

I set the servers nic to 10.10.1.1 subnet 255.0.0.0 gateway 10.10.1.2 and dns to 10.10.1.1. I set dhcp scope to 10.0.0.3 to 10.0.0.100 with router option set to 10.10.1.2. I deleted the root and added 24.221.30.4 and 24.221.192.5 to the dns fowards.

At that point, I could access the internet from the server.

I did an ipconfig /release and /renew on each of my clients as well as a flushdns and registerdns.

My clients could not access the internet but could see the server and the other clients by name and by ip.

I thought i might had messed up something during install, so i reinstalled the os and went through the configre server to set up the server as the pdc, dns, dhcp, etc...(that is where the 127.0.0.1 was added to the tcp/ip settings for the dns server) I tried to setup the foward but it still would not work.

That is when I had the idea to add the isp dns to the dhcp settings and remove the foward. Then everything started working.

During the first install and the second install, nslookup never worked.

Can you see a step i might of missed during settup?

**blubomber** · December 12th, 2003, 06:32 PM

What is the subnet of your router's internal IP?

Have you gone through your event logs on the server and checked for any DNS errors?

Under the properties for you DNS server in the DNS MMC, on the interfaces tab, have you told it to listen on all IP addresses or just the servers ip (10.10.1.1)? On the DNS serves in my corporate network they are set to listen on only certain IPs and not scan all IPs.

I think that the problem only lies with the DNS services.

Incase you have not seen this, here is a microsoft KB article on setting up DNS. It is fairly short and will hopefully give you some hints on where your problem is.

http://support.microsoft.com/default...b;en-us;172953

**friesr** · December 13th, 2003, 12:15 AM

The subnet of the routers internal ip is on my side is 255.0.0.0 on the isp side it is 255.255.255.0.

No, i have not gone through the logs. I am not sure were to look for them.

The dns server is setup to listen to all ip addresses.

Thanks for the link.

Here is exactly what I get on a client with nslookup:

*** Can't find server name for address 10.10.1.1: Non-existent domain
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 24.221.30.4: Timed out
Default Server: cocsmhns01.co.sprintbbd.net
Address: 24.221.192.5

I did make the changes you recommended but did not help. So i had to load the dns in the dhcp settings.

**friesr** · December 13th, 2003, 12:23 AM

I checked the link and that is for nt4 server i am running win2k server. Not sure if that will make that big of a difference.

**bailey** · December 13th, 2003, 01:15 AM

the IP 127.0.0.1 is the standard loop-back testing IP for all nic's
it factory built in

**blubomber** · December 13th, 2003, 01:56 AM

To get to the servers event logs, right click on my computer and click on manage. The window that opens will have an icon called Events. Double click on that and you should get 4 or 5 choices, one should be DNS.

What did you call your domain? Is there anything listed in you DNS? If you go into your forward lookup zone, is the next level your domain? Is there anything listed in there? Are your client IP's listed?

That link was just for a quick look. You should be able to find alot of DNS info in your servers help file or the MS knowledge base. But, if having your clients us your ISP's DNS servers work, then that could be the way to go until you get your DNS working. Just make sure that your sever is looking there too.

**friesr** · December 13th, 2003, 01:18 PM

The dns log has no errors

Here is a screenshot of my dns:

http://home.earthlink.net/~friesr/dns.bmp

I really want to thank you for the help you have given me so far. It is really frusterating that from everything i have read that this should be working correctly but of course it is not... might set up remote desktop if that is an option...

**friesr** · December 13th, 2003, 04:25 PM

found this at M$ site:

*** Can't find server name for address w.x.y.z: Non-existent domain

This error occurs when there is no PTR record for the name server's IP address. When Nslookup.exe starts, it does a reverse lookup to get the name of the default server. If no PTR data exists, this error message is returned. To correct make sure that a reverse lookup zone exists and contains PTR records for the name servers.

followed the instructions and wala! nslookup works!!!!

Now to see if dns fowards work... will be back soon!

**friesr** · December 13th, 2003, 04:29 PM

Well there you go, problem solved. DNS foward work now.

looks like dns reverse lookup is necessary after all.

blubomber - Thank you very much for your help!