CNAMEs not working on delegated domain

#1

I’ve created a delegated single zone domain and corresponding zone with A, AAAA and MX and TXT records. These all seem to be working correctly. However I’ve tried adding CNAME records (for example www.mydomain.com) but I can’t resolve them. Even using
dig @ns1.dynv6.com www.mydomain.com
fails to resolve the cname. I’ve now tried with two domains and I can’t get either to work with cnames.

I’ve tried ssh and can see the following:

> hosts mydomain.com records 
  NAME | TYPE  | PRIORITY |            VALUE              
-------+-------+----------+-------------------------------
  @    | MX    |       10 | mymailserver.com.                 
  @    | TXT   | -        | v=spf1 a mx ip4:123.123.123.123  
  @    | CNAME | -        | www                           
  @    | AAAA  | -        | ::aaaa:bbbb:cccc:dddd

(obviously I’ve obfuscated real domain name and ip addresses)

Does anyone have any suggestions? Thanks

#2

CNAME records without names do not work. Instead you should create a CNAME record for www that points to @ (or empty string).

correct:

www CNAME @

wrong:

@ CNAME www
#3

Thanks, I’ve got it working now. I’d assumed that the @ went in the field that says, " Leave empty or use @", but that’s actually where I enter the cname. I have to enter ‘mydomain.com.’ into the data field.

1 Like
#4

The validations for CNAME records are more strict now. Empty names are not permitted any more.

#5

It seems something broke,
because if I enter @ in the data field I get an error message : “must be a valid hostname”

Thank you for your help

#6

Thanks for your feedback. Empty targets (not @) are now allowed and will be resolved the zone itself.