When adding MX record in Custom DNS the format is incorrect in the signed zone file

[alento-group]

https://discourse.mailinabox.email/t/domain-appears-with-double-ending-when-using-custom-mx-record/4405

When adding a custom MX record for a domain in which the mail is not served by the local MiaB install the signed MX record is incorrect. It appears correct everywhere else.

Ex: adding a MX record for mx.tempdns2.tk on the custom DNS page at https://box.tempdns.tk/admin

10 mx.tempdns2.tk

when you dig that record it will return:

;; QUESTION SECTION: ;tempdns2.tk. IN MX

;; ANSWER SECTION: tempdns2.tk. 1800 IN MX 10 mx.tempdns2.tk.tempdns2.tk.

but the record appears fine on the admin page, the custom.yaml file as well as in the unsigned zone file.

[alento-group]

@JoshData

Ok, the issue is a lack of a trailing dot.

Maybe the message when adding a custom MX record should be:

Enter record in the form of PRIORITY DOMAIN., including trailing period (e.g. 20 mx.example.com.).

with the highlighted part in red? :)

[mitchellurgero]

Along with adding a more clear message on the dashboard, the script can easily check for a trailing period as well:

(Using pseudo code here):

if !newDomainRecord.endswith('.')
    # Warn the user about the trailing dot here. We could auto-append it but we don't want to modify user input in this case.

Or something, very simple.