DNS output is blocked, or delayed, or something

named BIND 9.18.33 (Extended Support Version)

I upgraded the hardware on an old (12 year) system that was functioning adequately, so that I can upgrade the OS to LEAP 16. The transition went well but for DNS issues.

The named configuration has not changed in any way. Only the hardware changed.

The firewall’s public zone allow DNS traffic. As it did before the hardware change.

Any suggestions what may be causing this?

The startup log is below. It looks good except for resolver priming query complete: timed out. Something is preventing all outgoing DNS queries. For instance, this blocks outgoing mail, network time requests, browser traffic, any service that runs locally and requires a DNS resolution.

I can SSH to the host. It can resolve local (internal) DNS queries.

17-May-2026 16:35:36.168 zoneload: info: managed-keys-zone: loaded serial 1947
17-May-2026 16:35:36.172 zoneload: info: zone 0.0.127.in-addr.arpa/IN: loaded serial 42
17-May-2026 16:35:36.172 zoneload: info: zone 109.88.192.in-addr.arpa/IN: loaded serial 2025060379 (DNSSEC signed)
17-May-2026 16:35:36.172 zoneload: info: zone 69.168.192.in-addr.arpa/IN: loaded serial 22111902
17-May-2026 16:35:36.172 zoneload: info: zone sma.com/IN: loaded serial 22111909
17-May-2026 16:35:36.172 zoneload: info: zone sma-inc.us/IN: loaded serial 2025060455 (DNSSEC signed)
17-May-2026 16:35:36.172 zoneload: info: zone localhost/IN: loaded serial 42
17-May-2026 16:35:36.172 notify: info: zone sma-inc.us/IN: sending notifies (serial 2025060455)
17-May-2026 16:35:36.172 general: notice: all zones loaded
17-May-2026 16:35:36.172 general: notice: running
17-May-2026 16:35:46.178 resolver: notice: resolver priming query complete: timed out
17-May-2026 16:37:27.345 resolver: notice: resolver priming query complete: timed out

Some hardware info about the network interface.

$ sudo ifstatus eth0
eth0            up
      link:     #2, state up, mtu 1500
      type:     ethernet, hwaddr a0:ad:9f:32:9d:74
      config:   compat:suse:/etc/sysconfig/network/ifcfg-eth0
      leases:   ipv4 static granted
      leases:   ipv6 static granted
      addr:     ipv4 192.168.69.246/24 [static]
      addr:     ipv6 fd2f:4760:521f:3f3c::c0a8:45f6/64 [static]
      addr:     ipv6 fd2f:4760:521f:3f3c:fc61:2c72:5c0:26f3/64
      addr:     ipv6 fd2f:4760:521f:3f3c:a2ad:9fff:fe32:9d74/64
      addr:     ipv6 fd2f:4760:521f:3f3c:602e:194b:25fb:3c35/64
      route:    ipv6 default via fe80::2eb8:edff:fe5a:9d44 metric 1024 proto ra

ns1 is the localhost that is broken.

$ host ibm.com ns1
;; communications error to fd2f:4760:521f:3f3c::c0a8:45f6#53: timed out
Using domain server:
Name: ns1
Address: 192.168.69.246#53
Aliases: 

Host ibm.com not found: 2(SERVFAIL)

I don’t see an IPv4 default route in the output you posted. Only an IPv6 default route appears present.

That would explain why recursive DNS lookups, outbound mail, NTP, etc are failing even though local zones still resolve.

Yes! Thank you.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.