[Bug 279950] dns/nsd: nonresponsive, 100% cpu, can't be stopped short of kill -9

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 24 Jun 2024 14:22:08 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279950

--- Comment #1 from Robert William Vesterman <bob@vesterman.com> ---
I guess I should note that I've been using it (successfully) for years, until
now. Also, here's my nsd.conf:

## NSD authoritative only DNS
## nsd.conf .:. https://calomel.org
## Primary or "Master" NSD server
#

server:
  # uncomment to specify specific interfaces to bind (default all).
    ip-address: 127.0.0.1

  # port to answer queries on. default is 53.
    port: 43253

  # Number of NSD servers to fork.
    server-count: 1

  # listen only on IPv4 connections
    ip4-only: yes

  # don't answer VERSION.BIND and VERSION.SERVER CHAOS class queries
    hide-version: yes

  # identify the server (CH TXT ID.SERVER entry).
    identity: ""

  # The directory for zonefile: files.
    zonesdir: "/usr/local/etc/nsd"

zone:
    name: vestertopia.net
    zonefile: vestertopia.net.forward


zone:
    name: 168.192.in-addr.arpa
    zonefile: vestertopia.net.reverse

remote-control:
    control-enable: no

#
## NSD authoritative only DNS
## nsd.conf .:. https://calomel.org
## Primary or "Master" NSD server

-- 
You are receiving this mail because:
You are the assignee for the bug.