Hey all,
I’ve been using MIAB for a few years now and enjoy using it greatly! So thanks to Josh and all the contributors.
On one of my servers though there’s an issue that keeps cropping up where the DNS fails to resolve on the same date each month.
The things unique about this installation compared to my other instances are:
- Uses 2FA for all admin accounts
- Has a mail relay (added rules to /etc/postfix/main.cf)
nsd’s logs look like:
[2021-07-10 13:52:30.653] nsd[967]: notice: nsd starting (NSD 4.1.17)
[2021-07-10 13:52:31.591] nsd[1014]: notice: nsd started (NSD 4.1.17), pid 967
[2021-08-09 13:43:15.692] nsd[1014]: warning: signal received, shutting down...
[2021-08-09 13:43:34.053] nsd[1030]: notice: nsd starting (NSD 4.1.17)
[2021-08-09 13:43:34.995] nsd[1075]: notice: nsd started (NSD 4.1.17), pid 1030
[2021-08-09 13:46:05.997] nsd[1075]: warning: signal received, shutting down...
[2021-08-09 13:46:05.999] nsd[1030]: error: xfrd: error writing shutdown to main: Broken pipe
[2021-08-09 13:46:06.024] nsd[13638]: notice: nsd starting (NSD 4.1.17)
[2021-08-09 13:46:06.171] nsd[13652]: notice: nsd started (NSD 4.1.17), pid 13638
[2021-09-06 17:57:40.649] nsd[13652]: warning: signal received, shutting down...
[2021-09-06 17:57:40.695] nsd[9177]: notice: nsd starting (NSD 4.1.17)
[2021-09-06 17:57:40.851] nsd[9189]: notice: nsd started (NSD 4.1.17), pid 9177
[2021-09-06 17:58:35.264] nsd[9189]: warning: signal received, shutting down...
[2021-09-06 17:58:50.863] nsd[979]: notice: nsd starting (NSD 4.1.17)
[2021-09-06 17:58:51.757] nsd[1022]: notice: nsd started (NSD 4.1.17), pid 979
[2021-10-06 06:30:07.902] nsd[1022]: warning: signal received, shutting down...
[2021-10-06 06:30:25.017] nsd[970]: notice: nsd starting (NSD 4.1.17)
[2021-10-06 06:30:26.046] nsd[978]: notice: nsd started (NSD 4.1.17), pid 970
[2021-10-06 06:33:08.774] nsd[978]: warning: signal received, shutting down...
[2021-10-06 06:33:08.799] nsd[7905]: notice: nsd starting (NSD 4.1.17)
[2021-10-06 06:33:08.897] nsd[7919]: notice: nsd started (NSD 4.1.17), pid 7905
I only noticed that the server was unreachable this morning.
To recover the server I need to ssh in using the ip, and run sudo mailinabox, then it is fixed for another month.
Has anyone else run into this? I’m on the latest (v0.54) and couldn’t put a finger on when exactly this started happening, possibly when I changed the ip address of the server. As the issue crops up even after reinstalling/upgrading, I’m unsure where to look to fix this, custom DNS records?
Any help would be appreciated,
Cheers