Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: systemd unit for zoneserver #83
    maradns
    Keymaster

    This is a very interesting bug and I do not know why zoneserver and only zoneserver acts this way. I can tell you this much: zoneserver also is the only service I can not start up in a podman (CentOS 8’s Docker clone); when I try to start up zoneserver in a Podman container, I get a “fork error”.

    Zoneserver uses the fork() model to handle incoming connections. When an incoming connecting comes in via TCP, Zoneserver forks a sub-process to handle the DNS-over-TCP connection. While this is not particularly efficient, it allowed me to fairly quickly get the “has support for TCP” checkbox checked when I was trying to get a fully functional basic DNS server out the door as quickly as possible back when Bind was the only open source DNS server and the Internet community felt having that kind of monoculture was not healthy.

    I have not gotten to the bottom of zoneserver’s issue with systemd or with Podman. I also know that newer versions of Dig have issues with the form of DNS-over-TCP packets sent by MaraDNS (and, I believe, zoneserver), so DNS-over-TCP has been relegated to the back burner: DNS is perfectly usable over just UDP, and DNS-over-TCP just really isn’t used except for zone transfers.

    in reply to: systemd unit for zoneserver #78
    maradns
    Keymaster

    Here is MaraDNS’s zoneserver system start up script:

    https://github.com/samboy/MaraDNS/blob/master/build/zoneserver.startup

    in reply to: systemd unit for zoneserver #77
    maradns
    Keymaster

    The entire system for starting up MaraDNS daemons was set up back in the days when System V Init was the standard way to starting up services, long before systemd was even a glint in Lennart Poettering and Kay Sievers’s eyes.

    That in mind, I’m not surprised that some of MaraDNS has a hard time starting up with systemd.

    The standard way to start up all MaraDNS services is to use the Duende daemonizer to make the service in question a daemon. For example, from a fresh compile of MaraDNS, in the tcp directory where zoneserver is compiled:

    duende zoneserver -f ../doc/en/examples/example_mararc

    So, I think the issue is that, here in 2020, we need to look in to getting things to work with systemd. At which point I am going to give you a rant:

    There are a number of different distributions of Linux out there, and they each have their own way of starting up and managing processes. Things got so messy, DJB gave up and created his own daemonizer and setup for starting and starting Qmail and DJBdns so that things would be consistent distribution to distribution.

    I won’t go that far, but I’m using CentOS 8 across the board here so if I go the route of getting everything to work with systemd, everything will work with CentOS 8’s version of systemd. Things may or may not work with Ubuntu or Debian.

    In the meantime, just add duende to the command line given to systemd so that Zoneserver is a sub-process of duende (actually, duende was not there at first and there was a time Zoneserver was just a background job in Bash).

Viewing 3 posts - 1 through 3 (of 3 total)