28-May-2026 01:38:25.083 general: debug 1: now using logging configuration from config file
28-May-2026 01:38:25.083 general: debug 1: loop exclusive mode: ending
28-May-2026 01:38:25.084 general: debug 1: loop exclusive mode: ended
28-May-2026 01:38:25.084 general: notice: command channel listening on 127.0.0.1#8094
28-May-2026 01:38:25.084 general: info: VDNS cleanup pass1: 0 departing views cleared
28-May-2026 01:38:25.084 general: info: VDNS cleanup pass2: 2 staying views re-checked
28-May-2026 01:38:25.084 general: debug 1: load_configuration: success
28-May-2026 01:38:25.084 general: debug 1: loop exclusive mode: starting
28-May-2026 01:38:25.090 general: debug 1: loop exclusive mode: started
28-May-2026 01:38:25.090 zoneload: debug 1: managed-keys-zone: starting load
28-May-2026 01:38:25.090 general: debug 1: zone_startload: managed-keys-zone: enter
28-May-2026 01:38:25.090 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
28-May-2026 01:38:25.090 general: debug 1: managed-keys-zone: creating SOA
28-May-2026 01:38:25.090 zoneload: debug 1: managed-keys-zone: loaded; checking validity
28-May-2026 01:38:25.090 zoneload: info: managed-keys-zone: loaded serial 0
28-May-2026 01:38:25.090 general: debug 1: loop exclusive mode: ending
28-May-2026 01:38:25.090 general: debug 1: loop exclusive mode: ended
28-May-2026 01:38:25.090 zoneload: debug 1: zone authors.bind/CH: starting load
28-May-2026 01:38:25.090 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
28-May-2026 01:38:25.090 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
28-May-2026 01:38:25.090 zoneload: debug 1: zone hostname.bind/CH: starting load
28-May-2026 01:38:25.090 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
28-May-2026 01:38:25.090 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
28-May-2026 01:38:25.090 zoneload: debug 1: zone id.server/CH: starting load
28-May-2026 01:38:25.090 zoneload: debug 1: zone id.server/CH: loaded; checking validity
28-May-2026 01:38:25.090 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
28-May-2026 01:38:25.090 general: debug 1: zone__settimer: zone authors.bind/CH: enter
28-May-2026 01:38:25.090 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
28-May-2026 01:38:25.090 general: debug 1: zone__settimer: zone id.server/CH: enter
28-May-2026 01:38:25.090 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
28-May-2026 01:38:25.090 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
28-May-2026 01:38:25.091 general: debug 1: zone_maintenance: zone id.server/CH: enter
28-May-2026 01:38:25.091 general: debug 1: zone__settimer: zone authors.bind/CH: enter
28-May-2026 01:38:25.091 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
28-May-2026 01:38:25.091 general: debug 1: zone__settimer: zone id.server/CH: enter
28-May-2026 01:38:25.091 general: debug 1: zone__settimer: managed-keys-zone: enter
28-May-2026 01:38:25.091 zoneload: debug 1: zone version.bind/CH: starting load
28-May-2026 01:38:25.091 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
28-May-2026 01:38:25.091 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
28-May-2026 01:38:25.091 general: notice: all zones loaded
28-May-2026 01:38:25.091 general: debug 1: managed-keys-zone: synchronizing trusted keys
28-May-2026 01:38:25.091 general: debug 1: create_keydata: managed-keys-zone: enter
28-May-2026 01:38:25.091 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
28-May-2026 01:38:25.091 general: debug 1: managed-keys-zone: next key refresh: 28-May-2026 01:38:25.091
28-May-2026 01:38:25.091 general: debug 1: zone_journal: managed-keys-zone: enter
28-May-2026 01:38:25.091 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
28-May-2026 01:38:25.328 general: debug 1: zone_needdump: managed-keys-zone: enter
28-May-2026 01:38:25.332 general: notice: FIPS mode is disabled
28-May-2026 01:38:25.332 general: notice: running
28-May-2026 01:38:25.332 general: debug 1: debug: t1-cloud-fixed version
28-May-2026 01:38:25.332 general: debug 1: zone__settimer: zone version.bind/CH: enter
28-May-2026 01:38:25.332 general: debug 1: zone__settimer: managed-keys-zone: enter
28-May-2026 01:38:25.332 general: debug 1: zone__settimer: managed-keys-zone: enter
28-May-2026 01:38:25.332 general: debug 1: zone__settimer: managed-keys-zone: enter
28-May-2026 01:38:25.332 general: debug 1: zone__settimer: zone version.bind/CH: enter
28-May-2026 01:38:25.332 general: debug 1: zone_maintenance: managed-keys-zone: enter
28-May-2026 01:38:25.332 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
28-May-2026 01:38:25.332 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
28-May-2026 01:38:25.332 general: debug 1: managed-keys-zone: next key refresh: 28-May-2026 01:38:25.332
28-May-2026 01:38:25.332 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
28-May-2026 01:38:25.332 general: debug 1: zone__settimer: zone authors.bind/CH: enter
28-May-2026 01:38:25.332 general: debug 1: zone__settimer: zone id.server/CH: enter
28-May-2026 01:38:25.332 general: debug 1: zone_maintenance: zone version.bind/CH: enter
28-May-2026 01:38:25.332 general: debug 1: zone__settimer: managed-keys-zone: enter
28-May-2026 01:38:25.332 resolver: debug 1: fetch: ./DNSKEY
28-May-2026 01:38:25.332 general: debug 1: zone__settimer: managed-keys-zone: enter
28-May-2026 01:38:25.332 general: debug 1: zone__settimer: zone version.bind/CH: enter
28-May-2026 01:38:25.332 resolver: debug 1: fetch: ./NS
28-May-2026 01:38:25.332 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
28-May-2026 01:38:25.333 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
28-May-2026 01:38:25.337 database: debug 1: delete_node(): 0x675cb0 . (bucket 0)
28-May-2026 01:38:25.337 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-May-2026 01:38:25.337 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
28-May-2026 01:38:25.337 general: debug 1: managed-keys-zone: next key refresh: 29-May-2026 01:38:25.337
28-May-2026 01:38:25.337 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-May-2026 01:38:25.337 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
28-May-2026 01:38:25.337 general: debug 1: managed-keys-zone: next key refresh: 29-May-2026 01:38:25.337
28-May-2026 01:38:25.337 general: debug 1: zone_journal: managed-keys-zone: enter
28-May-2026 01:38:25.354 general: debug 1: zone_needdump: managed-keys-zone: enter
28-May-2026 01:38:25.354 general: debug 1: zone__settimer: managed-keys-zone: enter
28-May-2026 01:38:25.354 general: debug 1: zone__settimer: managed-keys-zone: enter
28-May-2026 01:38:25.354 general: debug 1: zone__settimer: managed-keys-zone: enter
28-May-2026 01:38:25.386 resolver: debug 1: resolver priming query complete: success
28-May-2026 01:38:49.353 general: debug 1: zone_maintenance: managed-keys-zone: enter
28-May-2026 01:38:49.353 general: debug 1: zone_dump: managed-keys-zone: enter
28-May-2026 01:38:49.354 general: debug 1: zone__settimer: managed-keys-zone: enter
28-May-2026 01:38:49.361 general: debug 1: dump_done: managed-keys-zone: enter
28-May-2026 01:38:49.361 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
28-May-2026 01:39:15.077 network: info: listening on IPv6 interface tapeth0-528595, fe80::904d:39ff:fe7d:7f66%11#53
28-May-2026 01:39:15.078 network: info: listening on IPv6 interface tapeth0-7329bf, fe80::86f:9aff:fe19:5d30%13#53
28-May-2026 01:40:33.966 network: info: listening on IPv4 interface kube-ipvs0, 10.103.70.31#53
28-May-2026 01:40:41.735 network: info: listening on IPv6 interface tapeth0-b703ab, fe80::10c1:a3ff:fe5f:c555%15#53
28-May-2026 01:40:41.736 network: info: listening on IPv6 interface tapeth0-fc2c20, fe80::3854:5cff:fee3:a12f%17#53
28-May-2026 01:40:43.717 network: info: listening on IPv6 interface vethc4425b6b-1, fe80::9841:b3ff:fe37:98c9%18#53
28-May-2026 01:40:49.733 network: info: listening on IPv6 interface tapeth0-b5b28d, fe80::8462:c3ff:fee5:8452%20#53
28-May-2026 01:41:29.205 network: info: no longer listening on fe80::8462:c3ff:fee5:8452%20#53
28-May-2026 01:41:34.966 network: info: no longer listening on fe80::9841:b3ff:fe37:98c9%18#53
28-May-2026 01:41:35.894 network: info: no longer listening on fe80::3854:5cff:fee3:a12f%17#53
28-May-2026 01:41:40.664 network: info: no longer listening on fe80::10c1:a3ff:fe5f:c555%15#53
28-May-2026 01:42:00.708 network: info: listening on IPv6 interface tapeth0-53ef17, fe80::58b8:98ff:fe03:5b5e%22#53
28-May-2026 01:42:00.710 network: info: listening on IPv6 interface tapeth0-289314, fe80::f0dd:a6ff:fe64:18ad%24#53
28-May-2026 01:42:00.710 network: info: listening on IPv6 interface tapeth0-60fc27, fe80::bc95:53ff:fed7:56bb%26#53
28-May-2026 01:42:05.252 network: info: listening on IPv6 interface tapeth0-7b4dc2, fe80::5837:7bff:fef4:1797%28#53
28-May-2026 01:42:05.255 network: info: listening on IPv6 interface tapeth0-877787, fe80::a437:2cff:feda:2499%30#53
28-May-2026 01:42:05.255 network: info: listening on IPv6 interface tapeth0-0c518b, fe80::aca1:9dff:fe09:c7be%32#53
28-May-2026 01:42:05.255 network: info: listening on IPv6 interface tapeth0-80543f, fe80::3c07:a3ff:fe9d:23a9%34#53
28-May-2026 01:42:10.181 network: info: listening on IPv6 interface tapeth0-cedd08, fe80::842c:b1ff:fe7b:cf40%36#53
28-May-2026 01:42:19.633 network: info: listening on IPv4 interface kube-ipvs0, 10.111.119.156#53
28-May-2026 01:45:28.746 network: info: no longer listening on fe80::58b8:98ff:fe03:5b5e%22#53
28-May-2026 01:45:28.770 network: info: no longer listening on fe80::a437:2cff:feda:2499%30#53
28-May-2026 01:45:28.790 network: info: no longer listening on fe80::f0dd:a6ff:fe64:18ad%24#53
28-May-2026 01:45:28.792 network: info: no longer listening on fe80::bc95:53ff:fed7:56bb%26#53
28-May-2026 01:45:58.694 network: info: no longer listening on fe80::842c:b1ff:fe7b:cf40%36#53
28-May-2026 01:45:58.711 network: info: no longer listening on fe80::3c07:a3ff:fe9d:23a9%34#53
28-May-2026 01:45:58.741 network: info: no longer listening on fe80::5837:7bff:fef4:1797%28#53
28-May-2026 01:45:58.749 network: info: no longer listening on fe80::aca1:9dff:fe09:c7be%32#53
28-May-2026 01:46:14.078 network: info: no longer listening on 10.111.119.156#53