23-Feb-2026 01:29:14.318 general: debug 1: now using logging configuration from config file
23-Feb-2026 01:29:14.318 general: debug 1: loop exclusive mode: ending
23-Feb-2026 01:29:14.318 general: debug 1: loop exclusive mode: ended
23-Feb-2026 01:29:14.318 general: notice: command channel listening on 127.0.0.1#8094
23-Feb-2026 01:29:14.319 general: debug 1: load_configuration: success
23-Feb-2026 01:29:14.319 general: debug 1: loop exclusive mode: starting
23-Feb-2026 01:29:14.602 general: debug 1: loop exclusive mode: started
23-Feb-2026 01:29:14.602 zoneload: debug 1: managed-keys-zone: starting load
23-Feb-2026 01:29:14.602 general: debug 1: zone_startload: managed-keys-zone: enter
23-Feb-2026 01:29:14.602 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
23-Feb-2026 01:29:14.602 general: debug 1: managed-keys-zone: creating SOA
23-Feb-2026 01:29:14.602 zoneload: debug 1: managed-keys-zone: loaded; checking validity
23-Feb-2026 01:29:14.602 zoneload: info: managed-keys-zone: loaded serial 0
23-Feb-2026 01:29:14.602 general: debug 1: loop exclusive mode: ending
23-Feb-2026 01:29:14.602 general: debug 1: zone__settimer: managed-keys-zone: enter
23-Feb-2026 01:29:14.602 zoneload: debug 1: zone id.server/CH: starting load
23-Feb-2026 01:29:14.602 zoneload: debug 1: zone id.server/CH: loaded; checking validity
23-Feb-2026 01:29:14.602 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
23-Feb-2026 01:29:14.602 general: debug 1: zone__settimer: zone id.server/CH: enter
23-Feb-2026 01:29:14.602 general: debug 1: zone_maintenance: zone id.server/CH: enter
23-Feb-2026 01:29:14.602 general: debug 1: zone__settimer: zone id.server/CH: enter
23-Feb-2026 01:29:14.602 zoneload: debug 1: zone hostname.bind/CH: starting load
23-Feb-2026 01:29:14.602 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
23-Feb-2026 01:29:14.602 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
23-Feb-2026 01:29:14.602 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
23-Feb-2026 01:29:14.602 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
23-Feb-2026 01:29:14.602 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
23-Feb-2026 01:29:14.603 zoneload: debug 1: zone authors.bind/CH: starting load
23-Feb-2026 01:29:14.603 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
23-Feb-2026 01:29:14.603 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
23-Feb-2026 01:29:14.603 general: debug 1: zone__settimer: zone authors.bind/CH: enter
23-Feb-2026 01:29:14.603 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
23-Feb-2026 01:29:14.603 general: debug 1: zone__settimer: zone authors.bind/CH: enter
23-Feb-2026 01:29:14.603 general: debug 1: loop exclusive mode: ended
23-Feb-2026 01:29:14.603 zoneload: debug 1: zone version.bind/CH: starting load
23-Feb-2026 01:29:14.603 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
23-Feb-2026 01:29:14.603 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
23-Feb-2026 01:29:14.603 general: notice: all zones loaded
23-Feb-2026 01:29:14.603 general: debug 1: managed-keys-zone: synchronizing trusted keys
23-Feb-2026 01:29:14.603 general: debug 1: create_keydata: managed-keys-zone: enter
23-Feb-2026 01:29:14.603 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
23-Feb-2026 01:29:14.603 general: debug 1: managed-keys-zone: next key refresh: 23-Feb-2026 01:29:14.603
23-Feb-2026 01:29:14.692 general: debug 1: zone_journal: managed-keys-zone: enter
23-Feb-2026 01:29:14.692 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
23-Feb-2026 01:29:14.692 general: debug 1: zone__settimer: managed-keys-zone: enter
23-Feb-2026 01:29:14.713 general: debug 1: zone_needdump: managed-keys-zone: enter
23-Feb-2026 01:29:14.713 general: debug 1: zone_maintenance: managed-keys-zone: enter
23-Feb-2026 01:29:14.714 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
23-Feb-2026 01:29:14.714 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
23-Feb-2026 01:29:14.714 general: debug 1: managed-keys-zone: next key refresh: 23-Feb-2026 01:29:14.714
23-Feb-2026 01:29:14.714 general: debug 1: zone__settimer: managed-keys-zone: enter
23-Feb-2026 01:29:14.714 general: debug 1: zone__settimer: managed-keys-zone: enter
23-Feb-2026 01:29:14.714 resolver: debug 1: fetch: ./DNSKEY
23-Feb-2026 01:29:14.714 general: debug 1: zone__settimer: managed-keys-zone: enter
23-Feb-2026 01:29:14.714 resolver: debug 1: fetch: ./NS
23-Feb-2026 01:29:14.714 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
23-Feb-2026 01:29:14.726 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
23-Feb-2026 01:29:14.727 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
23-Feb-2026 01:29:14.731 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
23-Feb-2026 01:29:14.858 general: debug 1: zone__settimer: managed-keys-zone: enter
23-Feb-2026 01:29:14.858 database: debug 1: delete_node(): 0x7fe3c80012c0 . (bucket 1)
23-Feb-2026 01:29:14.858 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.
23-Feb-2026 01:29:14.859 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
23-Feb-2026 01:29:14.859 general: debug 1: managed-keys-zone: next key refresh: 24-Feb-2026 01:29:14.859
23-Feb-2026 01:29:14.859 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.
23-Feb-2026 01:29:14.859 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
23-Feb-2026 01:29:14.859 general: debug 1: managed-keys-zone: next key refresh: 24-Feb-2026 01:29:14.859
23-Feb-2026 01:29:14.859 general: debug 1: zone_journal: managed-keys-zone: enter
23-Feb-2026 01:29:14.882 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
23-Feb-2026 01:29:14.949 general: notice: FIPS mode is disabled
23-Feb-2026 01:29:14.949 general: notice: running
23-Feb-2026 01:29:14.949 general: debug 1: zone__settimer: zone version.bind/CH: enter
23-Feb-2026 01:29:14.949 general: debug 1: zone__settimer: zone version.bind/CH: enter
23-Feb-2026 01:29:14.949 general: debug 1: zone_maintenance: zone version.bind/CH: enter
23-Feb-2026 01:29:14.949 general: debug 1: zone__settimer: zone version.bind/CH: enter
23-Feb-2026 01:29:14.949 general: debug 1: zone__settimer: zone authors.bind/CH: enter
23-Feb-2026 01:29:14.977 general: debug 1: zone_needdump: managed-keys-zone: enter
23-Feb-2026 01:29:14.977 general: debug 1: zone__settimer: managed-keys-zone: enter
23-Feb-2026 01:29:14.977 general: debug 1: zone__settimer: managed-keys-zone: enter
23-Feb-2026 01:29:14.977 general: debug 1: zone__settimer: zone id.server/CH: enter
23-Feb-2026 01:29:14.977 general: debug 1: zone__settimer: managed-keys-zone: enter
23-Feb-2026 01:29:15.004 resolver: debug 1: resolver priming query complete: success
23-Feb-2026 01:29:15.141 general: info: received control channel command 'reconfig'
23-Feb-2026 01:29:15.141 general: debug 1: loop exclusive mode: starting
23-Feb-2026 01:29:15.160 general: debug 1: loop exclusive mode: started
23-Feb-2026 01:29:15.160 general: info: loading configuration from '/etc/contrail/dns/contrail-named.conf'
23-Feb-2026 01:29:15.160 general: info: the working directory is now '/etc/contrail/dns'
23-Feb-2026 01:29:15.160 general: info: using default UDP/IPv4 port range: [32768, 60999]
23-Feb-2026 01:29:15.161 general: info: using default UDP/IPv6 port range: [32768, 60999]
23-Feb-2026 01:29:15.162 general: info: Disabling periodic interface re-scans timer
23-Feb-2026 01:29:15.162 config: debug 1: none:215: dnssec-policy: load policy 'default'
23-Feb-2026 01:29:15.162 config: debug 1: none:238: dnssec-policy: load policy 'insecure'
23-Feb-2026 01:29:15.163 security: info: using built-in root key for view _default_view_
23-Feb-2026 01:29:15.163 general: info: set up managed keys zone for view _default_view_, file '/etc/contrail/dns/_default_view_.mkeys'
23-Feb-2026 01:29:15.163 general: debug 1: now using logging configuration from config file
23-Feb-2026 01:29:15.164 general: debug 1: loop exclusive mode: ending
23-Feb-2026 01:29:15.164 general: debug 1: loop exclusive mode: ended
23-Feb-2026 01:29:15.191 general: debug 1: managed-keys-zone: final reference detached
23-Feb-2026 01:29:15.192 database: debug 1: calling free_qpdb(.)
23-Feb-2026 01:29:15.192 database: debug 1: done free_qpdb(.)
23-Feb-2026 01:29:15.192 database: debug 1: calling free_qpdb(.)
23-Feb-2026 01:29:15.192 database: debug 1: called free_qpdb(.)
23-Feb-2026 01:29:15.200 general: debug 1: load_configuration: success
23-Feb-2026 01:29:15.200 general: info: reloading configuration succeeded
23-Feb-2026 01:29:15.200 general: debug 1: loop exclusive mode: starting
23-Feb-2026 01:29:15.357 general: debug 1: loop exclusive mode: started
23-Feb-2026 01:29:15.357 zoneload: debug 1: managed-keys-zone/_default_view_: starting load
23-Feb-2026 01:29:15.357 general: debug 1: zone_startload: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.357 zoneload: debug 1: managed-keys-zone/_default_view_: loading from master file /etc/contrail/dns/_default_view_.mkeys failed: file not found
23-Feb-2026 01:29:15.357 general: debug 1: managed-keys-zone/_default_view_: creating SOA
23-Feb-2026 01:29:15.360 zoneload: debug 1: managed-keys-zone/_default_view_: loaded; checking validity
23-Feb-2026 01:29:15.360 zoneload: info: managed-keys-zone/_default_view_: loaded serial 0
23-Feb-2026 01:29:15.360 general: debug 1: loop exclusive mode: ending
23-Feb-2026 01:29:15.360 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.360 general: debug 1: loop exclusive mode: ended
23-Feb-2026 01:29:15.360 general: info: scheduled loading new zones
23-Feb-2026 01:29:15.360 general: info: any newly configured zones are now loaded
23-Feb-2026 01:29:15.360 general: debug 1: managed-keys-zone/_default_view_: synchronizing trusted keys
23-Feb-2026 01:29:15.360 general: debug 1: create_keydata: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.360 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.360 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 23-Feb-2026 01:29:15.360
23-Feb-2026 01:29:15.376 general: debug 1: zone_journal: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.376 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.376 general: debug 1: journal file /etc/contrail/dns/_default_view_.mkeys.jnl does not exist, creating it
23-Feb-2026 01:29:15.383 general: debug 1: zone_needdump: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.383 general: debug 1: zone_maintenance: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.383 general: debug 1: zone_refreshkeys: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.383 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.383 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 23-Feb-2026 01:29:15.383
23-Feb-2026 01:29:15.383 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.383 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.383 resolver: debug 1: fetch: ./DNSKEY
23-Feb-2026 01:29:15.383 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.383 resolver: debug 1: fetch: ./NS
23-Feb-2026 01:29:15.385 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
23-Feb-2026 01:29:15.385 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
23-Feb-2026 01:29:15.385 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
23-Feb-2026 01:29:15.385 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
23-Feb-2026 01:29:15.385 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
23-Feb-2026 01:29:15.385 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
23-Feb-2026 01:29:15.385 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
23-Feb-2026 01:29:15.385 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
23-Feb-2026 01:29:15.385 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
23-Feb-2026 01:29:15.385 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
23-Feb-2026 01:29:15.385 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
23-Feb-2026 01:29:15.385 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
23-Feb-2026 01:29:15.385 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
23-Feb-2026 01:29:15.391 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.
23-Feb-2026 01:29:15.391 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.391 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 24-Feb-2026 01:29:15.391
23-Feb-2026 01:29:15.391 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.
23-Feb-2026 01:29:15.391 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.391 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 24-Feb-2026 01:29:15.391
23-Feb-2026 01:29:15.391 general: debug 1: zone_journal: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.408 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
23-Feb-2026 01:29:15.410 general: debug 1: zone_needdump: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.410 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.410 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.410 general: debug 1: zone__settimer: zone authors.bind/CH: enter
23-Feb-2026 01:29:15.410 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.414 general: notice: FIPS mode is disabled
23-Feb-2026 01:29:15.414 general: notice: running
23-Feb-2026 01:29:15.414 general: debug 1: zone__settimer: zone version.bind/CH: enter
23-Feb-2026 01:29:15.414 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:15.414 general: debug 1: zone__settimer: zone id.server/CH: enter
23-Feb-2026 01:29:15.441 resolver: debug 1: resolver priming query complete: success
23-Feb-2026 01:29:39.534 network: info: listening on IPv6 interface tapeth0-7db42c, fe80::d8dc:98ff:fe9e:84fa%11#53
23-Feb-2026 01:29:41.412 general: debug 1: zone_maintenance: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:41.412 general: debug 1: zone_dump: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:41.414 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:41.425 general: debug 1: dump_done: managed-keys-zone/_default_view_: enter
23-Feb-2026 01:29:41.425 general: debug 1: zone_journal_compact: managed-keys-zone/_default_view_: target journal size 0
23-Feb-2026 01:29:45.292 network: info: listening on IPv6 interface tapeth0-039e03, fe80::6c6d:41ff:fe57:91f0%13#53
23-Feb-2026 01:31:53.220 network: info: listening on IPv4 interface kube-ipvs0, 10.101.132.6#53
23-Feb-2026 01:32:02.255 network: info: listening on IPv6 interface tapeth0-f15b23, fe80::605c:58ff:fe09:bbb5%15#53
23-Feb-2026 01:32:02.274 network: info: listening on IPv6 interface tapeth0-c202aa, fe80::84ad:e8ff:feac:d8ac%17#53
23-Feb-2026 01:32:06.288 network: info: listening on IPv6 interface veth46237263-0, fe80::889a:6dff:feb8:69bb%18#53
23-Feb-2026 01:32:11.662 network: info: listening on IPv6 interface tapeth0-55c438, fe80::b0ca:e9ff:fe48:760b%20#53
23-Feb-2026 01:32:49.017 network: info: no longer listening on fe80::b0ca:e9ff:fe48:760b%20#53
23-Feb-2026 01:32:56.011 network: info: no longer listening on fe80::889a:6dff:feb8:69bb%18#53
23-Feb-2026 01:32:56.957 network: info: no longer listening on fe80::605c:58ff:fe09:bbb5%15#53
23-Feb-2026 01:33:01.913 network: info: no longer listening on fe80::84ad:e8ff:feac:d8ac%17#53
23-Feb-2026 01:33:21.676 network: info: listening on IPv6 interface tapeth0-f9bed5, fe80::c63:edff:fe20:d689%22#53
23-Feb-2026 01:33:21.680 network: info: listening on IPv6 interface tapeth0-c617c6, fe80::ccf7:bfff:fece:1eae%24#53
23-Feb-2026 01:33:21.680 network: info: listening on IPv6 interface tapeth0-6f79c6, fe80::c4de:b7ff:fe00:9c6a%26#53
23-Feb-2026 01:33:26.347 network: info: listening on IPv6 interface tapeth0-95bbaf, fe80::cc6e:e1ff:fe5d:da48%28#53
23-Feb-2026 01:33:26.348 network: info: listening on IPv6 interface tapeth0-7cbdb7, fe80::bc0a:7eff:feea:415b%30#53
23-Feb-2026 01:33:26.349 network: info: listening on IPv6 interface tapeth0-15f74b, fe80::30e8:bdff:feda:8eb4%32#53
23-Feb-2026 01:33:31.787 network: info: listening on IPv6 interface tapeth0-162fc9, fe80::40a6:1bff:fe69:aecb%34#53
23-Feb-2026 01:33:31.788 network: info: listening on IPv6 interface tapeth0-46c771, fe80::1832:3ff:fed1:f897%36#53
23-Feb-2026 01:33:40.997 network: info: listening on IPv4 interface kube-ipvs0, 10.100.79.239#53
23-Feb-2026 01:36:51.150 network: info: no longer listening on fe80::c63:edff:fe20:d689%22#53
23-Feb-2026 01:36:51.174 network: info: no longer listening on fe80::c4de:b7ff:fe00:9c6a%26#53
23-Feb-2026 01:36:51.201 network: info: no longer listening on fe80::ccf7:bfff:fece:1eae%24#53
23-Feb-2026 01:36:51.204 network: info: no longer listening on fe80::cc6e:e1ff:fe5d:da48%28#53
23-Feb-2026 01:37:21.182 network: info: no longer listening on fe80::1832:3ff:fed1:f897%36#53
23-Feb-2026 01:37:21.204 network: info: no longer listening on fe80::30e8:bdff:feda:8eb4%32#53
23-Feb-2026 01:37:21.228 network: info: no longer listening on fe80::bc0a:7eff:feea:415b%30#53
23-Feb-2026 01:37:21.239 network: info: no longer listening on fe80::40a6:1bff:fe69:aecb%34#53
23-Feb-2026 01:37:36.906 network: info: no longer listening on 10.100.79.239#53