I have a Win2k network. From any client on the network I have no
problem reaching websites. I do have a curious problem however when
using nslookup.
The results are as follows:
>nslookup www.google.com
Server: Loopback
Address: 192.168.1.5
Non-Authoritative Answer
Name: www.google.com
Address: 216.239.33.101
The puzzling part is why my DNS server has the name Loopback.
What I have found so far
1. There is no entry in HOSTS or LMHOSTS that automatically assigns my
DNS server's name Loopback.
2. My DNS server has both an NS record and an A record in DNS.
3. I don't have my reverse lookup zone configured correctly (I don't
think that matters)
4. I am using forwarders. I believe they are working correctly.
5. My DNS implementation is Win2K Active Directory Integrated.
6. I have one name server. |
Request for Question Clarification by
twitch-ga
on
01 Nov 2002 09:19 PST
pg3phillip-
Since I can't be certain that this answer will do the trick for you,
I'm just posting it as a clarification request. But I think that it
will solve the mystery. Consider the two following statements that you
made:
3. I don't have my reverse lookup zone configured correctly (I don't
think that matters)
4. I am using forwarders. I believe they are working correctly.
The reverse zone _does_ matter. Whenever you use nslookup one of the
first things that it does is find the name associated with the IP
address of your primary name server. Consider the following:
c:\>nslookup
Default Server: myns.mydom.org
Address: 192.168.1.3
> ns.google.com
Default Server: myns.mydom.org
Address: 192.168.1.3
Name: ns.google.com
Address: 216.239.32.10
> server 216.239.32.10
Default Server: ns1.google.com
Address: 216.239.32.10
So, the name associated with the address is not always the same in
forward and reverse mappings.
What I think is happening is that nslookup is trying to find the name
associated with 192.168.1.5. Since you don't have a zone file for the
1.168.192.in-addr.arpa zone, the name server forwards to someone else.
That server either has a zone file for 1.168.192.in-addr.arpa or knows
someone that does, and finds the name 'Loopback' associated with that
address. You can test this with nslookup by setting the server to one
of your forward servers and looking up 192.168.1.5.
If having this system named Loopback is annoying to you, all that you
need to do is create a zone file for 1.168.192.in-addr.arpa and give a
PTR entry for 192.168.1.5 and name it whatever you like.
Hopefully this helped you out. Again, this is just a guess at what the
issue is, so I'm only posting as a clarification request. Let me know
if this solved the mystery.
|
Clarification of Question by
pg3phillip-ga
on
01 Nov 2002 11:03 PST
Twitch......
I am not sure I completely understand the part of you explanation
where you write, "Since you don't have a zone file for the
1.168.192.in-addr.arpa zone, the name server forwards to someone else.
That server either has a zone file for 1.168.192.in-addr.arpa or knows
someone that does, and finds the name 'Loopback' associated with that
address."
Are you suggesting that the Forwarders are receiving this request and
returning loopback as the name?
|
Request for Question Clarification by
twitch-ga
on
01 Nov 2002 12:54 PST
pg3phillip-
"I am not sure I completely understand the part of you explanation
where you write...Are you suggesting that the Forwarders are receiving
this request and returning loopback as the name?"
Yes, exactly. Again, you can test to see if this is the case by
setting the server in nslookup to be one of your forwarders and asking
it for the name associated with 192.168.1.5. For instance, let's say
that the IP address of a forwarder is 192.168.3.9. You would do this:
c:\>nslookup
Server: Loopback
Address: 192.168.1.5
> server 192.168.3.9
Default Server: ns.somedom.com
Address: 192.168.3.9
> 192.168.1.5
...
Then the answer, I think, will look something like this:
> 192.168.1.5
Default Server: ns.somedom.com
Address: 192.168.3.9
Name: Loopback
Address: 192.168.1.5
Give that a try and let me know what you find.
|
