Hello,

I believe I am having problem with DNS NSLookup.

When I type xyz.com (any domain in the world ex. yahoo.com) at NSLOOKUP it
is resolving to as follows:

> yahoo.com
Server: DNSServer.domain.co.in
Address: 192.168.0.1

Non-authoritative answer:
Name: yahoo.com.co.in
Address: 216.8.177.28


> google.com
Server: DNSServer.domain.co.in
Address: 192.168.0.1

Non-authoritative answer:
Name: google.com.co.in
Address: 216.8.177.28

Every time it is returning with the same IP address but when I say only
<google>

> google
Server: DNSServer.domain.co.in
Address: 192.168.0.1

Non-authoritative answer:
Name: google.co.in
Addresses: 66.102.9.104, 66.249.93.104, 72.14.221.104

Can any body me in this regards.

Thanks in Advance
Andrew

Andrew wrote:
> Hello,
>
> I believe I am having problem with DNS NSLookup.
>
> When I type xyz.com (any domain in the world ex. yahoo.com) at
<snip>
>
> Can any body me in this regards.


This is a pretty common issue for domains using third level domain name of a
public domain, especially if the parent domain is in the ccTLD.
The proper way to fix this is to assign a DNS suffix search list the does
NOT include the parent domains. The problem really rears its ugly head when
the owners of the parent domains use Wildcarding to redirect unknown domains
to a page at the parent registrar in your case the problem parent is
com.co.in. Check this:
QUESTION SECTION:
you-can-enter-any-name-in-this-parent.domain.com.co.in. IN ANY

ANSWER SECTION:
you-can-enter-any-name-in-this-parent.domain.com.co.in. 3600 IN A
216.8.177.28

If you will take a look at your ipconfig /all your DNS suffix search list
looks something like this:
domain.com.co.in
com.co.in<--remove this
co.in<---remove this

To work around this issue, create a custom DNS suffix search list that does
not include "com.co.in" or "co.in" in your list. I highly recommend that all
DNS suffix search lists have zones in your local DNS server, or lists that
contain other child domains you need short host name resolution for.
Remember, the more names in the DNS suffix search list, the more zones that
will be searched and could slow resolution.

There are several ways to modify the DNS suffix search list, one is to go to
the DNS tab in TCP/IP properties. and select "Append these suffixes (in
order):" then enter only the suffix or suffixes you need short host name
resolution for.
Another way this can be done and pass it on to multiple domain members
running Windows XP or Windows Server 2003, is to use Group Policies (Does
not work on Windows 2000). This particular policy is here:
Computer Configuration
-Administrative templates
-Network
-DNS Client> DNS Suffix search list

A Windows 200 Domain Controller can assign the policy if you upgrade the ADM
files using XP or Win2k3 to set the policy.

How to configure a domain suffix search list on the Domain Name System
clients:
http://support.microsoft.com/kb/275553/en-us


--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This s
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oe.com/OEBackup/Default.aspx
===================================