Host server.example.com resolves as server.example.com.example.com when Wildcard entry *.example.com exists on public DNS server Hello!

I have had this happen on a few AD installations where the AD domain name is example.com, and there's also a Wildcard entry *.example.com on the public DNS (web host)

When I type "nslookup server.example.com" on a client that resolves using the Domain Controller, it returns the IP of the public web server with a name of "server.example.com.example.com".

My solution was always to remove the public wildcard entry, but I never found the actual cause. Is there a way to configure DNS in AD so that it ignores the wildcard?

Thanks!