If you got a DNS wildcard, say `*.example.com A 192.168.1.1` and create a new host in a (non-existing) subdomain, say `foo.bar.example.com A 192.168.1.1` then, depending on the server software, the intermediate label bar.example.com may be covered by the wildcards (and e.g. return the address associated with the wildcard), or it may return an empty answer (NOERROR, ANSWERS: 0).

For reference see the attached link. (I understood that getting an empty answer should be the more common way).

At least one DNS provider seems to use different versions of server software on its DNS servers, creating unstable results:


```
ns2.inwx.de.: "reg-wie1"
ns3.inwx.eu.: 84.19.194.8 "INWX DNS Server"
ns4.inwx.com.: 84.19.194.8 "INWX DNS Server"
ns5.inwx.net.: 84.19.194.8 "INWX DNS Server"
ns.inwx.de.: "reg-sin2"
```

#lessonlearned #dns #wildcard
Shared publicly