I have the domain example1.com – DNS managed at Linode.com
There is a site hosted at example1.com (1.1.1.2) and it works fine.
I have an A record for example1.com that points sub.example1.com to 1.1.2.2
I can confirm requests to sub.example1.com resolve to 1.1.2.2, as expected.
I have added sub.example1.com to DigitalOcean and linked to my server.
sub.example1.com loads up my site fine from the server at DigitalOcean.
Now, I have added an A record wildcard *
that points to the same 1.1.2.2 (*.sub.example1.com)
I have waited long enough for DNS propagation but pings to random.sub.example1.com are
failing as the host can't be located.
Why can't I add a wildcard for a sub-domain of a sub-domain? Is this even possible?
Best Answer
Something appears to be misconfigured. You are attempting to define a separate DNS zone for your subdomain, but it does not exist on the internet facing DNS servers.
Here is what I see, replacing your domain with
example.com.ng
:See that
SOA
record at the end? That isn't theSOA
record for your second zone. We can't tell you why this is the case, but until this is corrected none of the changes you make within that second zone file will influence DNS queries.