28-Sep-2026 01:50:56.521 general: debug 1: now using logging configuration from config file
28-Sep-2026 01:50:56.521 general: debug 1: loop exclusive mode: ending
28-Sep-2026 01:50:56.521 general: debug 1: loop exclusive mode: ended
28-Sep-2026 01:50:56.521 general: notice: command channel listening on 127.0.0.1#8094
28-Sep-2026 01:50:56.521 general: info: VDNS cleanup pass1: 0 departing views cleared
28-Sep-2026 01:50:56.521 general: info: VDNS cleanup pass2: 2 staying views re-checked
28-Sep-2026 01:50:56.521 general: debug 1: load_configuration: success
28-Sep-2026 01:50:56.521 general: debug 1: loop exclusive mode: starting
28-Sep-2026 01:50:56.540 general: debug 1: loop exclusive mode: started
28-Sep-2026 01:50:56.541 zoneload: debug 1: managed-keys-zone: starting load
28-Sep-2026 01:50:56.541 general: debug 1: zone_startload: managed-keys-zone: enter
28-Sep-2026 01:50:56.541 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
28-Sep-2026 01:50:56.541 general: debug 1: managed-keys-zone: creating SOA
28-Sep-2026 01:50:56.541 zoneload: debug 1: managed-keys-zone: loaded; checking validity
28-Sep-2026 01:50:56.542 zoneload: info: managed-keys-zone: loaded serial 0
28-Sep-2026 01:50:56.542 general: debug 1: loop exclusive mode: ending
28-Sep-2026 01:50:56.542 zoneload: debug 1: zone id.server/CH: starting load
28-Sep-2026 01:50:56.542 zoneload: debug 1: zone id.server/CH: loaded; checking validity
28-Sep-2026 01:50:56.542 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
28-Sep-2026 01:50:56.542 general: debug 1: zone__settimer: zone id.server/CH: enter
28-Sep-2026 01:50:56.542 general: debug 1: zone_maintenance: zone id.server/CH: enter
28-Sep-2026 01:50:56.542 general: debug 1: zone__settimer: zone id.server/CH: enter
28-Sep-2026 01:50:56.542 general: debug 1: zone__settimer: managed-keys-zone: enter
28-Sep-2026 01:50:56.542 zoneload: debug 1: zone authors.bind/CH: starting load
28-Sep-2026 01:50:56.542 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
28-Sep-2026 01:50:56.542 zoneload: debug 1: zone hostname.bind/CH: starting load
28-Sep-2026 01:50:56.542 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
28-Sep-2026 01:50:56.542 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
28-Sep-2026 01:50:56.542 zoneload: debug 1: zone version.bind/CH: starting load
28-Sep-2026 01:50:56.542 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
28-Sep-2026 01:50:56.542 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
28-Sep-2026 01:50:56.542 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
28-Sep-2026 01:50:56.542 general: debug 1: zone__settimer: zone version.bind/CH: enter
28-Sep-2026 01:50:56.542 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
28-Sep-2026 01:50:56.542 general: debug 1: zone_maintenance: zone version.bind/CH: enter
28-Sep-2026 01:50:56.542 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
28-Sep-2026 01:50:56.542 general: debug 1: zone__settimer: zone version.bind/CH: enter
28-Sep-2026 01:50:56.542 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
28-Sep-2026 01:50:56.542 general: notice: all zones loaded
28-Sep-2026 01:50:56.542 general: debug 1: managed-keys-zone: synchronizing trusted keys
28-Sep-2026 01:50:56.542 general: debug 1: create_keydata: managed-keys-zone: enter
28-Sep-2026 01:50:56.542 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
28-Sep-2026 01:50:56.542 general: debug 1: managed-keys-zone: next key refresh: 28-Sep-2026 01:50:56.542
28-Sep-2026 01:50:56.542 general: debug 1: zone_journal: managed-keys-zone: enter
28-Sep-2026 01:50:56.542 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
28-Sep-2026 01:50:56.543 general: debug 1: loop exclusive mode: ended
28-Sep-2026 01:50:56.850 general: debug 1: zone_needdump: managed-keys-zone: enter
28-Sep-2026 01:50:56.850 general: notice: FIPS mode is disabled
28-Sep-2026 01:50:56.850 general: notice: running
28-Sep-2026 01:50:56.850 general: debug 1: debug: t1-cloud-fixed version
28-Sep-2026 01:50:56.850 general: debug 1: zone__settimer: zone authors.bind/CH: enter
28-Sep-2026 01:50:56.850 general: debug 1: zone__settimer: managed-keys-zone: enter
28-Sep-2026 01:50:56.850 general: debug 1: zone__settimer: managed-keys-zone: enter
28-Sep-2026 01:50:56.850 general: debug 1: zone__settimer: managed-keys-zone: enter
28-Sep-2026 01:50:56.850 general: debug 1: zone__settimer: zone authors.bind/CH: enter
28-Sep-2026 01:50:56.850 general: debug 1: zone_maintenance: managed-keys-zone: enter
28-Sep-2026 01:50:56.850 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
28-Sep-2026 01:50:56.850 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
28-Sep-2026 01:50:56.850 general: debug 1: managed-keys-zone: next key refresh: 28-Sep-2026 01:50:56.850
28-Sep-2026 01:50:56.850 general: debug 1: zone__settimer: zone version.bind/CH: enter
28-Sep-2026 01:50:56.850 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
28-Sep-2026 01:50:56.850 general: debug 1: zone__settimer: zone id.server/CH: enter
28-Sep-2026 01:50:56.850 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
28-Sep-2026 01:50:56.850 general: debug 1: zone__settimer: managed-keys-zone: enter
28-Sep-2026 01:50:56.850 resolver: debug 1: fetch: ./DNSKEY
28-Sep-2026 01:50:56.850 general: debug 1: zone__settimer: managed-keys-zone: enter
28-Sep-2026 01:50:56.850 general: debug 1: zone__settimer: zone authors.bind/CH: enter
28-Sep-2026 01:50:56.850 resolver: debug 1: fetch: ./NS
28-Sep-2026 01:50:56.851 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
28-Sep-2026 01:50:56.867 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
28-Sep-2026 01:50:56.867 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
28-Sep-2026 01:50:56.867 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
28-Sep-2026 01:50:56.867 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
28-Sep-2026 01:50:56.867 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
28-Sep-2026 01:50:56.867 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
28-Sep-2026 01:50:56.867 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
28-Sep-2026 01:50:56.867 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
28-Sep-2026 01:50:56.867 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
28-Sep-2026 01:50:56.867 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
28-Sep-2026 01:50:56.867 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
28-Sep-2026 01:50:56.867 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
28-Sep-2026 01:50:56.867 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
28-Sep-2026 01:50:56.867 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
28-Sep-2026 01:50:56.867 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
28-Sep-2026 01:50:56.867 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
28-Sep-2026 01:50:56.885 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
28-Sep-2026 01:50:56.885 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
28-Sep-2026 01:50:56.885 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
28-Sep-2026 01:50:56.885 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
28-Sep-2026 01:50:56.885 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
28-Sep-2026 01:50:56.885 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
28-Sep-2026 01:50:56.885 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
28-Sep-2026 01:50:56.885 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
28-Sep-2026 01:50:56.908 database: debug 1: delete_node(): 0x7fc480002220 . (bucket 0)
28-Sep-2026 01:50:56.908 resolver: debug 1: fetch: ./DNSKEY
28-Sep-2026 01:50:56.909 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
28-Sep-2026 01:50:56.909 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
28-Sep-2026 01:50:56.909 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
28-Sep-2026 01:50:56.909 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
28-Sep-2026 01:50:56.909 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
28-Sep-2026 01:50:56.909 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
28-Sep-2026 01:50:56.909 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
28-Sep-2026 01:50:56.909 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
28-Sep-2026 01:50:56.951 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.
28-Sep-2026 01:50:56.952 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
28-Sep-2026 01:50:56.952 general: debug 1: managed-keys-zone: next key refresh: 29-Sep-2026 01:50:56.952
28-Sep-2026 01:50:56.952 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.
28-Sep-2026 01:50:56.952 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
28-Sep-2026 01:50:56.952 general: debug 1: managed-keys-zone: next key refresh: 29-Sep-2026 01:50:56.952
28-Sep-2026 01:50:56.952 general: debug 1: zone_journal: managed-keys-zone: enter
28-Sep-2026 01:50:57.302 general: debug 1: zone_needdump: managed-keys-zone: enter
28-Sep-2026 01:50:57.304 general: debug 1: zone__settimer: managed-keys-zone: enter
28-Sep-2026 01:50:57.304 general: debug 1: zone__settimer: managed-keys-zone: enter
28-Sep-2026 01:50:57.304 general: debug 1: zone__settimer: managed-keys-zone: enter
28-Sep-2026 01:50:57.308 resolver: debug 1: resolver priming query complete: success
28-Sep-2026 01:51:22.878 general: debug 1: zone_maintenance: managed-keys-zone: enter
28-Sep-2026 01:51:22.878 general: debug 1: zone_dump: managed-keys-zone: enter
28-Sep-2026 01:51:22.882 general: debug 1: zone__settimer: managed-keys-zone: enter
28-Sep-2026 01:51:22.889 general: debug 1: dump_done: managed-keys-zone: enter
28-Sep-2026 01:51:22.889 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
28-Sep-2026 01:51:54.478 network: info: listening on IPv6 interface tapeth0-439fbe, fe80::f459:9bff:feba:2244%11#53
28-Sep-2026 01:52:04.270 network: info: listening on IPv6 interface tapeth0-933175, fe80::149d:efff:fe7d:4596%13#53
28-Sep-2026 01:53:38.789 network: info: listening on IPv4 interface kube-ipvs0, 10.111.2.43#53
28-Sep-2026 01:53:46.415 network: info: listening on IPv6 interface tapeth0-7b5d58, fe80::98e9:85ff:fe55:10f6%15#53
28-Sep-2026 01:53:46.432 network: info: listening on IPv6 interface tapeth0-d10370, fe80::78da:aff:fe8b:2d8b%17#53
28-Sep-2026 01:53:54.096 network: info: listening on IPv6 interface veth59c29629-f, fe80::e8f5:f1ff:fe98:2b4d%18#53
28-Sep-2026 01:54:02.095 network: info: listening on IPv6 interface tapeth0-102f44, fe80::68d0:a0ff:fe3b:e13d%20#53
28-Sep-2026 01:54:34.931 network: info: no longer listening on fe80::68d0:a0ff:fe3b:e13d%20#53
28-Sep-2026 01:54:41.109 network: info: no longer listening on fe80::e8f5:f1ff:fe98:2b4d%18#53
28-Sep-2026 01:54:41.851 network: info: no longer listening on fe80::98e9:85ff:fe55:10f6%15#53
28-Sep-2026 01:54:46.960 network: info: no longer listening on fe80::78da:aff:fe8b:2d8b%17#53
28-Sep-2026 01:55:07.313 network: info: listening on IPv6 interface tapeth0-1e6c36, fe80::9c5c:feff:fef1:6d5%22#53
28-Sep-2026 01:55:07.331 network: info: listening on IPv6 interface tapeth0-b6089d, fe80::88e7:16ff:fed0:de0a%24#53
28-Sep-2026 01:55:12.943 network: info: listening on IPv6 interface tapeth0-c3fb05, fe80::1ce4:ccff:fed4:4c92%26#53
28-Sep-2026 01:55:12.949 network: info: listening on IPv6 interface tapeth0-b544af, fe80::d040:22ff:fe81:f7ff%28#53
28-Sep-2026 01:55:12.950 network: info: listening on IPv6 interface tapeth0-3f5d3e, fe80::a004:44ff:fe89:1307%30#53
28-Sep-2026 01:55:18.127 network: info: listening on IPv6 interface tapeth0-e9a360, fe80::f46f:9eff:febf:a4d7%32#53
28-Sep-2026 01:55:18.133 network: info: listening on IPv6 interface tapeth0-c188a3, fe80::74d0:9bff:fe16:3408%34#53
28-Sep-2026 01:55:18.135 network: info: listening on IPv6 interface tapeth0-29b56a, fe80::68c3:26ff:fed9:7f77%36#53
28-Sep-2026 01:55:24.041 network: info: listening on IPv4 interface kube-ipvs0, 10.104.82.92#53
28-Sep-2026 01:58:36.269 network: info: no longer listening on fe80::a004:44ff:fe89:1307%30#53
28-Sep-2026 01:58:36.290 network: info: no longer listening on fe80::9c5c:feff:fef1:6d5%22#53
28-Sep-2026 01:58:36.328 network: info: no longer listening on fe80::88e7:16ff:fed0:de0a%24#53
28-Sep-2026 01:58:36.333 network: info: no longer listening on fe80::1ce4:ccff:fed4:4c92%26#53
28-Sep-2026 01:59:06.102 network: info: no longer listening on fe80::68c3:26ff:fed9:7f77%36#53
28-Sep-2026 01:59:06.159 network: info: no longer listening on fe80::d040:22ff:fe81:f7ff%28#53
28-Sep-2026 01:59:06.170 network: info: no longer listening on fe80::74d0:9bff:fe16:3408%34#53
28-Sep-2026 01:59:06.171 network: info: no longer listening on fe80::f46f:9eff:febf:a4d7%32#53
28-Sep-2026 01:59:21.743 network: info: no longer listening on 10.104.82.92#53