19-Jan-2026 01:33:41.061 general: debug 1: now using logging configuration from config file
19-Jan-2026 01:33:41.061 general: debug 1: loop exclusive mode: ending
19-Jan-2026 01:33:41.061 general: debug 1: loop exclusive mode: ended
19-Jan-2026 01:33:41.061 general: notice: command channel listening on 127.0.0.1#8094
19-Jan-2026 01:33:41.061 general: debug 1: load_configuration: success
19-Jan-2026 01:33:41.061 general: debug 1: loop exclusive mode: starting
19-Jan-2026 01:33:41.064 general: debug 1: loop exclusive mode: started
19-Jan-2026 01:33:41.064 zoneload: debug 1: managed-keys-zone: starting load
19-Jan-2026 01:33:41.064 general: debug 1: zone_startload: managed-keys-zone: enter
19-Jan-2026 01:33:41.064 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
19-Jan-2026 01:33:41.064 general: debug 1: managed-keys-zone: creating SOA
19-Jan-2026 01:33:41.067 zoneload: debug 1: managed-keys-zone: loaded; checking validity
19-Jan-2026 01:33:41.067 zoneload: info: managed-keys-zone: loaded serial 0
19-Jan-2026 01:33:41.067 general: debug 1: loop exclusive mode: ending
19-Jan-2026 01:33:41.067 zoneload: debug 1: zone version.bind/CH: starting load
19-Jan-2026 01:33:41.067 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
19-Jan-2026 01:33:41.067 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
19-Jan-2026 01:33:41.067 general: debug 1: zone__settimer: zone version.bind/CH: enter
19-Jan-2026 01:33:41.067 general: debug 1: zone_maintenance: zone version.bind/CH: enter
19-Jan-2026 01:33:41.067 general: debug 1: zone__settimer: zone version.bind/CH: enter
19-Jan-2026 01:33:41.067 zoneload: debug 1: zone authors.bind/CH: starting load
19-Jan-2026 01:33:41.067 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
19-Jan-2026 01:33:41.067 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
19-Jan-2026 01:33:41.067 general: debug 1: zone__settimer: zone authors.bind/CH: enter
19-Jan-2026 01:33:41.067 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
19-Jan-2026 01:33:41.067 general: debug 1: zone__settimer: zone authors.bind/CH: enter
19-Jan-2026 01:33:41.067 general: debug 1: loop exclusive mode: ended
19-Jan-2026 01:33:41.067 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Jan-2026 01:33:41.067 zoneload: debug 1: zone id.server/CH: starting load
19-Jan-2026 01:33:41.067 zoneload: debug 1: zone id.server/CH: loaded; checking validity
19-Jan-2026 01:33:41.067 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
19-Jan-2026 01:33:41.067 general: debug 1: zone__settimer: zone id.server/CH: enter
19-Jan-2026 01:33:41.067 general: debug 1: zone_maintenance: zone id.server/CH: enter
19-Jan-2026 01:33:41.067 general: debug 1: zone__settimer: zone id.server/CH: enter
19-Jan-2026 01:33:41.067 zoneload: debug 1: zone hostname.bind/CH: starting load
19-Jan-2026 01:33:41.067 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
19-Jan-2026 01:33:41.067 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
19-Jan-2026 01:33:41.067 general: notice: all zones loaded
19-Jan-2026 01:33:41.067 general: debug 1: managed-keys-zone: synchronizing trusted keys
19-Jan-2026 01:33:41.067 general: debug 1: create_keydata: managed-keys-zone: enter
19-Jan-2026 01:33:41.067 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
19-Jan-2026 01:33:41.067 general: debug 1: managed-keys-zone: next key refresh: 19-Jan-2026 01:33:41.067
19-Jan-2026 01:33:41.067 general: debug 1: zone_journal: managed-keys-zone: enter
19-Jan-2026 01:33:41.067 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
19-Jan-2026 01:33:41.067 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Jan-2026 01:33:41.397 general: debug 1: zone_needdump: managed-keys-zone: enter
19-Jan-2026 01:33:41.398 general: debug 1: zone_maintenance: managed-keys-zone: enter
19-Jan-2026 01:33:41.398 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
19-Jan-2026 01:33:41.398 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
19-Jan-2026 01:33:41.398 general: debug 1: managed-keys-zone: next key refresh: 19-Jan-2026 01:33:41.398
19-Jan-2026 01:33:41.398 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Jan-2026 01:33:41.398 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Jan-2026 01:33:41.398 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Jan-2026 01:33:41.398 resolver: debug 1: fetch: ./DNSKEY
19-Jan-2026 01:33:41.398 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Jan-2026 01:33:41.398 resolver: debug 1: fetch: ./NS
19-Jan-2026 01:33:41.398 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
19-Jan-2026 01:33:41.403 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
19-Jan-2026 01:33:41.404 general: notice: FIPS mode is disabled
19-Jan-2026 01:33:41.404 general: notice: running
19-Jan-2026 01:33:41.404 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
19-Jan-2026 01:33:41.404 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
19-Jan-2026 01:33:41.404 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
19-Jan-2026 01:33:41.404 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
19-Jan-2026 01:33:41.404 general: debug 1: zone__settimer: zone id.server/CH: enter
19-Jan-2026 01:33:41.404 general: debug 1: zone__settimer: zone authors.bind/CH: enter
19-Jan-2026 01:33:41.404 general: debug 1: zone__settimer: zone version.bind/CH: enter
19-Jan-2026 01:33:41.408 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.
19-Jan-2026 01:33:41.408 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
19-Jan-2026 01:33:41.408 general: debug 1: managed-keys-zone: next key refresh: 20-Jan-2026 01:33:41.408
19-Jan-2026 01:33:41.408 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.
19-Jan-2026 01:33:41.408 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
19-Jan-2026 01:33:41.408 general: debug 1: managed-keys-zone: next key refresh: 20-Jan-2026 01:33:41.408
19-Jan-2026 01:33:41.408 general: debug 1: zone_journal: managed-keys-zone: enter
19-Jan-2026 01:33:41.416 general: debug 1: zone_needdump: managed-keys-zone: enter
19-Jan-2026 01:33:41.416 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Jan-2026 01:33:41.416 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Jan-2026 01:33:41.416 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Jan-2026 01:33:41.417 resolver: debug 1: resolver priming query complete: success
19-Jan-2026 01:34:07.416 general: debug 1: zone_maintenance: managed-keys-zone: enter
19-Jan-2026 01:34:07.416 general: debug 1: zone_dump: managed-keys-zone: enter
19-Jan-2026 01:34:07.417 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Jan-2026 01:34:07.422 general: debug 1: dump_done: managed-keys-zone: enter
19-Jan-2026 01:34:07.422 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
19-Jan-2026 01:34:08.312 network: info: listening on IPv6 interface tapeth0-f6f20b, fe80::68ec:5eff:fe65:e439%11#53
19-Jan-2026 01:34:08.323 network: info: listening on IPv6 interface tapeth0-987c0c, fe80::84a4:bfff:fee1:8a2b%13#53
19-Jan-2026 01:35:19.138 network: info: listening on IPv4 interface kube-ipvs0, 10.105.249.170#53
19-Jan-2026 01:35:26.775 network: info: listening on IPv6 interface tapeth0-6d3934, fe80::10eb:1cff:fe31:cab0%15#53
19-Jan-2026 01:35:26.788 network: info: listening on IPv6 interface tapeth0-57f6c2, fe80::bcf9:93ff:fec3:3c07%17#53
19-Jan-2026 01:35:31.710 network: info: listening on IPv6 interface veth7eb8bdb7-b, fe80::b8fd:2ff:fe78:4abf%18#53
19-Jan-2026 01:35:36.889 network: info: listening on IPv6 interface tapeth0-c60303, fe80::1058:22ff:febc:53dc%20#53
19-Jan-2026 01:36:15.232 network: info: no longer listening on fe80::1058:22ff:febc:53dc%20#53
19-Jan-2026 01:36:22.150 network: info: no longer listening on fe80::b8fd:2ff:fe78:4abf%18#53
19-Jan-2026 01:36:22.871 network: info: no longer listening on fe80::bcf9:93ff:fec3:3c07%17#53
19-Jan-2026 01:36:27.800 network: info: no longer listening on fe80::10eb:1cff:fe31:cab0%15#53
19-Jan-2026 01:36:47.159 network: info: listening on IPv6 interface tapeth0-dd8611, fe80::c45b:faff:fe10:b159%22#53
19-Jan-2026 01:36:47.160 network: info: listening on IPv6 interface tapeth0-1a7ef3, fe80::cdc:3ff:fedb:a48d%24#53
19-Jan-2026 01:36:51.894 network: info: listening on IPv6 interface tapeth0-96ef9c, fe80::9485:c4ff:fecd:c75b%26#53
19-Jan-2026 01:36:51.899 network: info: listening on IPv6 interface tapeth0-1d8029, fe80::288d:17ff:fe51:1174%28#53
19-Jan-2026 01:36:51.901 network: info: listening on IPv6 interface tapeth0-6a2cff, fe80::16:d1ff:fe34:374d%30#53
19-Jan-2026 01:36:51.901 network: info: listening on IPv6 interface tapeth0-870591, fe80::3c86:78ff:fef9:3ab1%32#53
19-Jan-2026 01:36:57.079 network: info: listening on IPv6 interface tapeth0-df6522, fe80::9c3a:23ff:feb8:94a4%34#53
19-Jan-2026 01:36:57.080 network: info: listening on IPv6 interface tapeth0-5f1682, fe80::784e:63ff:fe42:b827%36#53
19-Jan-2026 01:37:06.862 network: info: listening on IPv4 interface kube-ipvs0, 10.108.150.80#53
19-Jan-2026 01:40:16.270 network: info: no longer listening on fe80::3c86:78ff:fef9:3ab1%32#53
19-Jan-2026 01:40:16.354 network: info: no longer listening on fe80::c45b:faff:fe10:b159%22#53
19-Jan-2026 01:40:16.393 network: info: no longer listening on fe80::9485:c4ff:fecd:c75b%26#53
19-Jan-2026 01:40:16.418 network: info: no longer listening on fe80::cdc:3ff:fedb:a48d%24#53
19-Jan-2026 01:40:46.137 network: info: no longer listening on fe80::16:d1ff:fe34:374d%30#53
19-Jan-2026 01:40:46.170 network: info: no longer listening on fe80::288d:17ff:fe51:1174%28#53
19-Jan-2026 01:40:46.172 network: info: no longer listening on fe80::9c3a:23ff:feb8:94a4%34#53
19-Jan-2026 01:40:46.202 network: info: no longer listening on fe80::784e:63ff:fe42:b827%36#53
19-Jan-2026 01:41:01.788 network: info: no longer listening on 10.108.150.80#53