DNS or NSLOOKUP problem

  • Thread starter Thread starter Paul
  • Start date Start date
P

Paul

Hi

I have 3 computer on my home network all linked to the internet via an ADSL
router.
I have a DHCP server that assigns the IP and DNS addresses to each PC. The
DNS addresses used are that of my ISP and are public addresses.

The problem I am having on one of my PC's is with DNS resolution.

99% of DNS address will resolve on this PC but the odd one or two will not
however they DO resolve on the other 2 PC's.

The problem is obviously with the PC that cannot resolve the addresses as it
cannot be DNS as this resolves names on the other 2 PC's but I am a little
lost as to what is stopping this PC's resolving all but a couple of
addresses.

Hope someone can help.

Regards
 
Paul said:
Hi

I have 3 computer on my home network all linked to the internet via an ADSL
router.
I have a DHCP server that assigns the IP and DNS addresses to each PC. The
DNS addresses used are that of my ISP and are public addresses.

The problem I am having on one of my PC's is with DNS resolution.

99% of DNS address will resolve on this PC but the odd one or two will not
however they DO resolve on the other 2 PC's.

The problem is obviously with the PC that cannot resolve the addresses as it
cannot be DNS as this resolves names on the other 2 PC's but I am a little
lost as to what is stopping this PC's resolving all but a couple of
addresses.

First thing to check is the "Hosts" file to make sure there aren't any
entries in there causing this. Unlikely but possible.

Do they not resolve at all? Even with NSLookup -time=10 (or longer)?
Or do they resolve incorrectly?
Double check the DNS settings on this PC (ipconfig /all); that there are not
somehow "wrong" or "extra" DNS servers listed.
Is this (problem) PC a multi-homed machine? (Perhaps a DNS server listed
on the "other" NIC...)

Is it consistently the same names that failed to resolve or are the
names different at different times...? (In the latter case, I might
suspect a bad network, especially a bad cable giving intermittent
errors.)
 
Little more info would be helpfull. How about the output of the session
where is does not work. What names are not resolving. Maybe an ipconfig
/all from the pc.
 
C:\Documents and Settings\Paul>
William Stacey said:
Little more info would be helpfull. How about the output of the session
where is does not work. What names are not resolving. Maybe an ipconfig
/all from the pc.


Here is the ipconfig /all

C:\Documents and Settings\Paul>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : PC001
Primary Dns Suffix . . . . . . . : yewtree.road
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : yewtree.road

Ethernet adapter LAN:

Connection-specific DNS Suffix . : yewtree.road
Description . . . . . . . . . . . : NVIDIA nForce MCP Networking
Adapte

Physical Address. . . . . . . . . : 00-0C-6E-1B-10-E2
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.240
DNS Servers . . . . . . . . . . . : 213.120.62.103
213.120.62.104
192.168.0.1
Lease Obtained. . . . . . . . . . : 12 March 2004 17:03:02
Lease Expires . . . . . . . . . . : 12 March 2004 18:03:02


It seems to be only one ip address I cannot ping or do an nslookup on, the
ipconfig /all looks the same on the other PC's that work
 
nslookup is a utility , it stands for name server looku

C:\>nslookup /
Usage
nslookup [-opt ...] # interactive mode using default serve
nslookup [-opt ...] - server # interactive mode using 'server
nslookup [-opt ...] host # just look up 'host' using default serve
nslookup [-opt ...] host server # just look up 'host' using 'server

C:\
what internal ip address are you using
do you have a ptr record in your dns table for the computer in question?
 
In
Paul said:
Here is the ipconfig /all

C:\Documents and Settings\Paul>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : PC001
Primary Dns Suffix . . . . . . . : yewtree.road
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : yewtree.road

Ethernet adapter LAN:

Connection-specific DNS Suffix . : yewtree.road
Description . . . . . . . . . . . : NVIDIA nForce MCP
Networking Adapte

Physical Address. . . . . . . . . : 00-0C-6E-1B-10-E2
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.240
DNS Servers . . . . . . . . . . . : 213.120.62.103
213.120.62.104
192.168.0.1
Lease Obtained. . . . . . . . . . : 12 March 2004 17:03:02
Lease Expires . . . . . . . . . . : 12 March 2004 18:03:02


It seems to be only one ip address I cannot ping or do an nslookup
on, the ipconfig /all looks the same on the other PC's that work

Hi Paul,
Thanks for posting that info. It's a very helpful output for diagnosis.

Ok, obviously it's apparently due to the DNS addresses you are using.
Without a lengthy explanation, it;s due to the way the DNS Client side
resolver works. At any rate, in any AD infrastrcture or any internal
infrastructure, and you're running your own DNS services, we need to ONLY
use your internal DNS and NOT your ISP's. You'll need to change your
machines configs (whether static and your DHCP scope) to reflect only this
internal DNS IP for your DNS server address:
192.168.0.2

This way you'll insure that all queries go to your DNS first. This way also
Active Directory is insured proper functionality as well.

Once you've done that, in your DNS properties (rt-click DNS name in your
console, properties, forwarders tab), configure a forwarder to handle
efficient Internet name resolution. Use these two addresses:
213.120.62.103
213.120.62.104

If the option is grayed out, delete the root zone. If not sure how to do
these last two steps, see this article:
http://support.microsoft.com/?id=300202

Once you've done that, let us know if you're still experiencing any more
issues.


--
Regards,
Ace

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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
William Stacey said:
Thanks Ace.

No prob. Hope you didn't mind I jumped in! Couldn't resist on this one!
:-)

Cheers!


--
Regards,
Ace

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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
William Stacey said:
Not at all. Feel free. BTW - Not dns, but check this out when you
get a few - it will blow your socks off (at least mine)
http://microsoft.sitestream.com/PDC2003/ARC/ARC334_files/Default.htm

Cheers!


Yes, it is nice. Now, not being scripter, I'm going to assume this is
somewhat akin to all those scripts available put together in a manageable
GUI and is customizable based on our needs as we see fit? (loosely put).


--
Regards,
Ace

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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Kinda. Its, finally, a new shell like ksh and Perl folks have used over the
years, but different and baked into Windows for once. If you never done a
lot of cmd shell scripting or ksh scripting, it may be hard to see the value
here. To an old school admin, this will be like finding gold. Anyway,
sorry for going OT, just was excited when I saw it. This may get me back
into the admin business (remembering 3am phone calls...aahh maybe not.)
Cheers!
 
In
William Stacey said:
Kinda. Its, finally, a new shell like ksh and Perl folks have used
over the years, but different and baked into Windows for once. If
you never done a lot of cmd shell scripting or ksh scripting, it may
be hard to see the value here. To an old school admin, this will be
like finding gold. Anyway, sorry for going OT, just was excited when
I saw it. This may get me back into the admin business (remembering
3am phone calls...aahh maybe not.) Cheers!


Hmm, I see your point. I'm going to dig into it some more. Looks like it'll
come in handy. If I have any questions on usage or such, I'll ping you, if
ok with you.

--
Regards,
Ace

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

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