Prepare Windows Server
Setting up wildcard DNS
Set it while confirming operation with nslookup.
First of all, confirm the interface setting with
ipconfig / all. This time Windows Server 2016 as DNS server and DNS client. The IP address is 192.168.1.77, and confidence is designated as a DNS server. Also use Google DNS 126.96.36.199 for Internet communication. (Sorry in JP's)
Setting of DNS server is here. Internal domains resolve themselves, and general top domains configure conditional forwarders for Google DNS. If you set top domain as conditional forwarder, it will be transferred including subdomain.
In this state, try name resolution with nslookup. Naturally, name resolution of unset FQDN fails. For this time we will assume a domain called designetwork.com and the host will be test.
Register a new host (A record). The host sets *.
A wildcard record is set.
You can see that name resolution is done. test.desgnetwork.com that could not be resolved at first was resolved to 192.168.1.77. Also, the appropriate host aaa can be solved in the same way.
You can also support subdomains
Also, if you set with wildcard records, you can resolve names even if you include subdomains. test.sub.designetwork.com, there is no problem even if there is a subdomain.