New CNAME records not visible on MIAB DNS?

Maintenance
1

I used the Control Panel -> “Custom DNS” to add a CNAME record for one of my domains (let’s say mydomain.com which is hosted on mybox.com). I can see that CNAME record in Control Panel -> “External DNS”.

However, when I do dig @ns1.mybox.com +noall +answer mydomain.com any on another machine, the CNAME record is missing. Does it take some time for the updated records to be visible on the box’ own DNS or what could be the reason I can’t see the new entry?

2

That shouldn’t take time. I tried it a moment ago on my own installation and this works right away. Typo?

3

I don’t think so at least.

You can try for yourself:

host -t ns paul.fi
paul.fi name server ns1.mailbox.kypelihosting.com.
paul.fi name server ns2.mailbox.kypelihosting.com.

dig @ns1.mailbox.kypelihosting.com +noall +answer paul.fi any

There’s no CNAME entries in the dig result.

But in External DNS I can see:

johan.paul.fi	CNAME	kype.li
(Set by user.)
www.paul.fi	CNAME	kype.li
(Set by user.)

How can I see what the zone file actually looks like on the box?

4

Ok, well - I can also see the CNAME entry with

cat /etc/nsd/zones/paul.fi.txt

But I cannot see the entry if I do on my box

dig @localhost +noall +answer paul.fi any

So the CNAME entry is in NSD zone file, but the DNS server won’t serve the record. Sounds weird?

I tried to reboot the machine, but to no help.

5

We can continue on GitHub. I created the following issue: https://github.com/mail-in-a-box/mailinabox/issues/1237

6

I see you solved this. Interesting though, I made the same error yesterday when testing this (forgot the trailing .) but when queried with dig I did get the CNAME, albeit (obviously) with the domain of my box attached to the domain name I entered. (www.testdomain.com.domain-of-my-box.com).

Anyways, good to hear it works now.

Regards,

Paul

7

Yes, I got it resolved which was nice. And of course I knew I had to add the trailing dot, but it was a while since I’ve configured a DNS since last s:) A bit frustrating thought to not see the expected outcome from the dig query albeit it being wrong, which would have helped with the debugging.

But I am happy that it wasn’t a MIAB bug in the end.