26-Feb-2026 01:34:04.581 general: debug 1: now using logging configuration from config file
26-Feb-2026 01:34:04.582 general: debug 1: loop exclusive mode: ending
26-Feb-2026 01:34:04.582 general: debug 1: loop exclusive mode: ended
26-Feb-2026 01:34:04.582 general: notice: command channel listening on 127.0.0.1#8094
26-Feb-2026 01:34:04.582 general: debug 1: load_configuration: success
26-Feb-2026 01:34:04.582 general: debug 1: loop exclusive mode: starting
26-Feb-2026 01:34:04.582 general: debug 1: loop exclusive mode: started
26-Feb-2026 01:34:04.582 zoneload: debug 1: managed-keys-zone: starting load
26-Feb-2026 01:34:04.582 general: debug 1: zone_startload: managed-keys-zone: enter
26-Feb-2026 01:34:04.582 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
26-Feb-2026 01:34:04.582 general: debug 1: managed-keys-zone: creating SOA
26-Feb-2026 01:34:04.582 zoneload: debug 1: managed-keys-zone: loaded; checking validity
26-Feb-2026 01:34:04.582 zoneload: info: managed-keys-zone: loaded serial 0
26-Feb-2026 01:34:04.582 general: debug 1: loop exclusive mode: ending
26-Feb-2026 01:34:04.582 zoneload: debug 1: zone hostname.bind/CH: starting load
26-Feb-2026 01:34:04.582 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
26-Feb-2026 01:34:04.583 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
26-Feb-2026 01:34:04.583 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
26-Feb-2026 01:34:04.583 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
26-Feb-2026 01:34:04.583 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
26-Feb-2026 01:34:04.583 general: debug 1: loop exclusive mode: ended
26-Feb-2026 01:34:04.583 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Feb-2026 01:34:04.583 zoneload: debug 1: zone authors.bind/CH: starting load
26-Feb-2026 01:34:04.583 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
26-Feb-2026 01:34:04.583 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
26-Feb-2026 01:34:04.583 zoneload: debug 1: zone version.bind/CH: starting load
26-Feb-2026 01:34:04.583 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
26-Feb-2026 01:34:04.583 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
26-Feb-2026 01:34:04.583 zoneload: debug 1: zone id.server/CH: starting load
26-Feb-2026 01:34:04.583 zoneload: debug 1: zone id.server/CH: loaded; checking validity
26-Feb-2026 01:34:04.583 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
26-Feb-2026 01:34:04.583 general: notice: all zones loaded
26-Feb-2026 01:34:04.583 general: debug 1: managed-keys-zone: synchronizing trusted keys
26-Feb-2026 01:34:04.583 general: debug 1: create_keydata: managed-keys-zone: enter
26-Feb-2026 01:34:04.583 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
26-Feb-2026 01:34:04.583 general: debug 1: managed-keys-zone: next key refresh: 26-Feb-2026 01:34:04.583
26-Feb-2026 01:34:04.583 general: debug 1: zone_journal: managed-keys-zone: enter
26-Feb-2026 01:34:04.583 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
26-Feb-2026 01:34:04.605 general: debug 1: zone_needdump: managed-keys-zone: enter
26-Feb-2026 01:34:04.605 general: notice: FIPS mode is disabled
26-Feb-2026 01:34:04.605 general: notice: running
26-Feb-2026 01:34:04.605 general: debug 1: zone__settimer: zone authors.bind/CH: enter
26-Feb-2026 01:34:04.605 general: debug 1: zone__settimer: zone version.bind/CH: enter
26-Feb-2026 01:34:04.605 general: debug 1: zone__settimer: zone id.server/CH: enter
26-Feb-2026 01:34:04.605 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Feb-2026 01:34:04.605 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Feb-2026 01:34:04.605 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Feb-2026 01:34:04.605 general: debug 1: zone__settimer: zone version.bind/CH: enter
26-Feb-2026 01:34:04.605 general: debug 1: zone__settimer: zone authors.bind/CH: enter
26-Feb-2026 01:34:04.605 general: debug 1: zone__settimer: zone id.server/CH: enter
26-Feb-2026 01:34:04.605 general: debug 1: zone_maintenance: managed-keys-zone: enter
26-Feb-2026 01:34:04.605 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
26-Feb-2026 01:34:04.605 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
26-Feb-2026 01:34:04.605 general: debug 1: managed-keys-zone: next key refresh: 26-Feb-2026 01:34:04.605
26-Feb-2026 01:34:04.605 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
26-Feb-2026 01:34:04.605 general: debug 1: zone_maintenance: zone version.bind/CH: enter
26-Feb-2026 01:34:04.605 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
26-Feb-2026 01:34:04.605 general: debug 1: zone_maintenance: zone id.server/CH: enter
26-Feb-2026 01:34:04.605 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Feb-2026 01:34:04.605 resolver: debug 1: fetch: ./DNSKEY
26-Feb-2026 01:34:04.605 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Feb-2026 01:34:04.605 general: debug 1: zone__settimer: zone version.bind/CH: enter
26-Feb-2026 01:34:04.605 general: debug 1: zone__settimer: zone authors.bind/CH: enter
26-Feb-2026 01:34:04.605 general: debug 1: zone__settimer: zone id.server/CH: enter
26-Feb-2026 01:34:04.605 resolver: debug 1: fetch: ./NS
26-Feb-2026 01:34:04.605 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
26-Feb-2026 01:34:04.606 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
26-Feb-2026 01:34:04.654 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.
26-Feb-2026 01:34:04.654 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
26-Feb-2026 01:34:04.654 general: debug 1: managed-keys-zone: next key refresh: 27-Feb-2026 01:34:04.654
26-Feb-2026 01:34:04.654 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.
26-Feb-2026 01:34:04.654 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
26-Feb-2026 01:34:04.654 general: debug 1: managed-keys-zone: next key refresh: 27-Feb-2026 01:34:04.654
26-Feb-2026 01:34:04.654 general: debug 1: zone_journal: managed-keys-zone: enter
26-Feb-2026 01:34:04.671 general: debug 1: zone_needdump: managed-keys-zone: enter
26-Feb-2026 01:34:04.673 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Feb-2026 01:34:04.673 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Feb-2026 01:34:04.673 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Feb-2026 01:34:04.776 resolver: debug 1: resolver priming query complete: success
26-Feb-2026 01:34:28.628 general: debug 1: zone_maintenance: managed-keys-zone: enter
26-Feb-2026 01:34:28.628 general: debug 1: zone_dump: managed-keys-zone: enter
26-Feb-2026 01:34:28.630 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Feb-2026 01:34:28.633 general: debug 1: dump_done: managed-keys-zone: enter
26-Feb-2026 01:34:28.633 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
26-Feb-2026 01:34:36.642 network: info: listening on IPv6 interface tapeth0-33949d, fe80::78bb:dfff:fef2:2d2f%11#53
26-Feb-2026 01:34:41.828 network: info: listening on IPv6 interface tapeth0-d91571, fe80::3005:d3ff:fe29:8962%13#53
26-Feb-2026 01:36:35.292 network: info: listening on IPv4 interface kube-ipvs0, 10.111.132.114#53
26-Feb-2026 01:36:42.787 network: info: listening on IPv6 interface tapeth0-1ccd11, fe80::10cb:4bff:fe52:2f25%15#53
26-Feb-2026 01:36:42.796 network: info: listening on IPv6 interface tapeth0-6f84dd, fe80::600c:9cff:fe4a:2a5%17#53
26-Feb-2026 01:36:47.716 network: info: listening on IPv6 interface vethd11fb873-5, fe80::64e5:dcff:fe41:dbc8%18#53
26-Feb-2026 01:36:52.451 network: info: listening on IPv6 interface tapeth0-10a81c, fe80::87a:d2ff:fef5:d063%20#53
26-Feb-2026 01:37:30.988 network: info: no longer listening on fe80::87a:d2ff:fef5:d063%20#53
26-Feb-2026 01:37:37.962 network: info: no longer listening on fe80::64e5:dcff:fe41:dbc8%18#53
26-Feb-2026 01:37:38.678 network: info: no longer listening on fe80::600c:9cff:fe4a:2a5%17#53
26-Feb-2026 01:37:43.649 network: info: no longer listening on fe80::10cb:4bff:fe52:2f25%15#53
26-Feb-2026 01:38:03.748 network: info: listening on IPv6 interface tapeth0-5614e1, fe80::9c8d:b1ff:fefd:58f1%22#53
26-Feb-2026 01:38:03.754 network: info: listening on IPv6 interface tapeth0-859d9c, fe80::cfe:a7ff:fe7c:3ebb%24#53
26-Feb-2026 01:38:03.757 network: info: listening on IPv6 interface tapeth0-c0161f, fe80::dc1f:57ff:feb8:f71c%26#53
26-Feb-2026 01:38:09.444 network: info: listening on IPv6 interface tapeth0-b79c91, fe80::8031:a7ff:febc:8a77%28#53
26-Feb-2026 01:38:09.445 network: info: listening on IPv6 interface tapeth0-a7d083, fe80::1810:5dff:fe7b:7e1d%30#53
26-Feb-2026 01:38:09.448 network: info: listening on IPv6 interface tapeth0-85543d, fe80::449:e8ff:fe5e:7056%32#53
26-Feb-2026 01:38:14.243 network: info: listening on IPv6 interface tapeth0-8abe98, fe80::ec11:9cff:fe0c:c929%34#53
26-Feb-2026 01:38:14.245 network: info: listening on IPv6 interface tapeth0-72e6c8, fe80::f029:b8ff:fe91:f1e0%36#53
26-Feb-2026 01:38:23.050 network: info: listening on IPv4 interface kube-ipvs0, 10.98.131.78#53
26-Feb-2026 01:41:33.091 network: info: no longer listening on fe80::1810:5dff:fe7b:7e1d%30#53
26-Feb-2026 01:41:33.118 network: info: no longer listening on fe80::dc1f:57ff:feb8:f71c%26#53
26-Feb-2026 01:41:33.146 network: info: no longer listening on fe80::cfe:a7ff:fe7c:3ebb%24#53
26-Feb-2026 01:41:33.161 network: info: no longer listening on fe80::9c8d:b1ff:fefd:58f1%22#53
26-Feb-2026 01:42:02.751 network: info: no longer listening on fe80::ec11:9cff:fe0c:c929%34#53
26-Feb-2026 01:42:02.777 network: info: no longer listening on fe80::f029:b8ff:fe91:f1e0%36#53
26-Feb-2026 01:42:02.801 network: info: no longer listening on fe80::8031:a7ff:febc:8a77%28#53
26-Feb-2026 01:42:02.818 network: info: no longer listening on fe80::449:e8ff:fe5e:7056%32#53
26-Feb-2026 01:42:18.566 network: info: no longer listening on 10.98.131.78#53