I updated my mailinabox yesterday to:
Mail-in-a-Box Version: v56
Everything seemed fine, accessed emails directly in roundcube etc.
Today noticed on my desktop client, connection to my emails on the mailinabox were disconnected so went to login to admin to check:
https://box.{domain}.email/admin
And got this no connection issue - like no dns…
So I checked on my domain and saw no dns for my domains using this servers NS responding…
I then checked on the Nameservers resolution and nothing…
I did check with ICANN and I can see that the NS for my domain are set correctly still…
And I double checked with my Domain registrar, still pointing and asked them to look into it…
They replied with:
Hello,
Thank you for contacting Namecheap Support!
Per our check, the XXX.email domain was pointed to the following nameservers correctly on our side:
ns1.box.XXX.email
ns2.box.XXX.emailYou can check it using ICANN Whois tool at ICANN Lookup .
However, we cannot locate the host records set for the domain on these nameservers. Please contact your hosting-provider to investigate the issue further.
Should you have any other questions or require any further help, please do not hesitate to contact us anytime. We are here for you 24/7/365.
So it looks like the Name Server Daemon on the mailinabox might be screwed up…
I checked on the box, is running fine:
root@box:~# service nsd status
● nsd.service - Name Server Daemon
Loaded: loaded (/lib/systemd/system/nsd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-03-30 18:48:21 CST; 16min ago
Main PID: 871 (nsd)
Tasks: 3 (limit: 2360)
CGroup: /system.slice/nsd.service
├─ 871 /usr/sbin/nsd -d
├─ 893 /usr/sbin/nsd -d
└─1027 /usr/sbin/nsd -d
Mar 30 18:48:21 box.xxxx.email systemd[1]: Started Name Server Daemon.
I checked NSD config files:
root@box:/etc/nsd# cat nsd.conf
# Do not edit. Overwritten by Mail-in-a-Box setup.
server:
hide-version: yes
logfile: "/var/log/nsd.log"
# identify the server (CH TXT ID.SERVER entry).
identity: ""
# The directory for zonefile: files.
zonesdir: "/etc/nsd/zones"
# Allows NSD to bind to IP addresses that are not (yet) added to the
# network interface. This allows nsd to start even if the network stack
# isn't fully ready, which apparently happens in some cases.
# See https://www.nlnetlabs.nl/projects/nsd/nsd.conf.5.html.
ip-transparent: yes
ip-address: XXXXXXXXXXXXXXX
include: /etc/nsd/nsd.conf.d/*.conf
root@box:/etc/nsd# ls -l /etc/nsd/nsd.conf.d/
total 0
root@box:/etc/nsd# ls /etc/nsd/zones
box.XXX.email.txt XXX.email.txt XXXXXX.com.txt
box.XXX.email.txt.ds XXX.email.txt.ds XXXXXX.com.txt.ds
box.XXX.email.txt.signed XXX.email.txt.signed XXXXXX.com.txt.signed
As far as I can tell in these files, everything looks good…
But it is not resolving domains…
Luckily it’s just my personal email I use this for, so I guess I can find time to spin up another box at some point or check something else out, but if anyone has any ideas before I go ahead and do that then I’m all ears?
