Computing.Net > Forums > Windows 2000 > DNS Problem

Computing.Net: Over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to sign up now, it's free!

DNS Problem

Reply to Message Icon

Original Message
Name: Danny
Date: February 16, 2001 at 12:46:53 Pacific
Subject: DNS Problem
Comment:

I have a DNS problem with my w2k using a DSL connection. I tested it on a WAN directly connected and still being bogus. I can pull from ip and sometime by domain. However it stuck on specific domain names, and don't like relative URLs within html page... I tried to update with SP1 and it's not better!
The problem is more likely a reverse mapping bug. the box is not able to see the DNS server located on the LAN or any external DNS servers! Look like it have problem to resolve PTR (reverse mapping).

In Nslookup i do:
server x.x.x.x (where x is ip address)
and it resolve corectly the server's name.
As i test, i ask to resolve itself, and it failed!!

A second test: I set the same ip as default dns server, i flush the cache and re-register dns... i return in nslookup, and it is no more able to find the server's name...

As i said some domaine are not able to resolve at all, but in most case i think the problem is mainly with reverse mapping.
Sometime, when asking for a html page i see the "Waiting for reply...", and still waiting forever...

Someone have new info about this major w2k's bug??

NOTE: This computer was running very fine!!! this is not a newly configured pc


Report Offensive Message For Removal


Response Number 1
Name: MneMonix
Date: February 16, 2001 at 19:23:31 Pacific
Reply: (edit)

What's the actual problem ? You can Browse the internet by IP but not by (FQDN) fully qualified domain name ?

If this is the issue, the DNS Server is not Being reached. What are you trying to check with NSLookup ?

If you goto a DOS prompt and type NSLookup, then type ? and press enter you'll get all the commands. Server www.xxx.yyy.zzz just says t ouse that IP as the resolution server for NSLookup, if that IP is not reachable, that's a seperate issue than the IP is reachable but not resolving.

How many DNS Server are you using ? Are you registered to be your OWN DNS Server ?

How is your DNS Search order configured. The ISPs DNS server (if you are NOT your Own DNS Server) should be the only DNS server in your configuration.

If you are Your Own DNS Server, then the DNS Server search order should be Your DNS IP, then the ISP DNS IP as a secondary.

Now, if you are your OWN DNS Server and the Windows 2000 DNS Service os NOT configured correctly, that changes a lot of the, If this and if that. Sorry to be so Vague, but I'm not sure how you've confgiured your particular network..


Report Offensive Follow Up For Removal

Response Number 2
Name: Tony J
Date: February 17, 2001 at 10:33:58 Pacific
Reply: (edit)

Hi..if you have a static IPs and trying to set up your own DNS server...I will help you to set them up.

Tony J
P.S. Just did not understand your problem...!!!


Report Offensive Follow Up For Removal

Response Number 3
Name: Danny
Date: February 19, 2001 at 07:28:59 Pacific
Reply: (edit)

This is not a dns problem, this is a resolver corruption problem. The dns server i use has nothing to do with the problem. I tried with several dns servers anyway for testing purpose.

Most of domains resolve correctly, but some others don't anymore. I'm seriously suspecting a permanent resolver corruption due to a specific dns transaction error. This error may be caused by a routing misconfiguration at the ISP. After that if you try to connect to an other ISP,LAN, WAN,... there is no way to get it to work.

The resolver is completly incoherent. I know that zonealarm (firewall) users have a software patch that fix the problem. But i just need to know how this patch fixes this win2k bug. Someone told me that a SP2 is available in beta version to fix this problem, but did not find it yet.



Report Offensive Follow Up For Removal

Response Number 4
Name: Dave
Date: June 13, 2001 at 16:55:22 Pacific
Reply: (edit)

I am having a similiar problem on:

I am running windows 2000 workstation on 4 systems. I have my Cisco 675 plugged into a switch. I use DHCP on the Cisco to assign ip addresses to my machines.

They can all hit the internet and normally work ok. Once in a while, actually its been happening alot, when your surfing the web, it will all of a sudden time out and not be able to find the DNS servers. I can telnet into the router and ping the dns servers and from a dos prompt can ping the dns servers by ip address. At the time I cannot get to the DNS servers, I try a nslookup and it cant fiund them. I try changing to another server and it cant find them. But I still can ping the ip addresses of these DNS servers.

Ok here is another weird thing. On one machine I can drop to a dos prompt and do a continuous ping to a ip address and it replys no problem. Now if at the same time I go to the next machine and do the same ping, it timeouts! What DA?!?!?!?!?!!??!

Please email me if you know a solution.
zzCyanide@hotmail.com
Dave

ps. I am running CBOS Version 2.2.0.000 of the Cisco OS.


Report Offensive Follow Up For Removal

Response Number 5
Name: pradeep saluja
Date: March 4, 2002 at 02:49:34 Pacific
Reply: (edit)

Dear All,

I am facing the same problem.

We have windows 2000 advanced server SP2.We have defined 4 DNS addresses of our ISP since we donot have our own DNS server.The problem is that name resolution doesnot work for some time.But if we change the DNS address order or reboot the system,it starts working for few hours and then stops all of a sudden

PLEASE SOMEONE HELP TO SOLVE THIS PROBLE.ALSO,IF SOMEONE CAN MAIL ME AT PRADEEPSALUJA@YAHOO.COM


Report Offensive Follow Up For Removal







Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows 2000 Forum Home








Do you own an iPhone?

Yes
No, but soon
No


View Results

Poll Finishes In 7 Days.
Discuss in The Lounge
Poll History




Data Recovery Software