• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
bj-kaiser

name resolution issues

3 posts in this topic

long time since I had to ask a question, but I got a really stupid problem now.

I got a BSD fileserver named "beastie". nslookup from my new Win 7 Starter netbook is ok, but I cant ping or connect to it with Putty/SSH or anything by the name. Despite that, I can reach it with the IP nslookup reports.

I guess the clientname gets registered in the router, otherwise nslookup should fail. So why cant I reach the fileserver by name despite the fact that nslookup can resolve it?

0

Share this post


Link to post
Share on other sites

ok, so I found a solution to this issue.

apparently, windows 7 starter (as in the configuration I got with my EEEPC) will not resolve names without a domain through DNS. so a name like "beastie" won't resolve, except using nslookup. Instead of using DNS windows will try to resolve the name through WINS/workgroup. So a machine not running Windows file sharing or SAMBA won't resolve.

the easiest solution to this seems to be to add a "." after the hostname which apparently forces windows to use DNS. "beastie." resolves, "beastie" doesnt.

0

Share this post


Link to post
Share on other sites

The problem is starting with Windows Vista, Microsoft changed how DNS lookups are handled. Specifically DNS devolutions and unqualified names. There are two (2) changes.

1. This issue may caused by the different DNS resolve behavior between XP and Vista/7, below are the details:

Windows XP:

By default, when a machine attempts to resolve unqualified multi-label names, the DNS client will attempt to resolve the name as specified, then append the domains that are listed in the DNS suffix search order.

Windows Vista/7:

By default, when a machine attempts to resolve unqualified multi-label name, the DNS client will attempt to resolve the name as specified. The DNS suffix search order will NOT be used.

Domain Name Devolution

http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/93802.mspx?mfr=true

You can change this sith GPEdit or add the registry key. There is a second DNS change on resolution but this usually covers 90%+ of the issues.

Run the gpedit.msc on Windows Vista/7, then expand to Computer Configuration\Administrative Templates\Network\DNS Client. Under there, enable the option "Allow DNS Suffix Appending to Unqualified Multi-Label Name Queries." Restart the computer and try again.

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

UseDomainNameDevolution = dword 0x1

2. What is an unqualified multi-label name: The name specified in the query contains a dot(s), but is not dot-terminated.

To resolve it, try to run the gpedit.msc on Windows Vista client, then expand to Computer Configuration\Administrative Templates\Network\DNS Client. Enable the option “Allow DNS Suffix Appending to Unqualified Multi-Label Name Queries” under there.

or

HKLM\Software\Policies\Microsoft\Windows NT\DNSClient

AppendToMultiLabelName = dword 1

Edit: Found my notes and added references and reg keys.

Edited by pjb0222
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.