What you've done by adding a dot (.) as a DNS suffix is not an appropriate corrective action and is likely to cause DNS name resolution problems for the operating system and applications. Nslookup uses it's own DNS client resolver but does use the DNS search suffixes that are configured for the computer.The Windows DNS client resolver doesn't suffer from this behavior so you really don't need to change anything in the DNS client settings. The connection specific DNS suffix is being appended to your nslookup query because your nslookup query isn't fully qualified. This is the behavior you'll see when issuing queries with nslookup that aren't fully qualified. If you want to see the difference, run the same query but instead add the trailing dot (.), as such: Your nslookup query is technically not a fully qualified query because you left out the trailing dot (.). Enter the Alias name as your CMG service name and enter the FQDN which will be your. So now how do I disable this connection-specific suffix? Expand the domain and right click on right pane and click New Alias (CNAME). Tunnel adapter Teredo Tunneling Pseudo-Interface: : g2dibntere1erjhcdrrozsaeod.bx.internal.cl I found the suffixed domain in ipconfig results: C:\Users\admin>ipconfigĬonnection-specific DNS Suffix. Questions = 1, answers = 0, authority records = 0, additional = 0Ĭnn., type = A, class = IN The reason is that it's appending the query with a long domain.įor example, I set the d2 option on nslookup and queried cnn.com: > cnn.com Server: Address: 10.51.5.4 I have another VM in the same VNet and I am using nslookup to query the DNS server.Įvery time I query any domain name on this DNS server specifically, it times out the first two tries and then resolves successfully. I configured an Azure VM with Windows 2012 R2 and the DNS Server role installed.
0 Comments
Leave a Reply. |