Domain appears with double ending when using custom mx record

Maintenance
1

Hi,

im kinda confused atm. So i’ve added a custom mx record for one of my domains on my MIAB machine.
I’ve set an A record to point at the mail.domain.com and set the mx for the domain. domain.com mx 10 mail.domain.com.

But when i dig the mx record for this domain it appears like this:

domain.com MX mail.domain.com.domain.com

I am actually really confused. I’ve also looked into the zone files but it appears the same as i configured it on the admin panel.

I really hope someone can help me.

PS: ive already waited more then 24 hours in case they would update for some reason.

2

Where did you set this?

For example, if setting MX records for external DNS (like at a registrar for example) you may need different syntax.

EG Godaddy’s syntax for this is:

Host: @ (Means use A record
Server: box.example.com
Priority: 10

If you want, PM me and we can discuss logs, and I’ll need a real hostname as well.

3

Ive sent you a message.

But no i’ve set those record on the admin panel of my Mailinabox server. (in the custom dns tab).

4

When you set records there please be sure that you are NOT including the domain name as it is pre-filled for you. But you mentioned the MX record - there would be NO need to configure the MX record anywhere within MiaB unless for some reason you are hosting DNS for a domain which is using some other mail server, which would be somewhat odd, but possible.

5

Im using mailinabox for a pretty long time now. So i know how i put in the records :slight_smile: And yes this is the scenario you just described. The domain is using my mailinabox as DNS but i want to use an external mailserver.

I’ve setup my own nameservers now and it works fine. Seems to be a bug in the v0.30 version.

6

Seems quite possible. I have reproduced the error on a box I have that is running v0.30. I get the same results - when I dig the MX record it comes with the domain.tld repeated but if I look at the custom.yaml file it is fine.

However the same error shows in the actual signed zone file at /etc/nsd/zones/box.domain.com.signed.

7

oh ok thats “good”… i was really going crazy about this :smiley: didnt made sense at all for me… especially since the zone files looks perfect without the additional domain ending. But i guess its probably fixed in the latest version?

EDIT: Oh ok it only seems to appear in the signed zone file… its correct in the non signed

8

Please see my edit … and yes, I would think, and hope that the issue has been corrected in v0.40. At least I have not seen any similar complaints, yet. Knock on wood.

1 Like
9

Nope, this is a bug in v0.40 as well. I will open an issue on GitHub.

1 Like
10

nice! thank you for adding it!

11

This doesn’t really have anything to do with Mail-in-a-Box. See:

12

MIAB is adding the domain twice:

EG: box.domain.com.domain.com. Which is a scripting issue I would imagine since it appears in dig and zone file?

13

@JoshData

Nope, Josh is correct … I can only speak for myself, but I did indeed not include the trailing dot. When I added it, the record was correct.

Maybe the message needs to be in RED? :stuck_out_tongue:

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

1 Like
14

So are we saying, no dot = double or nothing on the TLD?? :wink: Still feel like that should be addressed in the script / api…

15

I will leave the issue open on GitHub for you to make that argument. :slight_smile:

1 Like
16

Alright, here comes the best argument in the world. :smiley: (In a good way)

17

It would be good to fix.