DNS server working but not resolving name

[mujeeb]

Dear!
Using win2k sp4 got problem two days ago.DNS stop
resolving name.Nslookup not working even on DNS server.
Nothing is there in DNS OR secrurity even logs.
DNS services(client and server)runing smoothly on server.

Quick reponse will be great pleasure for me

 

[Ace Fekay [MVP]]

In

Dear!
Using win2k sp4 got problem two days ago.DNS stop
resolving name.Nslookup not working even on DNS server.
Nothing is there in DNS OR secrurity even logs.
DNS services(client and server)runing smoothly on server.

Quick reponse will be great pleasure for me

242906 - DNS Request Timed Out Error Message When You Start Nslookup From a
Command Line:
http://support.microsoft.com/?id=242906




--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[mujeeb]

May be i was unable to explain.
DNS service is running and i can restart it without any
error.No error is logged in event log.

But dns is not working on clients.
When i try to use NSLOOKUP it gave me following message

*** Can't find server name for address 172.30.102.55: Non-
existent domain
*** Default servers are not available
Default Server: UnKnown
Address: 172.30.102.55

172.30.102.55 = DNS server ip address

Hope you will understand now

 

[Marc Reynolds [MSFT]]

See 242906 "DNS Request Timed Out" Error Message When You Start Nslookup
From a
http://support.microsoft.com/?id=242906

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Kevin D. Goodknecht [MVP]]

In

May be i was unable to explain.
DNS service is running and i can restart it without any
error.No error is logged in event log.

But dns is not working on clients.
When i try to use NSLOOKUP it gave me following message

*** Can't find server name for address 172.30.102.55: Non-
existent domain
*** Default servers are not available
Default Server: UnKnown
Address: 172.30.102.55

172.30.102.55 = DNS server ip address

Hope you will understand now

In addition to what I replied in your other thread on this same subject,
this message does not affect the DNS servers ability to resolve further
queries.
If DNS is unable to resolve further queries it is another issue and not
related to the message nslookup gives. Possibly a "." (Root) Forward Lookup
Zone, you can safely delete this zone which will enable Root Hints. Also,
after the zone is deleted and the console is refreshed you can enable a
forwarder to your ISP's DNS.
825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;825036

300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202&FR=1

323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;323380

 

[J.C. Hornbeck [MSFT]]

This specific message from nslookup does not necessarily indicate a problem.
When nslookup starts it tries to find a PTR record for the default DNS being
used. If it can't find it then it'll report an error but you can safely
ignore it. I do. Or if you like you can add the reverse zone and the PTR
record for the server and the message will go away. If you simply type in
www.yahoo.com at the nslookup prompt and hit enter does it fail? Does
nslookup work if you point it to another server using the SERVER command at
the nslookup prompt?

--
J.C. Hornbeck, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.

 

[Ace Fekay [MVP]]

In mujeeb <[email protected]> posted their thoughts, then I offered mine
<snip>

Hi Mujeeb,

As I mentioned, and Kevin and as well as Marc and JC all mentioned as well,
all you have to do is create a reverse zone for your internal IP range, and
make certain that a PTR record exists for your DNS server. That is all.

That is just a message you are getting saying (or translated to "You do
not have a PTR entry for your DNS server IP ADdress". That's all it says.But
nslookup will still function on subsequent commands.

To create a reverse zone, please look at this article and look for the
section on how to create a reverse zone:

308201 - HOW TO Create a New Zone on a DNS Server in Windows 2000:
http://support.microsoft.com/?id=308201




--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory