30-Apr-2026 02:18:40.488 general: debug 1: now using logging configuration from config file
30-Apr-2026 02:18:40.488 general: debug 1: loop exclusive mode: ending
30-Apr-2026 02:18:40.488 general: debug 1: loop exclusive mode: ended
30-Apr-2026 02:18:40.488 general: notice: command channel listening on 127.0.0.1#8094
30-Apr-2026 02:18:40.488 general: info: VDNS cleanup pass1: 0 departing views cleared
30-Apr-2026 02:18:40.488 general: info: VDNS cleanup pass2: 2 staying views re-checked
30-Apr-2026 02:18:40.488 general: debug 1: load_configuration: success
30-Apr-2026 02:18:40.488 general: debug 1: loop exclusive mode: starting
30-Apr-2026 02:18:40.492 general: debug 1: loop exclusive mode: started
30-Apr-2026 02:18:40.492 zoneload: debug 1: managed-keys-zone: starting load
30-Apr-2026 02:18:40.492 general: debug 1: zone_startload: managed-keys-zone: enter
30-Apr-2026 02:18:40.492 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
30-Apr-2026 02:18:40.492 general: debug 1: managed-keys-zone: creating SOA
30-Apr-2026 02:18:40.492 zoneload: debug 1: managed-keys-zone: loaded; checking validity
30-Apr-2026 02:18:40.492 zoneload: info: managed-keys-zone: loaded serial 0
30-Apr-2026 02:18:40.492 general: debug 1: loop exclusive mode: ending
30-Apr-2026 02:18:40.492 zoneload: debug 1: zone version.bind/CH: starting load
30-Apr-2026 02:18:40.492 zoneload: debug 1: zone hostname.bind/CH: starting load
30-Apr-2026 02:18:40.492 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
30-Apr-2026 02:18:40.492 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
30-Apr-2026 02:18:40.492 general: debug 1: zone__settimer: zone version.bind/CH: enter
30-Apr-2026 02:18:40.492 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
30-Apr-2026 02:18:40.492 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 02:18:40.492 zoneload: debug 1: zone authors.bind/CH: starting load
30-Apr-2026 02:18:40.492 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
30-Apr-2026 02:18:40.492 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
30-Apr-2026 02:18:40.492 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
30-Apr-2026 02:18:40.492 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
30-Apr-2026 02:18:40.492 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
30-Apr-2026 02:18:40.492 general: debug 1: zone__settimer: zone authors.bind/CH: enter
30-Apr-2026 02:18:40.492 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
30-Apr-2026 02:18:40.492 zoneload: debug 1: zone id.server/CH: starting load
30-Apr-2026 02:18:40.492 zoneload: debug 1: zone id.server/CH: loaded; checking validity
30-Apr-2026 02:18:40.492 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
30-Apr-2026 02:18:40.492 general: debug 1: loop exclusive mode: ended
30-Apr-2026 02:18:40.492 general: notice: all zones loaded
30-Apr-2026 02:18:40.492 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
30-Apr-2026 02:18:40.492 general: debug 1: zone_maintenance: zone version.bind/CH: enter
30-Apr-2026 02:18:40.492 general: debug 1: zone__settimer: zone authors.bind/CH: enter
30-Apr-2026 02:18:40.492 general: debug 1: managed-keys-zone: synchronizing trusted keys
30-Apr-2026 02:18:40.492 general: debug 1: create_keydata: managed-keys-zone: enter
30-Apr-2026 02:18:40.492 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
30-Apr-2026 02:18:40.492 general: debug 1: managed-keys-zone: next key refresh: 30-Apr-2026 02:18:40.492
30-Apr-2026 02:18:40.492 general: debug 1: zone_journal: managed-keys-zone: enter
30-Apr-2026 02:18:40.492 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
30-Apr-2026 02:18:40.492 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 02:18:40.496 general: debug 1: zone__settimer: zone version.bind/CH: enter
30-Apr-2026 02:18:40.504 general: debug 1: zone_needdump: managed-keys-zone: enter
30-Apr-2026 02:18:40.504 general: notice: FIPS mode is disabled
30-Apr-2026 02:18:40.504 general: notice: running
30-Apr-2026 02:18:40.504 general: debug 1: debug: t1-cloud-fixed version
30-Apr-2026 02:18:40.504 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
30-Apr-2026 02:18:40.504 general: debug 1: zone_maintenance: managed-keys-zone: enter
30-Apr-2026 02:18:40.504 general: debug 1: zone__settimer: zone version.bind/CH: enter
30-Apr-2026 02:18:40.504 general: debug 1: zone__settimer: zone id.server/CH: enter
30-Apr-2026 02:18:40.504 general: debug 1: zone__settimer: zone id.server/CH: enter
30-Apr-2026 02:18:40.504 general: debug 1: zone_maintenance: zone id.server/CH: enter
30-Apr-2026 02:18:40.504 general: debug 1: zone__settimer: zone id.server/CH: enter
30-Apr-2026 02:18:40.504 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
30-Apr-2026 02:18:40.504 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
30-Apr-2026 02:18:40.504 general: debug 1: managed-keys-zone: next key refresh: 30-Apr-2026 02:18:40.504
30-Apr-2026 02:18:40.504 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 02:18:40.504 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 02:18:40.504 general: debug 1: zone__settimer: zone authors.bind/CH: enter
30-Apr-2026 02:18:40.504 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 02:18:40.504 resolver: debug 1: fetch: ./DNSKEY
30-Apr-2026 02:18:40.504 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 02:18:40.504 resolver: debug 1: fetch: ./NS
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
30-Apr-2026 02:18:40.504 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
30-Apr-2026 02:18:40.508 database: debug 1: delete_node(): 0x7ff3d0002220 . (bucket 0)
30-Apr-2026 02:18:40.508 resolver: debug 1: fetch: ./DNSKEY
30-Apr-2026 02:18:40.508 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
30-Apr-2026 02:18:40.508 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
30-Apr-2026 02:18:40.508 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
30-Apr-2026 02:18:40.556 dnssec: warning: managed-keys-zone: Initializing automatic trust anchor management for zone '.'; DNSKEY ID 20326 is now trusted, waiving the normal 30-day waiting period.
30-Apr-2026 02:18:40.556 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
30-Apr-2026 02:18:40.556 general: debug 1: managed-keys-zone: next key refresh: 01-May-2026 02:18:40.556
30-Apr-2026 02:18:40.556 dnssec: warning: managed-keys-zone: Initializing automatic trust anchor management for zone '.'; DNSKEY ID 38696 is now trusted, waiving the normal 30-day waiting period.
30-Apr-2026 02:18:40.556 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
30-Apr-2026 02:18:40.556 general: debug 1: managed-keys-zone: next key refresh: 01-May-2026 02:18:40.556
30-Apr-2026 02:18:40.556 general: debug 1: zone_journal: managed-keys-zone: enter
30-Apr-2026 02:18:40.564 general: debug 1: zone_needdump: managed-keys-zone: enter
30-Apr-2026 02:18:40.564 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 02:18:40.564 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 02:18:40.564 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 02:18:40.564 resolver: debug 1: resolver priming query complete: success
30-Apr-2026 02:18:41.704 general: info: received control channel command 'reconfig'
30-Apr-2026 02:18:41.704 general: debug 1: loop exclusive mode: starting
30-Apr-2026 02:18:41.728 general: debug 1: loop exclusive mode: started
30-Apr-2026 02:18:41.728 general: info: loading configuration from '/etc/contrail/dns/contrail-named.conf'
30-Apr-2026 02:18:41.728 general: info: the working directory is now '/etc/contrail/dns'
30-Apr-2026 02:18:41.728 general: info: using default UDP/IPv4 port range: [32768, 60999]
30-Apr-2026 02:18:41.728 general: info: using default UDP/IPv6 port range: [32768, 60999]
30-Apr-2026 02:18:41.728 general: info: Disabling periodic interface re-scans timer
30-Apr-2026 02:18:41.728 config: debug 1: none:215: dnssec-policy: load policy 'default'
30-Apr-2026 02:18:41.728 config: debug 1: none:238: dnssec-policy: load policy 'insecure'
30-Apr-2026 02:18:41.732 security: info: using built-in root key for view _default_view_
30-Apr-2026 02:18:41.732 general: info: set up managed keys zone for view _default_view_, file '/etc/contrail/dns/_default_view_.mkeys'
30-Apr-2026 02:18:41.732 general: debug 1: now using logging configuration from config file
30-Apr-2026 02:18:41.732 general: debug 1: loop exclusive mode: ending
30-Apr-2026 02:18:41.732 general: debug 1: loop exclusive mode: ended
30-Apr-2026 02:18:41.732 general: info: VDNS cleanup pass1: 2 departing views cleared
30-Apr-2026 02:18:41.732 general: info: VDNS cleanup pass2: 2 staying views re-checked
30-Apr-2026 02:18:41.732 general: info: VDNS detach view '_default' refcount=1
30-Apr-2026 02:18:41.736 general: debug 1: managed-keys-zone: final reference detached
30-Apr-2026 02:18:41.736 general: info: VDNS detach view '_bind' refcount=1
30-Apr-2026 02:18:41.736 database: debug 1: calling free_qpdb(.)
30-Apr-2026 02:18:41.736 database: debug 1: done free_qpdb(.)
30-Apr-2026 02:18:41.736 database: debug 1: calling free_qpdb(.)
30-Apr-2026 02:18:41.736 database: debug 1: called free_qpdb(.)
30-Apr-2026 02:18:41.736 general: debug 1: load_configuration: success
30-Apr-2026 02:18:41.736 general: info: reloading configuration succeeded
30-Apr-2026 02:18:41.736 general: debug 1: loop exclusive mode: starting
30-Apr-2026 02:18:41.740 general: debug 1: loop exclusive mode: started
30-Apr-2026 02:18:41.740 zoneload: debug 1: managed-keys-zone/_default_view_: starting load
30-Apr-2026 02:18:41.740 general: debug 1: zone_startload: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.740 zoneload: debug 1: managed-keys-zone/_default_view_: loading from master file /etc/contrail/dns/_default_view_.mkeys failed: file not found
30-Apr-2026 02:18:41.740 general: debug 1: managed-keys-zone/_default_view_: creating SOA
30-Apr-2026 02:18:41.740 zoneload: debug 1: managed-keys-zone/_default_view_: loaded; checking validity
30-Apr-2026 02:18:41.740 zoneload: info: managed-keys-zone/_default_view_: loaded serial 0
30-Apr-2026 02:18:41.740 general: debug 1: loop exclusive mode: ending
30-Apr-2026 02:18:41.740 general: debug 1: loop exclusive mode: ended
30-Apr-2026 02:18:41.740 general: info: scheduled loading new zones
30-Apr-2026 02:18:41.740 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.740 general: info: any newly configured zones are now loaded
30-Apr-2026 02:18:41.740 general: debug 1: managed-keys-zone/_default_view_: synchronizing trusted keys
30-Apr-2026 02:18:41.740 general: debug 1: create_keydata: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.740 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.740 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 30-Apr-2026 02:18:41.740
30-Apr-2026 02:18:41.740 general: debug 1: zone_journal: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.740 general: debug 1: journal file /etc/contrail/dns/_default_view_.mkeys.jnl does not exist, creating it
30-Apr-2026 02:18:41.740 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.748 general: debug 1: zone_needdump: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.748 general: notice: FIPS mode is disabled
30-Apr-2026 02:18:41.748 general: notice: running
30-Apr-2026 02:18:41.748 general: debug 1: debug: t1-cloud-fixed version
30-Apr-2026 02:18:41.748 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
30-Apr-2026 02:18:41.748 general: debug 1: zone_maintenance: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.748 general: debug 1: zone_refreshkeys: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.748 general: debug 1: zone__settimer: zone id.server/CH: enter
30-Apr-2026 02:18:41.748 general: debug 1: zone__settimer: zone authors.bind/CH: enter
30-Apr-2026 02:18:41.748 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.748 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 30-Apr-2026 02:18:41.748
30-Apr-2026 02:18:41.748 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.748 general: debug 1: zone__settimer: zone version.bind/CH: enter
30-Apr-2026 02:18:41.748 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.748 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.748 resolver: debug 1: fetch: ./DNSKEY
30-Apr-2026 02:18:41.748 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.748 resolver: debug 1: fetch: ./NS
30-Apr-2026 02:18:41.752 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
30-Apr-2026 02:18:41.752 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
30-Apr-2026 02:18:41.752 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
30-Apr-2026 02:18:41.752 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
30-Apr-2026 02:18:41.752 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
30-Apr-2026 02:18:41.752 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
30-Apr-2026 02:18:41.752 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
30-Apr-2026 02:18:41.752 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
30-Apr-2026 02:18:41.752 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
30-Apr-2026 02:18:41.752 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
30-Apr-2026 02:18:41.752 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
30-Apr-2026 02:18:41.752 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
30-Apr-2026 02:18:41.752 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
30-Apr-2026 02:18:41.752 dnssec: warning: managed-keys-zone/_default_view_: Initializing automatic trust anchor management for zone '.'; DNSKEY ID 20326 is now trusted, waiving the normal 30-day waiting period.
30-Apr-2026 02:18:41.752 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.752 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 01-May-2026 02:18:41.752
30-Apr-2026 02:18:41.752 dnssec: warning: managed-keys-zone/_default_view_: Initializing automatic trust anchor management for zone '.'; DNSKEY ID 38696 is now trusted, waiving the normal 30-day waiting period.
30-Apr-2026 02:18:41.752 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.752 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 01-May-2026 02:18:41.752
30-Apr-2026 02:18:41.752 general: debug 1: zone_journal: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.760 general: debug 1: zone_needdump: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.760 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.760 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.760 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:18:41.800 resolver: debug 1: resolver priming query complete: success
30-Apr-2026 02:19:06.784 general: debug 1: zone_maintenance: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:19:06.784 general: debug 1: zone_dump: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:19:06.784 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:19:06.960 general: debug 1: dump_done: managed-keys-zone/_default_view_: enter
30-Apr-2026 02:19:06.960 general: debug 1: zone_journal_compact: managed-keys-zone/_default_view_: target journal size 0
30-Apr-2026 02:22:43.453 network: info: listening on IPv6 interface vhost0, fe80::f816:3eff:fefe:ba3b%8#53
30-Apr-2026 02:22:43.457 network: info: no longer listening on 10.20.0.254#53
30-Apr-2026 02:22:43.461 network: info: listening on IPv4 interface vhost0, 10.20.0.254#53
30-Apr-2026 02:22:43.481 network: info: no longer listening on fe80::f816:3eff:fefe:ba3b%3#53
30-Apr-2026 02:22:46.453 network: info: listening on IPv6 interface pkt0, fe80::4c28:8fff:fe89:284f%9#53
30-Apr-2026 02:24:57.752 network: info: listening on IPv6 interface vethacf0b24d-a, fe80::68b6:46ff:feff:345%12#53
30-Apr-2026 02:24:57.756 network: info: listening on IPv6 interface veth90859b5f-7, fe80::d861:c9ff:fe06:4da7%13#53
30-Apr-2026 02:25:17.525 network: info: listening on IPv6 interface veth0430e31f-1, fe80::64ff:44ff:fe4f:da36%14#53
30-Apr-2026 02:25:17.561 network: info: listening on IPv6 interface veth458d7ed2-d, fe80::6889:90ff:fe52:78c9%15#53
30-Apr-2026 02:25:22.357 network: info: no longer listening on fe80::64ff:44ff:fe4f:da36%14#53
30-Apr-2026 02:25:22.417 network: info: no longer listening on fe80::6889:90ff:fe52:78c9%15#53
30-Apr-2026 02:26:08.758 network: info: listening on IPv6 interface veth7d5035aa-c, fe80::ac9f:21ff:fe1b:4246%18#53
30-Apr-2026 02:26:08.758 network: info: listening on IPv6 interface veth23d77f02-6, fe80::48d9:99ff:feff:1617%19#53