19-Feb-2026 01:36:54.253 general: debug 1: now using logging configuration from config file
19-Feb-2026 01:36:54.253 general: debug 1: loop exclusive mode: ending
19-Feb-2026 01:36:54.253 general: debug 1: loop exclusive mode: ended
19-Feb-2026 01:36:54.253 general: notice: command channel listening on 127.0.0.1#8094
19-Feb-2026 01:36:54.253 general: debug 1: load_configuration: success
19-Feb-2026 01:36:54.253 general: debug 1: loop exclusive mode: starting
19-Feb-2026 01:36:54.254 general: debug 1: loop exclusive mode: started
19-Feb-2026 01:36:54.254 zoneload: debug 1: managed-keys-zone: starting load
19-Feb-2026 01:36:54.254 general: debug 1: zone_startload: managed-keys-zone: enter
19-Feb-2026 01:36:54.254 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
19-Feb-2026 01:36:54.254 general: debug 1: managed-keys-zone: creating SOA
19-Feb-2026 01:36:54.254 zoneload: debug 1: managed-keys-zone: loaded; checking validity
19-Feb-2026 01:36:54.254 zoneload: info: managed-keys-zone: loaded serial 0
19-Feb-2026 01:36:54.254 general: debug 1: loop exclusive mode: ending
19-Feb-2026 01:36:54.254 general: debug 1: loop exclusive mode: ended
19-Feb-2026 01:36:54.254 zoneload: debug 1: zone authors.bind/CH: starting load
19-Feb-2026 01:36:54.254 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
19-Feb-2026 01:36:54.254 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
19-Feb-2026 01:36:54.254 zoneload: debug 1: zone version.bind/CH: starting load
19-Feb-2026 01:36:54.254 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
19-Feb-2026 01:36:54.254 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
19-Feb-2026 01:36:54.254 zoneload: debug 1: zone id.server/CH: starting load
19-Feb-2026 01:36:54.254 zoneload: debug 1: zone id.server/CH: loaded; checking validity
19-Feb-2026 01:36:54.254 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
19-Feb-2026 01:36:54.254 general: debug 1: zone__settimer: zone authors.bind/CH: enter
19-Feb-2026 01:36:54.254 general: debug 1: zone__settimer: zone version.bind/CH: enter
19-Feb-2026 01:36:54.254 general: debug 1: zone__settimer: zone id.server/CH: enter
19-Feb-2026 01:36:54.254 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
19-Feb-2026 01:36:54.255 general: debug 1: zone_maintenance: zone version.bind/CH: enter
19-Feb-2026 01:36:54.255 general: debug 1: zone_maintenance: zone id.server/CH: enter
19-Feb-2026 01:36:54.255 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:36:54.255 general: debug 1: zone__settimer: zone authors.bind/CH: enter
19-Feb-2026 01:36:54.255 general: debug 1: zone__settimer: zone version.bind/CH: enter
19-Feb-2026 01:36:54.255 general: debug 1: zone__settimer: zone id.server/CH: enter
19-Feb-2026 01:36:54.255 zoneload: debug 1: zone hostname.bind/CH: starting load
19-Feb-2026 01:36:54.255 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
19-Feb-2026 01:36:54.255 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
19-Feb-2026 01:36:54.255 general: notice: all zones loaded
19-Feb-2026 01:36:54.255 general: debug 1: managed-keys-zone: synchronizing trusted keys
19-Feb-2026 01:36:54.255 general: debug 1: create_keydata: managed-keys-zone: enter
19-Feb-2026 01:36:54.255 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
19-Feb-2026 01:36:54.255 general: debug 1: managed-keys-zone: next key refresh: 19-Feb-2026 01:36:54.255
19-Feb-2026 01:36:54.255 general: debug 1: zone_journal: managed-keys-zone: enter
19-Feb-2026 01:36:54.255 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
19-Feb-2026 01:36:54.337 general: debug 1: zone_needdump: managed-keys-zone: enter
19-Feb-2026 01:36:54.337 general: notice: FIPS mode is disabled
19-Feb-2026 01:36:54.337 general: notice: running
19-Feb-2026 01:36:54.337 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
19-Feb-2026 01:36:54.337 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:36:54.337 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:36:54.337 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:36:54.337 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
19-Feb-2026 01:36:54.337 general: debug 1: zone_maintenance: managed-keys-zone: enter
19-Feb-2026 01:36:54.337 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
19-Feb-2026 01:36:54.339 general: debug 1: zone__settimer: zone version.bind/CH: enter
19-Feb-2026 01:36:54.339 general: debug 1: zone__settimer: zone authors.bind/CH: enter
19-Feb-2026 01:36:54.339 general: debug 1: zone__settimer: zone id.server/CH: enter
19-Feb-2026 01:36:54.342 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
19-Feb-2026 01:36:54.342 general: debug 1: managed-keys-zone: next key refresh: 19-Feb-2026 01:36:54.342
19-Feb-2026 01:36:54.342 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
19-Feb-2026 01:36:54.342 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:36:54.342 resolver: debug 1: fetch: ./DNSKEY
19-Feb-2026 01:36:54.342 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:36:54.342 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
19-Feb-2026 01:36:54.342 resolver: debug 1: fetch: ./NS
19-Feb-2026 01:36:54.342 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
19-Feb-2026 01:36:54.342 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
19-Feb-2026 01:36:54.342 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
19-Feb-2026 01:36:54.342 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
19-Feb-2026 01:36:54.342 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
19-Feb-2026 01:36:54.342 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
19-Feb-2026 01:36:54.346 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
19-Feb-2026 01:36:54.348 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
19-Feb-2026 01:36:54.354 database: debug 1: delete_node(): 0x22c63b0 . (bucket 0)
19-Feb-2026 01:36:54.354 resolver: debug 1: fetch: ./DNSKEY
19-Feb-2026 01:36:54.354 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
19-Feb-2026 01:36:54.354 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
19-Feb-2026 01:36:54.390 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.
19-Feb-2026 01:36:54.390 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
19-Feb-2026 01:36:54.390 general: debug 1: managed-keys-zone: next key refresh: 20-Feb-2026 01:36:54.390
19-Feb-2026 01:36:54.390 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.
19-Feb-2026 01:36:54.390 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
19-Feb-2026 01:36:54.390 general: debug 1: managed-keys-zone: next key refresh: 20-Feb-2026 01:36:54.390
19-Feb-2026 01:36:54.390 general: debug 1: zone_journal: managed-keys-zone: enter
19-Feb-2026 01:36:54.405 general: debug 1: zone_needdump: managed-keys-zone: enter
19-Feb-2026 01:36:54.405 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:36:54.405 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:36:54.405 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:36:54.422 resolver: debug 1: resolver priming query complete: success
19-Feb-2026 01:37:19.357 general: debug 1: zone_maintenance: managed-keys-zone: enter
19-Feb-2026 01:37:19.357 general: debug 1: zone_dump: managed-keys-zone: enter
19-Feb-2026 01:37:19.358 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:37:19.361 general: debug 1: dump_done: managed-keys-zone: enter
19-Feb-2026 01:37:19.361 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
19-Feb-2026 01:37:30.631 network: info: listening on IPv6 interface tapeth0-07367b, fe80::c4d2:ff:fec8:e646%11#53
19-Feb-2026 01:37:30.632 network: info: listening on IPv6 interface tapeth0-dfbc67, fe80::306f:e4ff:fe1f:c14e%13#53
19-Feb-2026 01:39:09.092 network: info: listening on IPv4 interface kube-ipvs0, 10.101.41.8#53
19-Feb-2026 01:39:16.744 network: info: listening on IPv6 interface tapeth0-0bddd7, fe80::6c7e:60ff:febc:4ee3%15#53
19-Feb-2026 01:39:16.750 network: info: listening on IPv6 interface tapeth0-6c4952, fe80::bc5e:cdff:fecc:b3d9%17#53
19-Feb-2026 01:39:22.120 network: info: listening on IPv6 interface veth71a8ce02-8, fe80::40fa:7bff:feda:7619%18#53
19-Feb-2026 01:39:26.791 network: info: listening on IPv6 interface tapeth0-72d15a, fe80::281f:27ff:fe81:9844%20#53
19-Feb-2026 01:39:59.768 network: info: no longer listening on fe80::281f:27ff:fe81:9844%20#53
19-Feb-2026 01:40:07.248 network: info: no longer listening on fe80::40fa:7bff:feda:7619%18#53
19-Feb-2026 01:40:07.630 network: info: no longer listening on fe80::6c7e:60ff:febc:4ee3%15#53
19-Feb-2026 01:40:12.487 network: info: no longer listening on fe80::bc5e:cdff:fecc:b3d9%17#53
19-Feb-2026 01:40:32.775 network: info: listening on IPv6 interface tapeth0-fc4c39, fe80::30cf:68ff:fe1a:bb8f%22#53
19-Feb-2026 01:40:32.777 network: info: listening on IPv6 interface tapeth0-c07818, fe80::c0ad:63ff:fe41:4061%24#53
19-Feb-2026 01:40:32.779 network: info: listening on IPv6 interface tapeth0-53e7fe, fe80::477:a4ff:fece:e629%26#53
19-Feb-2026 01:40:38.023 network: info: listening on IPv6 interface tapeth0-b34fc7, fe80::40fe:39ff:febb:b062%28#53
19-Feb-2026 01:40:38.026 network: info: listening on IPv6 interface tapeth0-6f3026, fe80::18a7:6eff:fefc:e23f%30#53
19-Feb-2026 01:40:38.026 network: info: listening on IPv6 interface tapeth0-c4e5b0, fe80::9835:69ff:fea8:84ff%32#53
19-Feb-2026 01:40:42.951 network: info: listening on IPv6 interface tapeth0-7a542b, fe80::c859:51ff:fe16:5bd4%34#53
19-Feb-2026 01:40:42.952 network: info: listening on IPv6 interface tapeth0-e2cdb1, fe80::888e:24ff:fe79:fb53%36#53
19-Feb-2026 01:40:51.688 network: info: listening on IPv4 interface kube-ipvs0, 10.96.113.76#53
19-Feb-2026 01:44:01.064 network: info: no longer listening on fe80::c0ad:63ff:fe41:4061%24#53
19-Feb-2026 01:44:01.086 network: info: no longer listening on fe80::477:a4ff:fece:e629%26#53
19-Feb-2026 01:44:01.113 network: info: no longer listening on fe80::30cf:68ff:fe1a:bb8f%22#53
19-Feb-2026 01:44:01.127 network: info: no longer listening on fe80::9835:69ff:fea8:84ff%32#53
19-Feb-2026 01:44:31.311 network: info: no longer listening on fe80::18a7:6eff:fefc:e23f%30#53
19-Feb-2026 01:44:31.319 network: info: no longer listening on fe80::c859:51ff:fe16:5bd4%34#53
19-Feb-2026 01:44:31.349 network: info: no longer listening on fe80::888e:24ff:fe79:fb53%36#53
19-Feb-2026 01:44:31.360 network: info: no longer listening on fe80::40fe:39ff:febb:b062%28#53
19-Feb-2026 01:44:46.717 network: info: no longer listening on 10.96.113.76#53