Vista not appending primary DNS suffix beyond one level deep, Anyone Seen this ?

Question

This is new to Vista as XP works fine.

When you simply set append Primary DNS suffix, the system should always append it, such that is your domain is mydomain.com, and you look up www, it should append so the FQDN=www.mydomian.com

That seems to work fine, but if you do one more deep, such as www.test, you would expect as in XP and in DNS in general to append the primary suffix, such that the FQDN = www.test.mydomain.com

Vista does not do this, and this is a very major problem for our company as we have many DNS zones and normally the user does not need to append the domain he/she is in and it should recursive lookup. It is not. We are not going to GPO 100 domain suffixes to each workstation just so they don’t have to type the "root" domain, it should append it.

Has anyone seen this ?

-ap

Answer 1

Yes, I am. Here is the summary of my problem also:

I'm trying to load 6.5.4 on Vista Build 5600. I am unable to enter the Networking, Advanced TCP/IP Settings, enter the DNS tab, check the Append these DNS suffixes (in order) radio button, and add the domain I need to connect to. This section is all grayed out. How do I activate this section? Does anyone have the solution to this problem?

 

thanks

 

Daryl

 

Lotus Notes Configuration – DNS Error:108

 

Local TCP/IP Settings Problem!

 

Unable to send confirmation completion email!

 

Verify that Verizon.com is correctly specified

In the DNS Suffix search order of your local

TCP/IP settings.

 

Answer 2

This however is a different issue than mine as you cannot even select the append DNS radio-button. I have no asnwer for you there.

Mine is, no matter what you put in the DNS suffix search order, either by GPO or natural assignemnt, if you try too do a lookup of anything 2 tiers deep, it does not prepend the root domain. Such that if the root domain is mydomain.com  and you try to look up www.qaroom  it wont prepend mydomain.com to give the resulting FQDN: www.qaroom.mydomain.com.

Iv have tried all combinations.

Some answer from a developer would be nince here, has that been tested, has anyone else seen this.

 

Thanks

Xerlic

Answer 3

Acutally, i completely reloaded Vista and can now append the DNS section. However, now add a domain name to append, save the configuration, and even if I immediately return to the DNS tab, the domain name just entred is gone; it just dissappears.

Xerlic, any advice how to keep the domain name in the append box? As the first post of this thread says, this function works flawlessly in XP.

thanks

 

Daryl

Answer 4

I'm having problems with Vista's DNS Suffixing:

- My entire network has the dns suffix : work.intranet and I have a BIND dns server that resolves a.work.intranet and *.a.work.intranet to 192.168.0.2 so that if I ping bbb.a.work.intranet or ccc.a.work.intranet they all resolve to 192.168.0.2 (at least up until Vista)

- If I ping a.work.intranet it correctly resolves to 192.168.0.2;
- If I ping a it correctly resolves to 192.168.0.2;
- If I ping bbb.a.work.intranet it correctly resolves to 192.168.0.2;
- BUT IF I ping bbb.a it no longer resolves. (could not find host)

- If I do a nslookup bbb.a it correcly resolves to 192.168.0.2

So what appears to be happening is that it isn't adding the dns suffix when the domain has more than two parts (xxx.yyy).


Any ideas how to solve this?

Answer 5

I too am having a similar problem, except mine is related to appending a DNS suffix in the advanced TCP/IP properties of a VPN connection. The option to append DNS suffixes is grayed out. I have installed the new release of Windows Vista Business edition.

Has anyone learned how to resolve this?

Answer 6

Has anyone found a solution for this yet ?

I'm having exactly the same problem: Dns suffixes more then 1 level deep are not being appended ...

is Microsoft working on this problem ? I'm experiencing in the final release of vista ...

 

thanx,

 

B

Answer 7

Benjamin, just wanted to let you know that I haven't found a solution yet.

Wayne

Answer 8

Have you found a solution to this problem yet ?I have exactly the same problem that you describe ...
is Microsoft aware of this bug ('cause that's what I think this is)

Answer 9

I have encountered the exact same problem.  This is almost certainly a bug or defect.

DNS suffixes are not being added to local domains that have more then 1 level.  We have a multi-os network, and all our other non vista workstations (winXP, MacOS and Linux ) are working correctly.

version tested:
Windows Vista Ultimate
Version 6.0 (Build 6000)

Answer 10

same problem.

is this problem solved?

Answer 11

All

As I wrote the original question and researched every possible solution, there is NO solution as of yet, I am getting our company and partnerships to get this up the chain at MS, as this is a big problem to roll out company wide.

You will see no problem IF you only have one-level deep DNS lookups, more than one-level where prepending of the root domain(s) it wont period.

Thanks

Alex Paoli

Answer 12

This is an EXTREMELY annoying bug. I had seen this in beta versions of Vista I was playing with as well and forgot about it until I purchased a retail version and installed it on my system. I work at an ISP where we have naturally tiered hostnames in different subdomains to signify the node of the network. It is irritating that I can no longer have my company domain name appended automatically if I include the subdomain after the hostname. It seems as soon as you enter a period in the hostname, it just turns off appending of the domain suffix. This is a horrible problem that I hope Microsoft fixes ASAP. They flat out broke the DNS resolution behavior they had working since Windows 95 (not to mention every other non-Microsoft operating system)!

Answer 13

Hi

Im having the same problem and need to get it sorted, has anyone actually contacted PSS and if so what is their stance on this problem?

Answer 14

 

I solved this problem. By default it does not do this but their are good old group policy settings. To enable this do
1. start>run>"gpedit.msc"
2. navagate to "Computer Config>Administrative Templates>Network>DNS Client"
3. enable the following two entries
-allow dns suffix appending to unqualified multi-label name queries
-Primary DNS Suffix Devolution.

Restart, or force policy update. and thats it

Answer 15

 

thanx a lot man ! I think a lot of people were waiting for this, I surtenly was !

Go figure; this time it was no bug but it WAS a feature :)

thx again,

Benjamin

Answer 16

The gpedit thing didn't work for us.  If anybody has some solution to this problem, please let us all know.

thanks,

Answer 17

Ok, i did notice this caused problems with home/home premium as you are unable to access Group Policy,  but i did manage to solve the problem, but by altering the registry, so all the usuall registry warnings apply (to lazy to type out)

Find HKLM\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient"  and change/create a dword value called "AppendToMultiLabelName" and set it to 1, you may need to restart

 

Hope this helps

SimAda00

 

Answer 18

That fixed it

 

Very stupid to put that there.

 

Good work

 

ap

Answer 19

Missed page 2.. ignore post

Answer 20

I just figured this out on a Vista Business install.  It seems to be a permissions issue that can be resolved by enabling the administrator account (disabled by default on Vista.)  A user account in the administrator group does not seem to have the permission level necessary to edit this particular connection property.

 

I started out by changing to the Classic Start menu view (rt click on taskbar>properties>start menu>"Classic Start menu")

 

Then I launched the computer management mmc panel (rt click computer>manage)

 

Navigate to the Administrator User under Local Users and Groups>Users, rt click>set password (set a password), then rt click again, go to properties, and uncheck "account is disabled"

 

You can now log into the machine as "administrator" with the password that you set and edit the DNS suffix list that was previously greyed out.

 

Two interesting things:  Even after logging back in with my user account (in the administrator's group) and disabling the administrator account, I am now able to edit what was previously unavailable before the above "exercise."

 

Also strange, the setting changes I made were not initially preserved!  Everything looked normal, but I had to make the changes about 7 times or so, then they finally stuck.  I think the trick was making a minor edit to the primary "local area connection" first, then I was able to edit an additional setting.  Definately buggy, but this is how I got it to work.

 

Hope this helps!

 

Ken

Answer 21

Thanks a lot. I am now able to resolve in all of the subdomains as well as the TLD.