12-Feb-2026 01:41:35.982 general: debug 1: now using logging configuration from config file
12-Feb-2026 01:41:35.982 general: debug 1: loop exclusive mode: ending
12-Feb-2026 01:41:35.982 general: debug 1: loop exclusive mode: ended
12-Feb-2026 01:41:35.982 general: notice: command channel listening on 127.0.0.1#8094
12-Feb-2026 01:41:35.982 general: debug 1: load_configuration: success
12-Feb-2026 01:41:35.982 general: debug 1: loop exclusive mode: starting
12-Feb-2026 01:41:35.998 general: debug 1: loop exclusive mode: started
12-Feb-2026 01:41:35.998 zoneload: debug 1: managed-keys-zone: starting load
12-Feb-2026 01:41:35.998 general: debug 1: zone_startload: managed-keys-zone: enter
12-Feb-2026 01:41:35.998 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
12-Feb-2026 01:41:35.998 general: debug 1: managed-keys-zone: creating SOA
12-Feb-2026 01:41:35.998 zoneload: debug 1: managed-keys-zone: loaded; checking validity
12-Feb-2026 01:41:35.998 zoneload: info: managed-keys-zone: loaded serial 0
12-Feb-2026 01:41:35.998 general: debug 1: loop exclusive mode: ending
12-Feb-2026 01:41:35.998 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 01:41:35.998 zoneload: debug 1: zone authors.bind/CH: starting load
12-Feb-2026 01:41:35.998 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
12-Feb-2026 01:41:35.998 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
12-Feb-2026 01:41:35.998 zoneload: debug 1: zone hostname.bind/CH: starting load
12-Feb-2026 01:41:35.998 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
12-Feb-2026 01:41:35.998 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
12-Feb-2026 01:41:35.998 zoneload: debug 1: zone version.bind/CH: starting load
12-Feb-2026 01:41:35.998 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
12-Feb-2026 01:41:35.998 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
12-Feb-2026 01:41:35.998 general: debug 1: zone__settimer: zone authors.bind/CH: enter
12-Feb-2026 01:41:35.998 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
12-Feb-2026 01:41:35.998 general: debug 1: zone__settimer: zone version.bind/CH: enter
12-Feb-2026 01:41:35.998 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
12-Feb-2026 01:41:35.998 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
12-Feb-2026 01:41:35.998 general: debug 1: zone_maintenance: zone version.bind/CH: enter
12-Feb-2026 01:41:35.998 general: debug 1: zone__settimer: zone authors.bind/CH: enter
12-Feb-2026 01:41:35.998 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
12-Feb-2026 01:41:35.998 general: debug 1: zone__settimer: zone version.bind/CH: enter
12-Feb-2026 01:41:35.998 zoneload: debug 1: zone id.server/CH: starting load
12-Feb-2026 01:41:35.998 zoneload: debug 1: zone id.server/CH: loaded; checking validity
12-Feb-2026 01:41:35.998 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
12-Feb-2026 01:41:35.998 general: notice: all zones loaded
12-Feb-2026 01:41:35.998 general: debug 1: managed-keys-zone: synchronizing trusted keys
12-Feb-2026 01:41:35.999 general: debug 1: create_keydata: managed-keys-zone: enter
12-Feb-2026 01:41:35.999 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
12-Feb-2026 01:41:35.999 general: debug 1: managed-keys-zone: next key refresh: 12-Feb-2026 01:41:35.999
12-Feb-2026 01:41:35.999 general: debug 1: zone_journal: managed-keys-zone: enter
12-Feb-2026 01:41:35.999 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
12-Feb-2026 01:41:35.999 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 01:41:35.999 general: debug 1: loop exclusive mode: ended
12-Feb-2026 01:41:36.020 general: debug 1: zone_needdump: managed-keys-zone: enter
12-Feb-2026 01:41:36.020 general: notice: FIPS mode is disabled
12-Feb-2026 01:41:36.020 general: notice: running
12-Feb-2026 01:41:36.020 general: debug 1: zone__settimer: zone id.server/CH: enter
12-Feb-2026 01:41:36.020 general: debug 1: zone__settimer: zone id.server/CH: enter
12-Feb-2026 01:41:36.020 general: debug 1: zone_maintenance: zone id.server/CH: enter
12-Feb-2026 01:41:36.020 general: debug 1: zone__settimer: zone id.server/CH: enter
12-Feb-2026 01:41:36.020 general: debug 1: zone_maintenance: managed-keys-zone: enter
12-Feb-2026 01:41:36.020 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
12-Feb-2026 01:41:36.021 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
12-Feb-2026 01:41:36.021 general: debug 1: managed-keys-zone: next key refresh: 12-Feb-2026 01:41:36.021
12-Feb-2026 01:41:36.021 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 01:41:36.021 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 01:41:36.021 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 01:41:36.021 resolver: debug 1: fetch: ./DNSKEY
12-Feb-2026 01:41:36.021 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 01:41:36.021 resolver: debug 1: fetch: ./NS
12-Feb-2026 01:41:36.021 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
12-Feb-2026 01:41:36.021 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
12-Feb-2026 01:41:36.021 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
12-Feb-2026 01:41:36.021 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
12-Feb-2026 01:41:36.021 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
12-Feb-2026 01:41:36.021 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
12-Feb-2026 01:41:36.021 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
12-Feb-2026 01:41:36.021 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
12-Feb-2026 01:41:36.022 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
12-Feb-2026 01:41:36.022 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
12-Feb-2026 01:41:36.022 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
12-Feb-2026 01:41:36.022 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
12-Feb-2026 01:41:36.022 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
12-Feb-2026 01:41:36.022 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
12-Feb-2026 01:41:36.022 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
12-Feb-2026 01:41:36.022 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
12-Feb-2026 01:41:36.022 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
12-Feb-2026 01:41:36.022 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
12-Feb-2026 01:41:36.022 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
12-Feb-2026 01:41:36.022 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
12-Feb-2026 01:41:36.022 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
12-Feb-2026 01:41:36.022 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
12-Feb-2026 01:41:36.025 general: debug 1: zone__settimer: zone version.bind/CH: enter
12-Feb-2026 01:41:36.025 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
12-Feb-2026 01:41:36.025 general: debug 1: zone__settimer: zone authors.bind/CH: enter
12-Feb-2026 01:41:36.025 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
12-Feb-2026 01:41:36.025 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
12-Feb-2026 01:41:36.025 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
12-Feb-2026 01:41:36.083 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-Feb-2026 01:41:36.083 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
12-Feb-2026 01:41:36.083 general: debug 1: managed-keys-zone: next key refresh: 13-Feb-2026 01:41:36.083
12-Feb-2026 01:41:36.083 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-Feb-2026 01:41:36.083 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
12-Feb-2026 01:41:36.083 general: debug 1: managed-keys-zone: next key refresh: 13-Feb-2026 01:41:36.083
12-Feb-2026 01:41:36.083 general: debug 1: zone_journal: managed-keys-zone: enter
12-Feb-2026 01:41:36.103 general: debug 1: zone_needdump: managed-keys-zone: enter
12-Feb-2026 01:41:36.103 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 01:41:36.103 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 01:41:36.103 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 01:41:36.129 resolver: debug 1: resolver priming query complete: success
12-Feb-2026 01:42:01.127 general: debug 1: zone_maintenance: managed-keys-zone: enter
12-Feb-2026 01:42:01.127 general: debug 1: zone_dump: managed-keys-zone: enter
12-Feb-2026 01:42:01.129 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 01:42:01.132 general: debug 1: dump_done: managed-keys-zone: enter
12-Feb-2026 01:42:01.132 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
12-Feb-2026 01:42:01.796 network: info: listening on IPv6 interface tapeth0-c4a3c1, fe80::58cc:2ff:fe9f:5958%11#53
12-Feb-2026 01:42:06.789 network: info: listening on IPv6 interface tapeth0-041a2c, fe80::788e:88ff:fea2:7840%13#53
12-Feb-2026 01:43:49.008 network: info: listening on IPv4 interface kube-ipvs0, 10.107.131.50#53
12-Feb-2026 01:43:57.255 network: info: listening on IPv6 interface tapeth0-6d3114, fe80::286f:26ff:fe33:3c8%15#53
12-Feb-2026 01:43:57.258 network: info: listening on IPv6 interface tapeth0-8b2a59, fe80::1064:40ff:fe8d:a8d8%17#53
12-Feb-2026 01:44:02.244 network: info: listening on IPv6 interface vethf945de1f-0, fe80::3c99:6fff:fe7a:902b%18#53
12-Feb-2026 01:44:07.114 network: info: listening on IPv6 interface tapeth0-70ed22, fe80::8ca5:5aff:fea3:4f1c%20#53
12-Feb-2026 01:44:39.803 network: info: no longer listening on fe80::8ca5:5aff:fea3:4f1c%20#53
12-Feb-2026 01:44:46.577 network: info: no longer listening on fe80::3c99:6fff:fe7a:902b%18#53
12-Feb-2026 01:44:47.820 network: info: no longer listening on fe80::1064:40ff:fe8d:a8d8%17#53
12-Feb-2026 01:44:52.689 network: info: no longer listening on fe80::286f:26ff:fe33:3c8%15#53
12-Feb-2026 01:45:13.027 network: info: listening on IPv6 interface tapeth0-3dfa96, fe80::44b9:27ff:fe0f:da1e%22#53
12-Feb-2026 01:45:13.028 network: info: listening on IPv6 interface tapeth0-926016, fe80::b461:55ff:fe43:9e44%24#53
12-Feb-2026 01:45:13.029 network: info: listening on IPv6 interface tapeth0-8a28e3, fe80::78e0:dcff:feb3:18d7%26#53
12-Feb-2026 01:45:17.830 network: info: listening on IPv6 interface tapeth0-d0891b, fe80::de:23ff:fedb:fe06%28#53
12-Feb-2026 01:45:17.837 network: info: listening on IPv6 interface tapeth0-8baef4, fe80::c482:26ff:feef:ac31%30#53
12-Feb-2026 01:45:17.838 network: info: listening on IPv6 interface tapeth0-725d98, fe80::dcde:83ff:fea2:68ed%32#53
12-Feb-2026 01:45:23.013 network: info: listening on IPv6 interface tapeth0-12aa9b, fe80::af:8aff:fe00:953c%34#53
12-Feb-2026 01:45:23.018 network: info: listening on IPv6 interface tapeth0-6e41e5, fe80::30a0:b8ff:fe59:622%36#53
12-Feb-2026 01:45:32.650 network: info: listening on IPv4 interface kube-ipvs0, 10.104.50.72#53
12-Feb-2026 01:48:42.714 network: info: no longer listening on fe80::dcde:83ff:fea2:68ed%32#53
12-Feb-2026 01:48:42.727 network: info: no longer listening on fe80::78e0:dcff:feb3:18d7%26#53
12-Feb-2026 01:48:42.741 network: info: no longer listening on fe80::b461:55ff:fe43:9e44%24#53
12-Feb-2026 01:48:42.751 network: info: no longer listening on fe80::44b9:27ff:fe0f:da1e%22#53
12-Feb-2026 01:49:13.110 network: info: no longer listening on fe80::de:23ff:fedb:fe06%28#53
12-Feb-2026 01:49:13.137 network: info: no longer listening on fe80::c482:26ff:feef:ac31%30#53
12-Feb-2026 01:49:13.148 network: info: no longer listening on fe80::af:8aff:fe00:953c%34#53
12-Feb-2026 01:49:13.156 network: info: no longer listening on fe80::30a0:b8ff:fe59:622%36#53
12-Feb-2026 01:49:28.798 network: info: no longer listening on 10.104.50.72#53