I recently had an issue with a website not working because it wasn't resolving the www subdomain correctly. The issue was the lack of a dot (.) at the end of the domain name for the CNAME record.

Some DNS providers don't require a dot at the end (or they auto manage it in the background) -for example Cloudflare- and that makes this a little more confusing for the client, and mistakes can be made.

Is it a way to automatically determine when a dot is needed and add it? Or manage it in the background?

Thanks.

In the few migrations I've managed to do so far I've had a client get tripped up by the same thing. However, it's my opinion that it should be the client that ensures proper record syntax. Panels that make these assumptions just enable dumbed down clients, and dumbed down clients make for a heavier support workload. It might be difficult at first, but a client that's properly educated on DNS record management is better than plain ignorance requiring support assistance.

Entirely my own opinion though!

We're thinking of prompting for the . at the end if the target already contains a . as it's more likely the client intends for it to be a FQDN. What do you think?

    Adam I believe that it should be done in such a way that an inexperienced client could do it well and without mistakes.

      15 days later
      Aliysa_Enhance changed the title to Auto check for dots at the end of domain name in DNS records [RELEASED].
      Write a Reply...
      Follow @enhancecp