05-Jan-2026 01:37:09.320 general: debug 1: now using logging configuration from config file
05-Jan-2026 01:37:09.320 general: debug 1: loop exclusive mode: ending
05-Jan-2026 01:37:09.320 general: debug 1: loop exclusive mode: ended
05-Jan-2026 01:37:09.321 general: notice: command channel listening on 127.0.0.1#8094
05-Jan-2026 01:37:09.321 general: debug 1: load_configuration: success
05-Jan-2026 01:37:09.321 general: debug 1: loop exclusive mode: starting
05-Jan-2026 01:37:09.385 general: debug 1: loop exclusive mode: started
05-Jan-2026 01:37:09.385 zoneload: debug 1: managed-keys-zone: starting load
05-Jan-2026 01:37:09.385 general: debug 1: zone_startload: managed-keys-zone: enter
05-Jan-2026 01:37:09.385 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
05-Jan-2026 01:37:09.385 general: debug 1: managed-keys-zone: creating SOA
05-Jan-2026 01:37:09.385 zoneload: debug 1: managed-keys-zone: loaded; checking validity
05-Jan-2026 01:37:09.385 zoneload: info: managed-keys-zone: loaded serial 0
05-Jan-2026 01:37:09.385 general: debug 1: loop exclusive mode: ending
05-Jan-2026 01:37:09.385 zoneload: debug 1: zone id.server/CH: starting load
05-Jan-2026 01:37:09.385 zoneload: debug 1: zone id.server/CH: loaded; checking validity
05-Jan-2026 01:37:09.385 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
05-Jan-2026 01:37:09.385 general: debug 1: zone__settimer: zone id.server/CH: enter
05-Jan-2026 01:37:09.385 general: debug 1: zone_maintenance: zone id.server/CH: enter
05-Jan-2026 01:37:09.385 general: debug 1: zone__settimer: zone id.server/CH: enter
05-Jan-2026 01:37:09.385 zoneload: debug 1: zone authors.bind/CH: starting load
05-Jan-2026 01:37:09.385 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
05-Jan-2026 01:37:09.385 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
05-Jan-2026 01:37:09.385 general: debug 1: zone__settimer: zone authors.bind/CH: enter
05-Jan-2026 01:37:09.385 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
05-Jan-2026 01:37:09.385 general: debug 1: zone__settimer: zone authors.bind/CH: enter
05-Jan-2026 01:37:09.385 zoneload: debug 1: zone hostname.bind/CH: starting load
05-Jan-2026 01:37:09.386 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
05-Jan-2026 01:37:09.386 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
05-Jan-2026 01:37:09.386 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
05-Jan-2026 01:37:09.386 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
05-Jan-2026 01:37:09.386 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
05-Jan-2026 01:37:09.386 general: debug 1: loop exclusive mode: ended
05-Jan-2026 01:37:09.386 general: debug 1: zone__settimer: managed-keys-zone: enter
05-Jan-2026 01:37:09.386 zoneload: debug 1: zone version.bind/CH: starting load
05-Jan-2026 01:37:09.386 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
05-Jan-2026 01:37:09.386 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
05-Jan-2026 01:37:09.386 general: notice: all zones loaded
05-Jan-2026 01:37:09.386 general: debug 1: managed-keys-zone: synchronizing trusted keys
05-Jan-2026 01:37:09.386 general: debug 1: create_keydata: managed-keys-zone: enter
05-Jan-2026 01:37:09.386 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
05-Jan-2026 01:37:09.386 general: debug 1: managed-keys-zone: next key refresh: 05-Jan-2026 01:37:09.386
05-Jan-2026 01:37:09.386 general: debug 1: zone_journal: managed-keys-zone: enter
05-Jan-2026 01:37:09.386 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
05-Jan-2026 01:37:09.404 general: debug 1: zone_needdump: managed-keys-zone: enter
05-Jan-2026 01:37:09.412 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
05-Jan-2026 01:37:09.417 general: debug 1: zone__settimer: zone authors.bind/CH: enter
05-Jan-2026 01:37:09.417 general: notice: FIPS mode is disabled
05-Jan-2026 01:37:09.417 general: notice: running
05-Jan-2026 01:37:09.417 general: debug 1: zone__settimer: zone version.bind/CH: enter
05-Jan-2026 01:37:09.417 general: debug 1: zone__settimer: managed-keys-zone: enter
05-Jan-2026 01:37:09.417 general: debug 1: zone__settimer: managed-keys-zone: enter
05-Jan-2026 01:37:09.417 general: debug 1: zone__settimer: managed-keys-zone: enter
05-Jan-2026 01:37:09.417 general: debug 1: zone__settimer: zone version.bind/CH: enter
05-Jan-2026 01:37:09.417 general: debug 1: zone_maintenance: managed-keys-zone: enter
05-Jan-2026 01:37:09.417 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
05-Jan-2026 01:37:09.417 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
05-Jan-2026 01:37:09.417 general: debug 1: managed-keys-zone: next key refresh: 05-Jan-2026 01:37:09.417
05-Jan-2026 01:37:09.417 general: debug 1: zone__settimer: zone id.server/CH: enter
05-Jan-2026 01:37:09.417 general: debug 1: zone_maintenance: zone version.bind/CH: enter
05-Jan-2026 01:37:09.417 general: debug 1: zone__settimer: managed-keys-zone: enter
05-Jan-2026 01:37:09.417 resolver: debug 1: fetch: ./DNSKEY
05-Jan-2026 01:37:09.417 general: debug 1: zone__settimer: managed-keys-zone: enter
05-Jan-2026 01:37:09.417 general: debug 1: zone__settimer: zone version.bind/CH: enter
05-Jan-2026 01:37:09.418 resolver: debug 1: fetch: ./NS
05-Jan-2026 01:37:09.418 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
05-Jan-2026 01:37:09.418 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
05-Jan-2026 01:37:09.418 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
05-Jan-2026 01:37:09.418 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
05-Jan-2026 01:37:09.418 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
05-Jan-2026 01:37:09.418 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
05-Jan-2026 01:37:09.418 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
05-Jan-2026 01:37:09.418 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
05-Jan-2026 01:37:09.418 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
05-Jan-2026 01:37:09.418 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
05-Jan-2026 01:37:09.419 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
05-Jan-2026 01:37:09.419 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
05-Jan-2026 01:37:09.419 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
05-Jan-2026 01:37:09.419 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
05-Jan-2026 01:37:09.419 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
05-Jan-2026 01:37:09.419 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
05-Jan-2026 01:37:09.419 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
05-Jan-2026 01:37:09.419 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
05-Jan-2026 01:37:09.419 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
05-Jan-2026 01:37:09.419 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
05-Jan-2026 01:37:09.419 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
05-Jan-2026 01:37:09.419 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
05-Jan-2026 01:37:09.419 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
05-Jan-2026 01:37:09.419 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
05-Jan-2026 01:37:09.419 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
05-Jan-2026 01:37:09.419 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
05-Jan-2026 01:37:09.430 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.
05-Jan-2026 01:37:09.430 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
05-Jan-2026 01:37:09.430 general: debug 1: managed-keys-zone: next key refresh: 06-Jan-2026 01:37:09.430
05-Jan-2026 01:37:09.430 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.
05-Jan-2026 01:37:09.430 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
05-Jan-2026 01:37:09.430 general: debug 1: managed-keys-zone: next key refresh: 06-Jan-2026 01:37:09.430
05-Jan-2026 01:37:09.430 general: debug 1: zone_journal: managed-keys-zone: enter
05-Jan-2026 01:37:09.442 general: debug 1: zone_needdump: managed-keys-zone: enter
05-Jan-2026 01:37:09.442 general: debug 1: zone__settimer: managed-keys-zone: enter
05-Jan-2026 01:37:09.442 general: debug 1: zone__settimer: managed-keys-zone: enter
05-Jan-2026 01:37:09.442 general: debug 1: zone__settimer: managed-keys-zone: enter
05-Jan-2026 01:37:09.493 resolver: debug 1: resolver priming query complete: success
05-Jan-2026 01:37:33.428 general: debug 1: zone_maintenance: managed-keys-zone: enter
05-Jan-2026 01:37:33.428 general: debug 1: zone_dump: managed-keys-zone: enter
05-Jan-2026 01:37:33.428 general: debug 1: zone__settimer: managed-keys-zone: enter
05-Jan-2026 01:37:33.432 general: debug 1: dump_done: managed-keys-zone: enter
05-Jan-2026 01:37:33.432 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
05-Jan-2026 01:37:40.087 network: info: listening on IPv6 interface tapeth0-581068, fe80::18da:9fff:feeb:1cbf%11#53
05-Jan-2026 01:37:50.199 network: info: listening on IPv6 interface tapeth0-cabb2b, fe80::bc05:5cff:feab:4555%13#53
05-Jan-2026 01:39:41.453 network: info: listening on IPv4 interface kube-ipvs0, 10.99.2.197#53
05-Jan-2026 01:39:48.984 network: info: listening on IPv6 interface tapeth0-a04cc2, fe80::e86e:44ff:fe02:20a4%15#53
05-Jan-2026 01:39:48.998 network: info: listening on IPv6 interface tapeth0-5a361a, fe80::bc5f:d6ff:fe9b:74f0%17#53
05-Jan-2026 01:39:52.311 network: info: listening on IPv6 interface veth71c866e2-2, fe80::4da:a9ff:fec1:9c91%18#53
05-Jan-2026 01:39:58.199 network: info: listening on IPv6 interface tapeth0-fc96fb, fe80::2c60:42ff:fe04:236c%20#53
05-Jan-2026 01:40:31.127 network: info: no longer listening on fe80::2c60:42ff:fe04:236c%20#53
05-Jan-2026 01:40:38.019 network: info: no longer listening on fe80::4da:a9ff:fec1:9c91%18#53
05-Jan-2026 01:40:39.457 network: info: no longer listening on fe80::e86e:44ff:fe02:20a4%15#53
05-Jan-2026 01:40:44.214 network: info: no longer listening on fe80::bc5f:d6ff:fe9b:74f0%17#53
05-Jan-2026 01:41:04.503 network: info: listening on IPv6 interface tapeth0-2c0e79, fe80::4c85:44ff:feca:4d72%22#53
05-Jan-2026 01:41:04.512 network: info: listening on IPv6 interface tapeth0-de0e79, fe80::dcd7:cfff:fe91:9131%24#53
05-Jan-2026 01:41:04.513 network: info: listening on IPv6 interface tapeth0-186039, fe80::7044:89ff:feb0:3620%26#53
05-Jan-2026 01:41:09.303 network: info: listening on IPv6 interface tapeth0-c028c1, fe80::5099:58ff:fed9:d795%28#53
05-Jan-2026 01:41:09.311 network: info: listening on IPv6 interface tapeth0-db820a, fe80::1034:42ff:feab:4de1%30#53
05-Jan-2026 01:41:09.312 network: info: listening on IPv6 interface tapeth0-7fca35, fe80::68bc:67ff:fe0a:21ad%32#53
05-Jan-2026 01:41:09.313 network: info: listening on IPv6 interface tapeth0-571293, fe80::dc01:7aff:fe51:bafe%34#53
05-Jan-2026 01:41:14.999 network: info: listening on IPv6 interface tapeth0-c9e28b, fe80::b8f2:eff:fe6d:8829%36#53
05-Jan-2026 01:41:23.564 network: info: listening on IPv4 interface kube-ipvs0, 10.100.127.145#53
05-Jan-2026 01:44:32.818 network: info: no longer listening on fe80::dcd7:cfff:fe91:9131%24#53
05-Jan-2026 01:44:32.822 network: info: no longer listening on fe80::7044:89ff:feb0:3620%26#53
05-Jan-2026 01:44:32.835 network: info: no longer listening on fe80::5099:58ff:fed9:d795%28#53
05-Jan-2026 01:44:32.847 network: info: no longer listening on fe80::4c85:44ff:feca:4d72%22#53
05-Jan-2026 01:45:03.398 network: info: no longer listening on fe80::dc01:7aff:fe51:bafe%34#53
05-Jan-2026 01:45:03.449 network: info: no longer listening on fe80::1034:42ff:feab:4de1%30#53
05-Jan-2026 01:45:03.450 network: info: no longer listening on fe80::68bc:67ff:fe0a:21ad%32#53
05-Jan-2026 01:45:03.450 network: info: no longer listening on fe80::b8f2:eff:fe6d:8829%36#53
05-Jan-2026 01:45:19.037 network: info: no longer listening on 10.100.127.145#53