Invalid Hostname message for wildcard domains

The workaround is to go to the main DNS Manager page and "Add a domain zone" named subdomain.domain.com. Then create a wildcard entry for * in that new zone.

You can add . You can't do ".subdomain". You'll have to add the subdomain as another zone, then add * as the record.

@amityweb:

Hi

I have setup wildcard domains on other DNS managers for some time now… e.g. *.mysubdomain

This works fine everywhere else, and is required for a system we have that can create websites on the fly with chosen subdomains (we cant manually add in every sub domain everytime!).

When I try to add this on Lindes DNS I get: Invalid hostname '*.mysubdomain'

(obviously my subdomain is something else).

So does it mean Linode will not accept wildcard subdomains?? Everyone else I use does. I have had to revert to another DNS manager but ideally I want to keep them all in Linode.

Thanks

I do not agree that a wildcard is the only option, you could absolutely add the new subdomains in an automated way (Linode API if using the linode service with it being the master, dynamic updates if using bind as a master, etc).

However, I do agree that it's a completely unnecessary limitation in the dns manager, the limitation being fairly similar to that of http://forum.linode.com/viewtopic.php?f=7&t=9300#p53391.

I guess I should add it to my list of strangeness at: http://forum.linode.com/viewtopic.php?f=7&t=8932#p51363.

I forgot to say that the sub domain IS already added as a sub-domain… so mysubdomain.mydomain.com DOES work and is pointed to the IP, but I need to add *.mysubdomain.mydomain.com (so I assume a hostname entry of *.mysubdomain).

So are you saying I need to add the full sub-domain as a new domain entry (zone record??)? I have several, it looks untidy this way.

We are not going to use the API, this is too much unnecessary work when DNS managers have the facility to add a wildcard. It makes no sense to develop this into our system to get around the Linode limitation.

For info, I am using Cloudflare for this domain now. I did not want to use Couldflare because I could see no speed benefit in using them, which is the point of using them, so wanted to come back to Linode, but cant.

Thanks

@amityweb:

We are not going to use the API, this is too much unnecessary work when DNS managers have the facility to add a wildcard. It makes no sense to develop this into our system to get around the Linode limitation.

I did not mean that suggestion as a way to get around the Linode limitation specifically but rather as a way of avoiding wildcard records in the first place.

Oh ok… we dont want to avoid wildcards though, it works a treat. Is there any reason we should? We create websites on the fly often and then delete them, for live sites and development reasons. Makes sense for us that all the sub-domains we create just work already. Also… I assume using the API if an entry is added we have to wait for the DNS to propagate?? If so then that is definitely why we need wildcards, because we need it to work immediately, we cant wait for DNS to propagate.

Thanks

@amityweb:

So are you saying I need to add the full sub-domain as a new domain entry (zone record??)? I have several, it looks untidy this way.
Yes, that's what they're saying (assuming I'm understanding you right), and yes, it looks untidy. It's a limitation of the DNS manager. Could be worse.

Ok thanks. I'll use an alternate DNS manager that supports it.

If they're all the same IP just add one wildcard at the top level. It works for sub sub sub domains too.

*.domain.com means any.thing.domain.com will resolve along with sub.domain.com

-Chris

thanks, but they are not, I have a lot of 1st level sub domains pointing to different IPs.