NSLOOKUP returning the domain appended to non-authoritative answer, along with wrong address

domain-name-systemwindows-server-2008-r2

I recently installed a Windows 2008r2 server (workgroup only, no AD or Domain). This server has DNS enabled.

From a different client machine on the LAN, I run NSLOOKUP to test DNS operation.

When starting up, it correctly lists the server name and IP address.

when I type in "realdomain.com" from the > prompt, NSLOOKUP returns:

Non-authoritative answer:
Name:   realdomain.com.my.domain.net
Address:  67.215.65.132

The client system is able to resolve names, so DNS is working to some extent, but I don't understand why "my.domain.net" is appended.

The 67.215.65.132 address returned for realdomain.com is also incorrect. The address actually belongs to OpenDNS. I am using OpenDNS as the forwarders, but those addresses are 208.67.xxx.xxx.

"my.domain.net" is the primary DNS suffix of the my local LAN server. It is not a publicly visible domain, since the server is on a private network.

This question seems to be quite similar, but I don't understand how to apply the solution: "…remove the wild card entry from your network solutions configuration". What wild card entry? Where is the "network solutions configuration"?

As in the referenced question, if I enter realdomain.com. (with the period at the end), it works correctly and returns the correct address.

Best Answer

I get a similar result:

D:\Users\tannerf>nslookup domain.net 208.67.222.222
Server:  resolver1.opendns.com
Address:  208.67.222.222

Non-authoritative answer:
Name:    domain.net.MYSUFFIX.COM
Address:  67.215.65.132

Looks like OpenDNS is redirecting when the name can't be resolved. You can change the query to any subdomain that won't resolve, and it will return the same:

D:\Users\tannerf>nslookup mdmarra.local 208.67.222.222
Server:  resolver1.opendns.com
Address:  208.67.222.222

Non-authoritative answer:
Name:    mdmarra.local.microsoft.com
Address:  67.215.65.132

nslookup is, by default, appending the search suffix. Take a look at this question. And here's a thread bemoaning OpenDNS' decision. I find it terribly confusing myself.

If you'd like to prevent OpenDNS from redirecting, you might take a look here.

Related Topic