Hetzner cloud: Public DNS (nsd4) is not running (port 53)

[33145]

Hi everyone,

I’m trying hard to setup my miab but can’t get passed the Public DNS (nsd4) is not running (port 53).

It would be great if you could help me with trouble shooting.

The following describes my latest (of many) installs on a fresh machine:

• create glue records and custom nameserver on namecheap following

  • https://www.namecheap.com/support/knowledgebase/article.aspx/768/10/how-do-i-register-personal-nameservers-for-my-domain
  • https://www.namecheap.com/support/knowledgebase/article.aspx/767/10/how-to-change-dns-for-a-domain
  • glue records look good according to
    How long does it take to propagate new ip dns glue records

• create new server + ip on hetzer. com
  name: “box.mydomain. com”
  ubuntu 18.04 size CX11
  create new public ip “box.mydomain. com”

  • assign public ip to server
    https://wiki.hetzner.de/index.php/Cloud_floating_IP_persistent/en
    add to /etc/network/interfaces.d/60-my-floating-ip.cfg

    auto eth0:1
    iface eth0:1 inet static
    address your.Float.ing.IP
    netmask 32

    sudo service networking restart

• use ssh + public ip to lock into server

• install mailinabox with floating ip
  export PUBLIC_IP=78.xx.xxx.xxx
  mailinabox -e
  Force to be on alternate IP address

  git clone --single-branch -b ubuntu_bionic --depth=1 httpsx://github.com/mail-in-a-box/mailinabox.git
  cd mailinabox
  bash setup/start.sh -e

Primary Hostname: box.xxxxxxxx-xxx. com
Public IP Address: 78.xx.xxx.xxx
Public IPv6 Address: 2a01:xxx:xxx:xxxx::x
Private IP Address: 88.xx.xx.xx
fatal: No names found, cannot describe anything.
Mail-in-a-Box Version

System Status Checks

System

• Public DNS (nsd4) is not running (port 53). <==== Locks like the main issue.

box.xxxxxxxx-xxx. com

• Nameserver glue records are incorrect. The ns1.box.xxxxxxxx-xxx. com and ns2.box.xxxxxxxx-xxx.c om
  nameservers must be configured at your domain name registrar as having the IP address 78.xx.xxx.xx.
  They currently report addresses of [Not Set]/[Not Set]. It may take several hours for public DNS to update after a change.
• This domain must resolve to your box’s IP address (xxxxxxxxxxxxx / xxxxxxxxxxxxxxxxxxxx) in public DNS but it currently resolves to [Not Set] / [Not Set].
  It may take several hours for public DNS to update after a change. This problem may result from other issues listed above.
• Your box’s reverse DNS is currently static.xxxxxxxxxxxxx.box.xxxxxxxxxxxx. com (IPv4) and [Not Set] (IPv6),
  but it should be box.xxxxxxxx-xxx. com. Your ISP or cloud provider will have instructions on setting up reverse DNS for your box.

evidence that miab can be made to work on hetzner clout

• How long does it take to propagate new ip dns glue records
• https://news.ycombinator.com/item?id=21632847

Sorry, new users can only put 2 links in a post.

Please see post below for links
Apparently I’m not new anymore.

[33145]

root@box:~#     systemctl status -l nsd
● nsd.service - Name Server Daemon
   Loaded: loaded (/lib/systemd/system/nsd.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-12-23 14:58:34 CET; 4h 56min ago
 Main PID: 18922 (nsd)
    Tasks: 3 (limit: 2299)
   CGroup: /system.slice/nsd.service
           ├─18922 /usr/sbin/nsd -d
           ├─18934 /usr/sbin/nsd -d
           └─18940 /usr/sbin/nsd -d

Dec 23 14:58:34 box.XXXXXXXX-dev.com systemd[1]: Stopped Name Server Daemon.
Dec 23 14:58:34 box.XXXXXXXX-dev.com systemd[1]: Started Name Server Daemon.

-- Logs begin at Mon 2019-12-23 14:36:34 CET, end at Mon 2019-12-23 19:56:56 CET. --
Dec 23 14:49:24 box.xxxxxxxx-dev.com systemd[1]: Started Name Server Daemon.
Dec 23 14:49:24 box.xxxxxxxx-dev.com nsd[19463]: nsd starting (NSD 4.1.17)
Dec 23 14:49:24 box.xxxxxxxx-dev.com nsd[19463]: [2019-12-23 14:49:24.923] nsd[19463]: notice: nsd starting (NSD 4.1.17)
Dec 23 14:49:24 box.xxxxxxxx-dev.com nsd[19463]: can't bind udp socket: Address already in use
Dec 23 14:49:24 box.xxxxxxxx-dev.com nsd[19463]: [2019-12-23 14:49:24.924] nsd[19463]: error: can't bind udp socket: Address already in use
Dec 23 14:49:24 box.xxxxxxxx-dev.com nsd[19463]: server initialization failed, nsd could not be started
Dec 23 14:49:24 box.xxxxxxxx-dev.com nsd[19463]: [2019-12-23 14:49:24.924] nsd[19463]: error: server initialization failed, nsd could not be started
Dec 23 14:49:24 box.xxxxxxxx-dev.com systemd[1]: nsd.service: Main process exited, code=exited, status=1/FAILURE
Dec 23 14:49:24 box.xxxxxxxx-dev.com systemd[1]: nsd.service: Failed with result 'exit-code'.
Dec 23 14:49:25 box.xxxxxxxx-dev.com systemd[1]: nsd.service: Service hold-off time over, scheduling restart.
Dec 23 14:49:25 box.xxxxxxxx-dev.com systemd[1]: nsd.service: Scheduled restart job, restart counter is at 1.
Dec 23 14:49:25 box.xxxxxxxx-dev.com systemd[1]: Stopped Name Server Daemon.
Dec 23 14:49:25 box.xxxxxxxx-dev.com systemd[1]: Started Name Server Daemon.
Dec 23 14:49:25 box.xxxxxxxx-dev.com nsd[19503]: nsd starting (NSD 4.1.17)
Dec 23 14:49:25 box.xxxxxxxx-dev.com nsd[19503]: [2019-12-23 14:49:25.181] nsd[19503]: notice: nsd starting (NSD 4.1.17)
Dec 23 14:49:25 box.xxxxxxxx-dev.com nsd[19503]: [2019-12-23 14:49:25.181] nsd[19503]: error: can't bind udp socket: Address already in use
Dec 23 14:49:25 box.xxxxxxxx-dev.com nsd[19503]: [2019-12-23 14:49:25.181] nsd[19503]: error: server initialization failed, nsd could not be started
Dec 23 14:49:25 box.xxxxxxxx-dev.com nsd[19503]: can't bind udp socket: Address already in use
Dec 23 14:49:25 box.xxxxxxxx-dev.com nsd[19503]: server initialization failed, nsd could not be started
Dec 23 14:49:25 box.xxxxxxxx-dev.com systemd[1]: nsd.service: Main process exited, code=exited, status=1/FAILURE
Dec 23 14:49:25 box.xxxxxxxx-dev.com systemd[1]: nsd.service: Failed with result 'exit-code'.
Dec 23 14:49:25 box.xxxxxxxx-dev.com systemd[1]: nsd.service: Service hold-off time over, scheduling restart.
Dec 23 14:49:25 box.xxxxxxxx-dev.com systemd[1]: nsd.service: Scheduled restart job, restart counter is at 2.
Dec 23 14:49:25 box.xxxxxxxx-dev.com systemd[1]: Stopped Name Server Daemon.
Dec 23 14:49:25 box.xxxxxxxx-dev.com systemd[1]: Started Name Server Daemon.
Dec 23 14:49:25 box.xxxxxxxx-dev.com nsd[19530]: nsd starting (NSD 4.1.17)

[alento]

Two questions … why can you not use the primary IP that Hetzner assigns rather than a floating IP address?

and have you actually tried installing following the MiaB setup guide instructions?

[33145]

Thanks, for asking.

why can you not use the primary IP that Hetzner assigns rather than a floating IP address?

Advantage of floating IP is that I can keep it even when upgrading or resetting server.

I had the impression that having a steady and clean IP is important.

have you actually tried installing following the MiaB setup guide instructions?

yes, that’s what I have used. I guess the only difference should be the -e for the public IP.

[alento]

@33145

Advantage of floating IP is that I can keep it even when upgrading or resetting server.

I will admit that I am not a Hetzner customer (yet) so I asked a couple of other Hetzner customers and you do NOT have to maintain a floating IP to keep it - the assigned IP address will be valid as long as you do not destroy the instance. It should survive a OS reinstall from what I was told.

@33145

yes, that’s what I have used. I guess the only difference should be the -e for the public IP.

I see a few other modifications - the most striking ones being the configuration of the floating IP with the network card, as well as cloning the repository outside of the MiaB install script.

The issue you are having seems related to the floating IP address. I do not know what affect, if any cloning the script again from github may have, but as it is not a part of the actual documented install procedure, it is suspect, IMHO.

[33145]

Thanks for asking around.

valid as long as you do not destroy the instance.

Right, but upgrading will destroy the instance. I didn’t now that OS reinstall is possible without destroying, that’s interesting I have to check that.

cloning the repository outside of the MiaB install script.

This is straight from repo README, but I have also done it the regular way with exactly the same result.

the most striking ones being the configuration of the floating IP

I’m pretty sure that’s what’s causing the trouble. The floating IP is ipv4 only, I have read elsewhere
that not having ipv6 can cause trouble.

[alento]

@33145

I have read elsewhere
that not having ipv6 can cause trouble.

I cannot remember for certain, but it seems that if you disable IPv6 then it will work.

[33145]

Okay, without the floating ip everything worked straight away.

Hetzner allows to reinstall OS and to keep server (and ip) when moving to larger instance and disk (only downgrade isn’t possible afterwards).

For me the benefits of a public are not big enough to keep trying to get the floating ip to work.
Without it I can recommend hetzner so far.