12-Oct-2026 01:39:31.230 general: debug 1: now using logging configuration from config file
12-Oct-2026 01:39:31.230 general: debug 1: loop exclusive mode: ending
12-Oct-2026 01:39:31.230 general: debug 1: loop exclusive mode: ended
12-Oct-2026 01:39:31.230 general: notice: command channel listening on 127.0.0.1#8094
12-Oct-2026 01:39:31.230 general: info: VDNS cleanup pass1: 0 departing views cleared
12-Oct-2026 01:39:31.230 general: info: VDNS cleanup pass2: 2 staying views re-checked
12-Oct-2026 01:39:31.230 general: debug 1: load_configuration: success
12-Oct-2026 01:39:31.230 general: debug 1: loop exclusive mode: starting
12-Oct-2026 01:39:31.231 general: debug 1: loop exclusive mode: started
12-Oct-2026 01:39:31.231 zoneload: debug 1: managed-keys-zone: starting load
12-Oct-2026 01:39:31.232 general: debug 1: zone_startload: managed-keys-zone: enter
12-Oct-2026 01:39:31.232 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
12-Oct-2026 01:39:31.232 general: debug 1: managed-keys-zone: creating SOA
12-Oct-2026 01:39:31.232 zoneload: debug 1: managed-keys-zone: loaded; checking validity
12-Oct-2026 01:39:31.232 zoneload: info: managed-keys-zone: loaded serial 0
12-Oct-2026 01:39:31.232 general: debug 1: loop exclusive mode: ending
12-Oct-2026 01:39:31.232 zoneload: debug 1: zone hostname.bind/CH: starting load
12-Oct-2026 01:39:31.232 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Oct-2026 01:39:31.232 zoneload: debug 1: zone authors.bind/CH: starting load
12-Oct-2026 01:39:31.232 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
12-Oct-2026 01:39:31.232 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
12-Oct-2026 01:39:31.232 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
12-Oct-2026 01:39:31.232 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
12-Oct-2026 01:39:31.232 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
12-Oct-2026 01:39:31.232 general: debug 1: loop exclusive mode: ended
12-Oct-2026 01:39:31.232 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
12-Oct-2026 01:39:31.232 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
12-Oct-2026 01:39:31.232 zoneload: debug 1: zone version.bind/CH: starting load
12-Oct-2026 01:39:31.232 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
12-Oct-2026 01:39:31.232 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
12-Oct-2026 01:39:31.232 zoneload: debug 1: zone id.server/CH: starting load
12-Oct-2026 01:39:31.232 zoneload: debug 1: zone id.server/CH: loaded; checking validity
12-Oct-2026 01:39:31.232 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
12-Oct-2026 01:39:31.232 general: notice: all zones loaded
12-Oct-2026 01:39:31.232 general: debug 1: managed-keys-zone: synchronizing trusted keys
12-Oct-2026 01:39:31.232 general: debug 1: create_keydata: managed-keys-zone: enter
12-Oct-2026 01:39:31.232 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
12-Oct-2026 01:39:31.232 general: debug 1: managed-keys-zone: next key refresh: 12-Oct-2026 01:39:31.232
12-Oct-2026 01:39:31.232 general: debug 1: zone_journal: managed-keys-zone: enter
12-Oct-2026 01:39:31.232 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
12-Oct-2026 01:39:31.262 general: debug 1: zone_needdump: managed-keys-zone: enter
12-Oct-2026 01:39:31.263 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
12-Oct-2026 01:39:31.263 general: notice: FIPS mode is disabled
12-Oct-2026 01:39:31.263 general: notice: running
12-Oct-2026 01:39:31.263 general: debug 1: debug: t1-cloud-fixed version
12-Oct-2026 01:39:31.263 general: debug 1: zone__settimer: zone authors.bind/CH: enter
12-Oct-2026 01:39:31.263 general: debug 1: zone__settimer: zone version.bind/CH: enter
12-Oct-2026 01:39:31.263 general: debug 1: zone__settimer: zone id.server/CH: enter
12-Oct-2026 01:39:31.263 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Oct-2026 01:39:31.263 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Oct-2026 01:39:31.263 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Oct-2026 01:39:31.263 general: debug 1: zone__settimer: zone version.bind/CH: enter
12-Oct-2026 01:39:31.263 general: debug 1: zone__settimer: zone authors.bind/CH: enter
12-Oct-2026 01:39:31.263 general: debug 1: zone__settimer: zone id.server/CH: enter
12-Oct-2026 01:39:31.263 general: debug 1: zone_maintenance: managed-keys-zone: enter
12-Oct-2026 01:39:31.263 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
12-Oct-2026 01:39:31.264 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
12-Oct-2026 01:39:31.264 general: debug 1: managed-keys-zone: next key refresh: 12-Oct-2026 01:39:31.264
12-Oct-2026 01:39:31.264 general: debug 1: zone_maintenance: zone version.bind/CH: enter
12-Oct-2026 01:39:31.264 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
12-Oct-2026 01:39:31.264 general: debug 1: zone_maintenance: zone id.server/CH: enter
12-Oct-2026 01:39:31.264 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Oct-2026 01:39:31.264 resolver: debug 1: fetch: ./DNSKEY
12-Oct-2026 01:39:31.264 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Oct-2026 01:39:31.264 general: debug 1: zone__settimer: zone version.bind/CH: enter
12-Oct-2026 01:39:31.264 general: debug 1: zone__settimer: zone authors.bind/CH: enter
12-Oct-2026 01:39:31.264 general: debug 1: zone__settimer: zone id.server/CH: enter
12-Oct-2026 01:39:31.264 resolver: debug 1: fetch: ./NS
12-Oct-2026 01:39:31.264 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
12-Oct-2026 01:39:31.264 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
12-Oct-2026 01:39:31.264 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
12-Oct-2026 01:39:31.264 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
12-Oct-2026 01:39:31.264 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
12-Oct-2026 01:39:31.264 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
12-Oct-2026 01:39:31.264 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
12-Oct-2026 01:39:31.264 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
12-Oct-2026 01:39:31.264 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
12-Oct-2026 01:39:31.264 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
12-Oct-2026 01:39:31.264 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
12-Oct-2026 01:39:31.264 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
12-Oct-2026 01:39:31.264 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
12-Oct-2026 01:39:31.264 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
12-Oct-2026 01:39:31.265 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
12-Oct-2026 01:39:31.265 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
12-Oct-2026 01:39:31.265 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
12-Oct-2026 01:39:31.265 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
12-Oct-2026 01:39:31.265 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
12-Oct-2026 01:39:31.265 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
12-Oct-2026 01:39:31.265 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
12-Oct-2026 01:39:31.265 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
12-Oct-2026 01:39:31.265 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
12-Oct-2026 01:39:31.265 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
12-Oct-2026 01:39:31.265 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
12-Oct-2026 01:39:31.266 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
12-Oct-2026 01:39:31.270 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.
12-Oct-2026 01:39:31.270 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
12-Oct-2026 01:39:31.270 general: debug 1: managed-keys-zone: next key refresh: 13-Oct-2026 01:39:31.270
12-Oct-2026 01:39:31.270 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.
12-Oct-2026 01:39:31.270 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
12-Oct-2026 01:39:31.270 general: debug 1: managed-keys-zone: next key refresh: 13-Oct-2026 01:39:31.270
12-Oct-2026 01:39:31.270 general: debug 1: zone_journal: managed-keys-zone: enter
12-Oct-2026 01:39:31.319 general: debug 1: zone_needdump: managed-keys-zone: enter
12-Oct-2026 01:39:31.319 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Oct-2026 01:39:31.319 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Oct-2026 01:39:31.319 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Oct-2026 01:39:31.321 resolver: debug 1: resolver priming query complete: success
12-Oct-2026 01:39:57.346 general: debug 1: zone_maintenance: managed-keys-zone: enter
12-Oct-2026 01:39:57.346 general: debug 1: zone_dump: managed-keys-zone: enter
12-Oct-2026 01:39:57.350 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Oct-2026 01:39:57.353 general: debug 1: dump_done: managed-keys-zone: enter
12-Oct-2026 01:39:57.353 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
12-Oct-2026 01:40:21.782 network: info: listening on IPv6 interface tapeth0-412758, fe80::fc2c:c1ff:fe8e:9f29%11#53
12-Oct-2026 01:40:26.966 network: info: listening on IPv6 interface tapeth0-896f9b, fe80::cc1:ccff:fe83:141d%13#53
12-Oct-2026 01:41:38.693 network: info: listening on IPv4 interface kube-ipvs0, 10.108.12.70#53
12-Oct-2026 01:41:46.646 network: info: listening on IPv6 interface tapeth0-90d245, fe80::b4fd:47ff:fe3a:26cb%15#53
12-Oct-2026 01:41:46.654 network: info: listening on IPv6 interface tapeth0-5f7fa8, fe80::d4e4:bff:fee9:56f4%17#53
12-Oct-2026 01:41:50.741 network: info: listening on IPv6 interface veth0b688424-e, fe80::b8eb:76ff:fe2b:ffed%18#53
12-Oct-2026 01:41:55.606 network: info: listening on IPv6 interface tapeth0-ca06e8, fe80::6c59:67ff:feeb:e37%20#53
12-Oct-2026 01:42:30.466 network: info: no longer listening on fe80::6c59:67ff:feeb:e37%20#53
12-Oct-2026 01:42:36.279 network: info: no longer listening on fe80::b8eb:76ff:fe2b:ffed%18#53
12-Oct-2026 01:42:36.922 network: info: no longer listening on fe80::b4fd:47ff:fe3a:26cb%15#53
12-Oct-2026 01:42:41.739 network: info: no longer listening on fe80::d4e4:bff:fee9:56f4%17#53
12-Oct-2026 01:43:01.525 network: info: listening on IPv6 interface tapeth0-7f8258, fe80::9d:e8ff:fe23:ab28%22#53
12-Oct-2026 01:43:01.527 network: info: listening on IPv6 interface tapeth0-a3a15b, fe80::a0aa:28ff:fe53:d37b%24#53
12-Oct-2026 01:43:01.528 network: info: listening on IPv6 interface tapeth0-8f29bb, fe80::b08d:3fff:fe5c:594d%26#53
12-Oct-2026 01:43:07.349 network: info: listening on IPv6 interface tapeth0-4964de, fe80::9cc6:6cff:fe94:588e%28#53
12-Oct-2026 01:43:07.349 network: info: listening on IPv6 interface tapeth0-78d7fc, fe80::80bb:e5ff:fe0c:9879%30#53
12-Oct-2026 01:43:07.350 network: info: listening on IPv6 interface tapeth0-510760, fe80::fc98:1cff:fe78:f4d1%32#53
12-Oct-2026 01:43:12.533 network: info: listening on IPv6 interface tapeth0-40ce1b, fe80::2c7c:99ff:fe2e:a62b%34#53
12-Oct-2026 01:43:12.534 network: info: listening on IPv6 interface tapeth0-b36d3a, fe80::847b:27ff:fee9:e2f1%36#53
12-Oct-2026 01:43:20.965 network: info: listening on IPv4 interface kube-ipvs0, 10.102.43.38#53
12-Oct-2026 01:46:29.955 network: info: no longer listening on fe80::80bb:e5ff:fe0c:9879%30#53
12-Oct-2026 01:46:29.987 network: info: no longer listening on fe80::a0aa:28ff:fe53:d37b%24#53
12-Oct-2026 01:46:29.990 network: info: no longer listening on fe80::b08d:3fff:fe5c:594d%26#53
12-Oct-2026 01:46:30.002 network: info: no longer listening on fe80::9d:e8ff:fe23:ab28%22#53
12-Oct-2026 01:46:59.834 network: info: no longer listening on fe80::9cc6:6cff:fe94:588e%28#53
12-Oct-2026 01:46:59.872 network: info: no longer listening on fe80::fc98:1cff:fe78:f4d1%32#53
12-Oct-2026 01:46:59.873 network: info: no longer listening on fe80::2c7c:99ff:fe2e:a62b%34#53
12-Oct-2026 01:46:59.873 network: info: no longer listening on fe80::847b:27ff:fee9:e2f1%36#53
12-Oct-2026 01:47:15.763 network: info: no longer listening on 10.102.43.38#53