NSlookup reports domain.com.domain.com on every lookup

[John Martoccio]

Good Afternoon,

I am having a problem that after several weeks, I cannot
solve:
When I do a NSlookup of any name, it always reports back
that name as a prefix to my-domain, example:

NSLOOKUP TEST.COM NS1.EARTHLINK.COM
reports as: TEST.COM.MYDOMAIN.COM
with the correct IP for mydomain.

I have tried this with and without the "Append parent
suffixes of the primary DNS suffix" checked, in the
Advanced-DNS of the TCP/IP protocol of the NIC with the
same results.

My AD/DNS server does the same thing, so I tried using
an external one, with the same result.

All my internal machines are set to resolve through a
2000 server/ad-dc, however, I have also tried to resolve
directly with the router too(runs in NAT mode), but I get
the same result.

I am anxious to hear what might be causing this !

Sincerely,
John Martoccio
(e-mail address removed)

 

[Jonathan de Boyne Pollard]

JM> reports as: TEST.COM.MYDOMAIN.COM

Give fully qualified domain names to your DNS debugging tool.

<URL:http://menandmice.com./online_docs_and_faq/glossary/fqdn.htm>

 

[Kevin D. Goodknecht [MVP]]

In John Martoccio <[email protected]> posted a question
Then Kevin replied below:
: Good Afternoon,
:
: I am having a problem that after several weeks, I cannot
: solve:
: When I do a NSlookup of any name, it always reports back
: that name as a prefix to my-domain, example:
:
: NSLOOKUP TEST.COM NS1.EARTHLINK.COM
: reports as: TEST.COM.MYDOMAIN.COM
: with the correct IP for mydomain.
:
: I have tried this with and without the "Append parent
: suffixes of the primary DNS suffix" checked, in the
: Advanced-DNS of the TCP/IP protocol of the NIC with the
: same results.
:
: My AD/DNS server does the same thing, so I tried using
: an external one, with the same result.
:
: All my internal machines are set to resolve through a
: 2000 server/ad-dc, however, I have also tried to resolve
: directly with the router too(runs in NAT mode), but I get
: the same result.
:
: I am anxious to hear what might be causing this !
:
: Sincerely,
: John Martoccio
: (e-mail address removed)

It sounds like someone has put a wildcard record in the mydomain.com zone.
(a wildcard record is one that has * for its name)

 

[Alan Wood [MSFT]]

Hi John,
That is correct, NSLOOKUP is known to do that. It is trying different
combinations of the suffix's on the system, including the Primary Name on
the system.

If you are querying for an FQDN using NSLOOKUP you need to make sure and
end your query with a "." .

So if you are making a query for TEST.COM using nslookup try: nslookup
test.com.

Thank you,

Alan Wood[MSFT]

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

 

[John Martoccio]

That was exactly the sitation, no trailing "." after ".com"
When I did that, everything was normal !

BTW, there are no wildcards in my dns servers.

Thank you for your followup.
A Knowledgebase article to this effect, would certainly
clear this up for many of us !!!

Sincerely,
John Martoccio

 

[Alan Wood [MSFT]]

Hi John,
There is a blurb about it in the Windows 2000 Reskit that is online but
no KB.

Thanks,

Alan Wood[MSFT]

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