Help troubleshooting email DNS issues

[jdaviescoates]

6 hours ago I got a "Email is not configured" properly notification - all for domains that are all previously properly configured.

I have lots of errors like this, where is says "Actual: null"

But this is very confusing because there actually are such records.

Why does Cloudron think these records don't exist?!?

MXtoolbox finds them fine:

https://mxtoolbox.com/SuperTool.aspx?action=mx%3Auniteddiversity.coop&run=toolpage

[nebulon]

@jdaviescoates can you check if unbound is up and running on your Cloudron? Also maybe can you try to use host or dig via SSH from your server to see if the system can see the records?

[scooke]

I see this happen to mine too from time to time. Interestingly, never with domains in namesilo nor dynadot, ocassionally with porkbun, most commonly with namecheap. What could be causing this... I've always found Namecheaps DNS management more complicated than the others, so maybe in your case your registrar uses similar tech or approach. My impression: They want all of my services on their platform so these "problems' pop up, potentially making me consider moving hosting and whatnot to their system and "advanced DNS". I don't. They just keep having great sales, and though I've slowly migrated most of my domains away from namecheap, I keep adding new ones (for several months).

[humptydumpty]

@scooke said in Help troubleshooting email DNS issues:

most commonly with namecheap

I think that's coincidental because I occasionally experience this issue and my domains are with namesilo but have the DNS managed with dnsmadeeasy. I just ignore the issue and it auto-resolves itself. It doesn't seem to cause any delivery failures.

[jdaviescoates]

@nebulon said in Help troubleshooting email DNS issues:

@jdaviescoates can you check if unbound is up and running on your Cloudron?

It wasn't up. Restarting it twice got it back up. Do you think that was it then?

I'm guessing this could also be why some of the emails I've been sending haven't arrived too? (was going to start a thread about that too)

[nebulon]

@jdaviescoates most likely yes, unbound is quite essential for the system to work well. Would be good to know why it was wasn't up. Did you run out of disk space at some point lately? Also are there any hints in the unbound daemon logs?

[3gal]

@jdaviescoates every time when u add a new domain, it also activates the outbound email relay.

Login to your my.domain.xx
Click at ur Username -> Email -> Status
If Status is RED -> Outbound
Check Settings (Standart=Built-IN SMTP Server)
If your Hoster is not listed:
-> create a email-adress somewhere (at your hoster to use ur domain)
-> set external SMTP Server of that email-adress + emailuser + pw
Info: you can use same email adress for all domains
Test: you can also set "disable" - but you should only use that for redirections, since most services need to send emails for account creation.

[jdaviescoates]

@nebulon said in Help troubleshooting email DNS issues:

Did you run out of disk space at some point lately?

I think I may have done, yes.

Vaultwarden stopped running with an error about diskspace.

When I looked in System info it was still showing over 7GB free space (I guess because it's not live), but I can't not have BitWarden running and so I immediately went over to Hetzner and increased the size of my machine.

But re-sizing requires powering down, re-sizing and then powering up, so odd that unbound didn't come back up then too.

I'll see if I can find anything in the logs....

[jdaviescoates]

@jdaviescoates said in Help troubleshooting email DNS issues:

I'll see if I can find anything in the logs....

All I can see is this:

-- Logs begin at Sat 2021-12-25 21:07:01 UTC, end at Mon 2021-12-27 16:29:54 UTC. --
2021-12-26T17:08:23+0000 ubuntu-2gb-fsn1-1 systemd[1]: Starting Unbound DNS Resolver...
2021-12-26T17:08:23+0000 ubuntu-2gb-fsn1-1 unbound[3253]: [3253:0] notice: init module 0: subnet
2021-12-26T17:08:23+0000 ubuntu-2gb-fsn1-1 unbound[3253]: [3253:0] notice: init module 1: validator
2021-12-26T17:08:23+0000 ubuntu-2gb-fsn1-1 unbound[3253]: [3253:0] notice: init module 2: iterator
2021-12-26T17:08:23+0000 ubuntu-2gb-fsn1-1 unbound[3253]: [3253:0] info: start of service (unbound 1.6.7).
2021-12-26T17:08:23+0000 ubuntu-2gb-fsn1-1 systemd[1]: Started Unbound DNS Resolver.

Is there a way I can access older logs?

[nebulon]

@jdaviescoates ah yes then this most likely was the issue with the unbound anchor file. See https://docs.cloudron.io/troubleshooting/#recovery-after-disk-full