Score:0

Windows clients fail to lookup cname in own domain search-list

mm flag

So, today I found that Windows clients behave a little different to Linux and Mac DNS clients. Point in case:

The scenario

An nslookup of test.example.com, which returns a CNAME "test.temp.example.com". On Linux and mac this will return the result of the lookup of the CNAME, by means of a second DNS request. Rinse and repeat until an A record or an error is encountered.

The issue

On Windows 7/10 the result is the same, you can test this with "nslookup api.goole.com". Except if the domain you're resolving is in your domain search-list (and/or the local domain?). Then, the nslookup will just yield nothing at all.

  • For historical reasons non-qualified hostnames must be able to resolve:
    • Must use a domain search-list
  • For administrative purposes, I'd like to keep the CNAMEs instead of using many A-records all pointing to the same few IP addresses:
    • Must be able to resolve CNAME records

These two statements appear to be at odds, I'm hoping for a registry setting to change the behaviour!

mm flag
Same issue: https://community.spiceworks.com/topic/454495-dns-not-resolving-cname
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.