Question

Wildcard subdomain not accessible

Posted September 5, 2014 5.8k views

I’ve gone through the subdomain tutorial to try to get wildcard subdomains working for my domain. My Droplet’s DNS page looks like this. However, when I drop into a terminal session and try to look up any subdomain (e.g., “foo”), I get the following error:

$ host foo.hobolabs.com ns1.digitalocean.com
Using domain server:
Name: ns1.digitalocean.com
Address: 173.245.58.51#53
Aliases:

Host foo.hobolabs.com not found: 3(NXDOMAIN)

When I try to ping it, I get something suspicious:

$ ping foo.hobolabs.com
PING foo.hobolabs.com.com (54.183.52.48) 56(84) bytes of data.
^C
--- foo.hobolabs.com.com ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3022ms

The host tries to resolve as foo.hobolabs.com.com. Does this give any clues as to what might be going on?

2 comments
  • Can you provide a screen grab of your DNS config manager settings.

  • Thanks for the response, moisey. I’m not sure which page you mean, specifically. Is it different than the screen I already linked to?

    Here’s the only other DNS page I see in my dashboard.

    I should also note that as of this morning, running the previous host command gives me this output:

    $ host foo.hobolabs.com ns1.digitalocean.com
    Using domain server:
    Name: ns1.digitalocean.com
    Address: 2400:cb00:2049:1::adf5:3a33#53
    Aliases:
    
    foo.hobolabs.com is an alias for hobolabs.com.
    hobolabs.com has address 107.170.239.65
    

    However, trying to ping the subdomain gives me the same error as yesterday, and trying to run host without specifying the nameserver tells me the host is not found:

    $ host foo.hobolabs.com
    Host foo.hobolabs.com not found: 3(NXDOMAIN)
    

    Is this just DNS being really, really, ridiculously slow?

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
1 answer

It looks like it was indeed “DNS being really, really, ridiculously slow.” It now correctly resolves:

$ host foo.hobolabs.com
foo.hobolabs.com is an alias for hobolabs.com.
hobolabs.com has address 107.170.239.65
hobolabs.com mail is handled by 20 alt2.aspmx.l.google.com.
hobolabs.com mail is handled by 30 aspmx2.googlemail.com.
hobolabs.com mail is handled by 10 aspmx.l.google.com.
hobolabs.com mail is handled by 30 aspmx3.googlemail.com.
hobolabs.com mail is handled by 20 alt1.aspmx.l.google.com.

DigitalOcean’s DNS service recently experienced an issue that caused DNS records to take longer than normal to propagate completely. It sounds like you may have been affected. This issue should now be resolved. If you see any further issues with DNS propagation, please open a support ticket so the team can investigate the issue.

Thanks for your patience, and sorry for any inconvenience.

Submit an Answer