New in CWP Edge-LatestFree with every CWPpro licenceWebsites up to 300x faster

CWP now includes LSPHP, LSAPI-Cache and CWP Cage at no extra cost with all CWPpro licences. The LSAPI-Cache plugin is integrated into our WordPress and other script installers, and CWP Cage gives every user complete isolation. Available now in the CWP Edge-Latest version.

Get CWPpro ›

Format issue with dots

Started by luca, October 09, 2024, 02:03:10 PM

Previous topic - Next topic

luca

Seems when creating an MX, for example, Bind with CWP.

@ IN MX 5 mx.domain.com

It requires a dot

@ IN MX 5 mx.domain.com.

and CWP is not clear on that. We had to change tons of domains in batch. It would be nice if it alerted about the invalid syntax.

I believe same for CNAMEs, require an extra dot at the end of the value.

Thanks.

overseer

File a bug report. CWP should be able to check and sanitize input like this on individual form pages, as appropriate.

cyberspace

Actually, it is common rule to add a dot at the end of each FQDN in DNS. In case there is no dot then the value from $ORIGIN will be added to the specified domain name.

So if $ORIGIN of the DNS zone has the value "domain.com" then both lines are equal:

@ IN MX 5 mx
@ IN MX 5 mx.domain.com.


So if you add the dot then the specified domain name is recognized as fully qualified domain name.

It is not a bug.

luca

Devs:

Thanks, that's a good point, and you're right. In a DNS zone a target without the trailing dot is treated as relative to the zone, so "mx.domain.com" becomes "mx.domain.com.yourdomain.com" and mail breaks without any visible error. The same applies to CNAME, NS and SRV targets.

We've passed it to our developers as an improvement for the DNS editor: automatically add the trailing dot to full host names (or at least warn when it's missing), check the zone syntax when it's saved, and report any error instead of silently accepting it. We'll let you know which version includes it.