30-Mar-2026 03:39:28.336 general: debug 1: now using logging configuration from config file
30-Mar-2026 03:39:28.336 general: debug 1: loop exclusive mode: ending
30-Mar-2026 03:39:28.336 general: debug 1: loop exclusive mode: ended
30-Mar-2026 03:39:28.336 general: notice: command channel listening on 127.0.0.1#8094
30-Mar-2026 03:39:28.336 general: info: VDNS cleanup pass1: 0 departing views cleared
30-Mar-2026 03:39:28.336 general: info: VDNS cleanup pass2: 2 staying views re-checked
30-Mar-2026 03:39:28.336 general: debug 1: load_configuration: success
30-Mar-2026 03:39:28.336 general: debug 1: loop exclusive mode: starting
30-Mar-2026 03:39:28.348 general: debug 1: loop exclusive mode: started
30-Mar-2026 03:39:28.348 zoneload: debug 1: managed-keys-zone: starting load
30-Mar-2026 03:39:28.348 general: debug 1: zone_startload: managed-keys-zone: enter
30-Mar-2026 03:39:28.348 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
30-Mar-2026 03:39:28.348 general: debug 1: managed-keys-zone: creating SOA
30-Mar-2026 03:39:28.348 zoneload: debug 1: managed-keys-zone: loaded; checking validity
30-Mar-2026 03:39:28.348 zoneload: info: managed-keys-zone: loaded serial 0
30-Mar-2026 03:39:28.348 general: debug 1: loop exclusive mode: ending
30-Mar-2026 03:39:28.348 zoneload: debug 1: zone id.server/CH: starting load
30-Mar-2026 03:39:28.348 zoneload: debug 1: zone hostname.bind/CH: starting load
30-Mar-2026 03:39:28.348 zoneload: debug 1: zone authors.bind/CH: starting load
30-Mar-2026 03:39:28.348 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
30-Mar-2026 03:39:28.348 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 03:39:28.348 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
30-Mar-2026 03:39:28.348 zoneload: debug 1: zone id.server/CH: loaded; checking validity
30-Mar-2026 03:39:28.348 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
30-Mar-2026 03:39:28.348 zoneload: debug 1: zone version.bind/CH: starting load
30-Mar-2026 03:39:28.348 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
30-Mar-2026 03:39:28.348 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
30-Mar-2026 03:39:28.348 general: debug 1: loop exclusive mode: ended
30-Mar-2026 03:39:28.348 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
30-Mar-2026 03:39:28.348 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
30-Mar-2026 03:39:28.348 general: debug 1: zone__settimer: zone version.bind/CH: enter
30-Mar-2026 03:39:28.348 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
30-Mar-2026 03:39:28.348 general: debug 1: zone_maintenance: zone version.bind/CH: enter
30-Mar-2026 03:39:28.348 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
30-Mar-2026 03:39:28.348 general: debug 1: zone__settimer: zone version.bind/CH: enter
30-Mar-2026 03:39:28.348 general: debug 1: zone__settimer: zone authors.bind/CH: enter
30-Mar-2026 03:39:28.348 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
30-Mar-2026 03:39:28.348 general: debug 1: zone__settimer: zone authors.bind/CH: enter
30-Mar-2026 03:39:28.352 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
30-Mar-2026 03:39:28.352 general: notice: all zones loaded
30-Mar-2026 03:39:28.352 general: debug 1: managed-keys-zone: synchronizing trusted keys
30-Mar-2026 03:39:28.352 general: debug 1: create_keydata: managed-keys-zone: enter
30-Mar-2026 03:39:28.352 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
30-Mar-2026 03:39:28.352 general: debug 1: managed-keys-zone: next key refresh: 30-Mar-2026 03:39:28.352
30-Mar-2026 03:39:28.352 general: debug 1: zone_journal: managed-keys-zone: enter
30-Mar-2026 03:39:28.352 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
30-Mar-2026 03:39:28.352 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 03:39:28.364 general: debug 1: zone_needdump: managed-keys-zone: enter
30-Mar-2026 03:39:28.364 general: notice: FIPS mode is disabled
30-Mar-2026 03:39:28.364 general: notice: running
30-Mar-2026 03:39:28.364 general: debug 1: debug: t1-cloud-fixed version
30-Mar-2026 03:39:28.364 general: debug 1: zone__settimer: zone id.server/CH: enter
30-Mar-2026 03:39:28.364 general: debug 1: zone__settimer: zone id.server/CH: enter
30-Mar-2026 03:39:28.364 general: debug 1: zone_maintenance: zone id.server/CH: enter
30-Mar-2026 03:39:28.364 general: debug 1: zone__settimer: zone id.server/CH: enter
30-Mar-2026 03:39:28.364 general: debug 1: zone_maintenance: managed-keys-zone: enter
30-Mar-2026 03:39:28.364 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
30-Mar-2026 03:39:28.364 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
30-Mar-2026 03:39:28.364 general: debug 1: managed-keys-zone: next key refresh: 30-Mar-2026 03:39:28.364
30-Mar-2026 03:39:28.364 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 03:39:28.364 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 03:39:28.364 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 03:39:28.364 resolver: debug 1: fetch: ./DNSKEY
30-Mar-2026 03:39:28.364 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 03:39:28.364 resolver: debug 1: fetch: ./NS
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
30-Mar-2026 03:39:28.364 general: debug 1: zone__settimer: zone version.bind/CH: enter
30-Mar-2026 03:39:28.364 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
30-Mar-2026 03:39:28.364 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
30-Mar-2026 03:39:28.364 general: debug 1: zone__settimer: zone authors.bind/CH: enter
30-Mar-2026 03:39:28.412 database: debug 1: delete_node(): 0x7ff6980cbd40 . (bucket 4)
30-Mar-2026 03:39:28.412 resolver: debug 1: fetch: ./DNSKEY
30-Mar-2026 03:39:28.412 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
30-Mar-2026 03:39:28.412 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
30-Mar-2026 03:39:28.412 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
30-Mar-2026 03:39:28.412 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
30-Mar-2026 03:39:28.412 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
30-Mar-2026 03:39:28.412 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
30-Mar-2026 03:39:28.412 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
30-Mar-2026 03:39:28.420 database: debug 1: delete_node(): 0x7ff6980e2310 . (bucket 3)
30-Mar-2026 03:39:28.420 resolver: debug 1: resolver priming query complete: success
30-Mar-2026 03:39:28.500 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-Mar-2026 03:39:28.500 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
30-Mar-2026 03:39:28.500 general: debug 1: managed-keys-zone: next key refresh: 31-Mar-2026 03:39:28.500
30-Mar-2026 03:39:28.500 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-Mar-2026 03:39:28.500 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
30-Mar-2026 03:39:28.500 general: debug 1: managed-keys-zone: next key refresh: 31-Mar-2026 03:39:28.500
30-Mar-2026 03:39:28.500 general: debug 1: zone_journal: managed-keys-zone: enter
30-Mar-2026 03:39:28.508 general: debug 1: zone_needdump: managed-keys-zone: enter
30-Mar-2026 03:39:28.508 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 03:39:28.508 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 03:39:28.508 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 03:39:29.508 general: info: received control channel command 'reconfig'
30-Mar-2026 03:39:29.508 general: debug 1: loop exclusive mode: starting
30-Mar-2026 03:39:29.508 general: debug 1: loop exclusive mode: started
30-Mar-2026 03:39:29.508 general: info: loading configuration from '/etc/contrail/dns/contrail-named.conf'
30-Mar-2026 03:39:29.508 general: info: the working directory is now '/etc/contrail/dns'
30-Mar-2026 03:39:29.508 general: info: using default UDP/IPv4 port range: [32768, 60999]
30-Mar-2026 03:39:29.508 general: info: using default UDP/IPv6 port range: [32768, 60999]
30-Mar-2026 03:39:29.508 general: info: Disabling periodic interface re-scans timer
30-Mar-2026 03:39:29.508 config: debug 1: none:215: dnssec-policy: load policy 'default'
30-Mar-2026 03:39:29.508 config: debug 1: none:238: dnssec-policy: load policy 'insecure'
30-Mar-2026 03:39:29.508 security: info: using built-in root key for view _default_view_
30-Mar-2026 03:39:29.508 general: info: set up managed keys zone for view _default_view_, file '/etc/contrail/dns/_default_view_.mkeys'
30-Mar-2026 03:39:29.512 general: debug 1: now using logging configuration from config file
30-Mar-2026 03:39:29.512 general: debug 1: loop exclusive mode: ending
30-Mar-2026 03:39:29.512 general: debug 1: loop exclusive mode: ended
30-Mar-2026 03:39:29.512 general: info: VDNS cleanup pass1: 2 departing views cleared
30-Mar-2026 03:39:29.512 general: info: VDNS cleanup pass2: 2 staying views re-checked
30-Mar-2026 03:39:29.512 general: info: VDNS detach view '_default' refcount=1
30-Mar-2026 03:39:29.512 general: debug 1: managed-keys-zone: final reference detached
30-Mar-2026 03:39:29.512 general: info: VDNS detach view '_bind' refcount=1
30-Mar-2026 03:39:29.512 database: debug 1: calling free_qpdb(.)
30-Mar-2026 03:39:29.512 database: debug 1: done free_qpdb(.)
30-Mar-2026 03:39:29.512 database: debug 1: calling free_qpdb(.)
30-Mar-2026 03:39:29.512 database: debug 1: called free_qpdb(.)
30-Mar-2026 03:39:29.512 general: debug 1: load_configuration: success
30-Mar-2026 03:39:29.512 general: info: reloading configuration succeeded
30-Mar-2026 03:39:29.512 general: debug 1: loop exclusive mode: starting
30-Mar-2026 03:39:29.512 general: debug 1: loop exclusive mode: started
30-Mar-2026 03:39:29.512 zoneload: debug 1: managed-keys-zone/_default_view_: starting load
30-Mar-2026 03:39:29.512 general: debug 1: zone_startload: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.512 zoneload: debug 1: managed-keys-zone/_default_view_: loading from master file /etc/contrail/dns/_default_view_.mkeys failed: file not found
30-Mar-2026 03:39:29.512 general: debug 1: managed-keys-zone/_default_view_: creating SOA
30-Mar-2026 03:39:29.512 zoneload: debug 1: managed-keys-zone/_default_view_: loaded; checking validity
30-Mar-2026 03:39:29.512 zoneload: info: managed-keys-zone/_default_view_: loaded serial 0
30-Mar-2026 03:39:29.512 general: debug 1: loop exclusive mode: ending
30-Mar-2026 03:39:29.512 general: info: any newly configured zones are now loaded
30-Mar-2026 03:39:29.512 general: debug 1: loop exclusive mode: ended
30-Mar-2026 03:39:29.512 general: info: scheduled loading new zones
30-Mar-2026 03:39:29.512 general: debug 1: managed-keys-zone/_default_view_: synchronizing trusted keys
30-Mar-2026 03:39:29.512 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.512 general: debug 1: create_keydata: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.512 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.512 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 30-Mar-2026 03:39:29.512
30-Mar-2026 03:39:29.512 general: debug 1: zone_journal: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.512 general: debug 1: journal file /etc/contrail/dns/_default_view_.mkeys.jnl does not exist, creating it
30-Mar-2026 03:39:29.520 general: debug 1: zone_needdump: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.520 general: debug 1: zone_maintenance: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.520 general: debug 1: zone__settimer: zone authors.bind/CH: enter
30-Mar-2026 03:39:29.520 general: debug 1: zone__settimer: zone id.server/CH: enter
30-Mar-2026 03:39:29.520 general: debug 1: zone_refreshkeys: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.520 general: notice: FIPS mode is disabled
30-Mar-2026 03:39:29.520 general: notice: running
30-Mar-2026 03:39:29.520 general: debug 1: debug: t1-cloud-fixed version
30-Mar-2026 03:39:29.520 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.520 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 30-Mar-2026 03:39:29.520
30-Mar-2026 03:39:29.520 general: debug 1: zone__settimer: zone version.bind/CH: enter
30-Mar-2026 03:39:29.520 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
30-Mar-2026 03:39:29.520 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.520 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.520 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.520 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.520 resolver: debug 1: fetch: ./DNSKEY
30-Mar-2026 03:39:29.520 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.520 resolver: debug 1: fetch: ./NS
30-Mar-2026 03:39:29.520 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
30-Mar-2026 03:39:29.520 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
30-Mar-2026 03:39:29.520 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
30-Mar-2026 03:39:29.520 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
30-Mar-2026 03:39:29.520 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
30-Mar-2026 03:39:29.520 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
30-Mar-2026 03:39:29.520 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
30-Mar-2026 03:39:29.520 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
30-Mar-2026 03:39:29.520 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
30-Mar-2026 03:39:29.520 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
30-Mar-2026 03:39:29.520 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
30-Mar-2026 03:39:29.520 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
30-Mar-2026 03:39:29.520 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
30-Mar-2026 03:39:29.524 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-Mar-2026 03:39:29.524 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.524 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 31-Mar-2026 03:39:29.524
30-Mar-2026 03:39:29.524 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-Mar-2026 03:39:29.524 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.524 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 31-Mar-2026 03:39:29.524
30-Mar-2026 03:39:29.524 general: debug 1: zone_journal: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.528 general: debug 1: zone_needdump: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.528 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.528 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.528 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:29.564 resolver: debug 1: resolver priming query complete: success
30-Mar-2026 03:39:54.544 general: debug 1: zone_maintenance: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:54.544 general: debug 1: zone_dump: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:54.544 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:54.552 general: debug 1: dump_done: managed-keys-zone/_default_view_: enter
30-Mar-2026 03:39:54.552 general: debug 1: zone_journal_compact: managed-keys-zone/_default_view_: target journal size 0
30-Mar-2026 03:43:27.101 network: info: listening on IPv6 interface vhost0, fe80::f816:3eff:fe29:f583%8#53
30-Mar-2026 03:43:27.101 network: info: no longer listening on 10.20.0.201#53
30-Mar-2026 03:43:27.109 network: info: listening on IPv4 interface vhost0, 10.20.0.201#53
30-Mar-2026 03:43:27.125 network: info: no longer listening on fe80::f816:3eff:fe29:f583%3#53
30-Mar-2026 03:43:29.425 network: info: listening on IPv6 interface pkt0, fe80::4c28:8fff:fe89:284f%9#53
30-Mar-2026 03:46:21.553 network: info: listening on IPv6 interface veth5db8fa53-2, fe80::20fd:7ff:feed:eb5e%12#53
30-Mar-2026 03:46:21.561 network: info: listening on IPv6 interface vethac061dc2-5, fe80::bc32:d9ff:fe7d:826d%13#53
30-Mar-2026 03:46:24.561 network: info: listening on IPv6 interface veth6550720a-b, fe80::9425:edff:feb8:7989%14#53
30-Mar-2026 03:46:24.581 network: info: listening on IPv6 interface vethfb1723fd-e, fe80::3484:6cff:fee8:a9b2%15#53
30-Mar-2026 03:46:24.749 network: info: no longer listening on fe80::9425:edff:feb8:7989%14#53
30-Mar-2026 03:46:24.801 network: info: no longer listening on fe80::3484:6cff:fee8:a9b2%15#53
30-Mar-2026 03:46:25.773 network: info: no longer listening on fe80::20fd:7ff:feed:eb5e%12#53
30-Mar-2026 03:46:25.817 network: info: no longer listening on fe80::bc32:d9ff:fe7d:826d%13#53
30-Mar-2026 03:46:47.089 network: info: listening on IPv6 interface vethbc5240a7-0, fe80::9443:17ff:fe07:44c5%16#53
30-Mar-2026 03:46:47.089 network: info: listening on IPv6 interface veth44f75fdc-a, fe80::2889:9eff:fed6:341f%17#53
30-Mar-2026 03:47:11.473 network: info: listening on IPv6 interface veth999adb69-9, fe80::bcac:8eff:fe61:552b%18#53
30-Mar-2026 03:47:11.473 network: info: listening on IPv6 interface veth44e74b8f-1, fe80::a47e:8aff:fef0:c95b%19#53