Host Name Resolution Testing - Devolution or how to concatenates works
Hi, this is quite a difficult subject, but I am seeing multiple clients on our network displaying incorrect host name resolution when connecting via Cisco VPN. It works for 99% of clients but the 1% are unexplainable. OK to summarise as much as I can. If effects both Win XP clients and Win 7 - If machine comes into the office and connects on the LAN it works fine, goes home and problem persists. The client is being handed IP configuration settings via DHCP from the VPN concentrator. Client is showing the correct addresses for the DNS server and for WINS Client is showing a DNS suffix list (three devolving domains eg DM1.DM2.DM3.COM DM2.DM3.com DM3.com) Adaptor settings is correctly showing append parent suffix list of the primary dns suffix If I ping the host name of a server from this client, it shows unkown host. I try NSLOOKUP to same host name it resolves it to an ip address I try ping -a ipaddress it resolves it to a FQDN and gets a ping response Now the interesting bit Looking at the packet capture of the client as it tries a ping to host name, it uses the DNS protocol to the DNS server address but only appends the first DNS suffix list (eg HOSTNAME.DM1.DM2.DM3.COM) It gets a reply unkown host (which is correct as the server is in the next devolved domain) But the client repeats the same dns suffix list and continues about 3-4 times and gives up. It does not try WINS or a broadcast wont work due to the segment it is on (cant broadcast across router) So how do you check/test to see how a windows client is configured to devolve the dns suffix list. I saw this articlehere which talks about the registry setting for Win XP and vista but does not comment about Win 7, does the same apply? As it is there is a registry setting to use DNS turned on (1) but no mention of devolution levels. (I have asked around and they say this is actaully part of the windws kernell and not set in the registry) Machines works fine on the LAN office connection. Works fine if we use IP addresses for shares Machine has been rebooted a number of times, DNS cache flushed I checked the addaptor advanced settings and they seem to be correct PS I had posted this comment in the Microsoft.com Answers forum but was asked to post here instead due to the technicality of the problem. Cheers.
July 1st, 2011 4:48am

Hi excup, Based on your description, I suggest you contact Cisco for further research. It's not only related with the usage of Windows 7 and it's hard for us to test. Thanks for your understanding and cooperation! Regards, MiyaThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
July 5th, 2011 12:41pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics