Hi!I think I missed the spot...I just configured a system with one NIC: primary DNS suffix => primary.com, the connection-specific DNS suffix => secondary.com. The option 'append primary and connection specific DNS suffixes' is checked.So - when I try to resolve the unqualified name 'test1', I expected the system to try it in this order: 'test1.primary.com' => 'test1.secondary.com'. But the client does not try to use the second DNS name, just the one with the primary suffix.Is this the normal behaviour? When it is - what is the reason for a connection specific suffix? Just for registration?The client is Windows 7 RTM.Thank in advance!Greetings,Enn

Hi, The reason to use more then one DNS are if the first one does not resolve name to ip address. It moves to next one on the list. In your case it got the answer it needed from the 1st DNS. Slan go Foill, Paul

Also, hope following link can help you. Configure TCP/IP to use DNSThanks.

Hi Paul,thanks for your answer. I'm sorry but I think I didn't explain my scenario well. I have just one DNS server configured, but on that NIC is a connection-specific DNS suffix configured. So that machine got two DNS suffixes - the primary and the connection-specific.I thought that the option 'append primary and connection specific DNS suffixes' tries to 'expand' the resolution process for unqualified domain names. But I captured the DNS traffic and the client never asked the DNS server for that connection specific suffix. The client just stops the process after trying the primary DNS suffix.So: registration in that connection specific DNS zone: yes -- resolution: no.Do you have any ideas?Greetings,Enn

Hi Robinson,thanks for your help. I read the article and - unfortunately - I'm still not sure how the option 'append primary and connection specific DNS suffixes' works.Let's assume the client tries to resolve the unqualified DNS name 'ftp24'. The client is configured to use 'suffix1.com' as its primary DNS suffix and 'suffix2.com' as its connection specific DNS suffix. The client has got just one NIC.Could you please tell me, what DNS resolution a Windows client is going to try? And in which order? I though I would be 'ftp24.suffix1.com' and - if the client won't get an positive answer to that - it would try 'ftp24.suffix2.com'... but obviously I am wrong.Many thanks in advance.Enn

Not exactly the same problem but the same fix may work.http://social.msdn.microsoft.com/Forums/en-US/windowsgeneraldevelopmentissues/thread/9adaaa5c-7901-422c-9392-0ed73dafaa06The fix is buried in the thread. This is it here: 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 Kerry Brown MS-MVP - Windows Desktop Experience

Hi Kerry,thanks for your help. And the whole stuff should work without changing the local policies......yeah - it was my fault (of course). I tried it in my lab with 'nslookup' instead of an application that uses the local DNS client service. Nslookup is not implemented in the way to add a connection-specific DNS suffix when the query is made for an unqualified DNS name. Well, when I tried good-old-Ping instead, the DNS query worked as it should...Just another point for those who are interested: the primary DNS zone which is queried first has to be resolveable by the DNS server. Otherwise the DNS server will response with a 'server failure' instead of a 'name error'. When the client get a 'server failure' he won't try the connection-specific query afterwards.Thanks to all who took the time to help me!!Greetings,Enn