16-Mar-2026 01:30:36.599 general: debug 1: now using logging configuration from config file
16-Mar-2026 01:30:36.599 general: debug 1: loop exclusive mode: ending
16-Mar-2026 01:30:36.599 general: debug 1: loop exclusive mode: ended
16-Mar-2026 01:30:36.599 general: notice: command channel listening on 127.0.0.1#8094
16-Mar-2026 01:30:36.599 general: debug 1: load_configuration: success
16-Mar-2026 01:30:36.599 general: debug 1: loop exclusive mode: starting
16-Mar-2026 01:30:36.600 general: debug 1: loop exclusive mode: started
16-Mar-2026 01:30:36.600 zoneload: debug 1: managed-keys-zone: starting load
16-Mar-2026 01:30:36.600 general: debug 1: zone_startload: managed-keys-zone: enter
16-Mar-2026 01:30:36.600 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
16-Mar-2026 01:30:36.600 general: debug 1: managed-keys-zone: creating SOA
16-Mar-2026 01:30:36.600 zoneload: debug 1: managed-keys-zone: loaded; checking validity
16-Mar-2026 01:30:36.600 zoneload: info: managed-keys-zone: loaded serial 0
16-Mar-2026 01:30:36.600 general: debug 1: loop exclusive mode: ending
16-Mar-2026 01:30:36.600 general: debug 1: loop exclusive mode: ended
16-Mar-2026 01:30:36.600 zoneload: debug 1: zone hostname.bind/CH: starting load
16-Mar-2026 01:30:36.600 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Mar-2026 01:30:36.600 zoneload: debug 1: zone authors.bind/CH: starting load
16-Mar-2026 01:30:36.600 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
16-Mar-2026 01:30:36.600 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
16-Mar-2026 01:30:36.600 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
16-Mar-2026 01:30:36.600 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
16-Mar-2026 01:30:36.600 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
16-Mar-2026 01:30:36.600 zoneload: debug 1: zone version.bind/CH: starting load
16-Mar-2026 01:30:36.600 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
16-Mar-2026 01:30:36.600 general: debug 1: zone__settimer: zone authors.bind/CH: enter
16-Mar-2026 01:30:36.600 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
16-Mar-2026 01:30:36.600 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
16-Mar-2026 01:30:36.600 general: debug 1: zone__settimer: zone authors.bind/CH: enter
16-Mar-2026 01:30:36.600 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
16-Mar-2026 01:30:36.600 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
16-Mar-2026 01:30:36.600 zoneload: debug 1: zone id.server/CH: starting load
16-Mar-2026 01:30:36.600 zoneload: debug 1: zone id.server/CH: loaded; checking validity
16-Mar-2026 01:30:36.600 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
16-Mar-2026 01:30:36.600 general: notice: all zones loaded
16-Mar-2026 01:30:36.600 general: debug 1: managed-keys-zone: synchronizing trusted keys
16-Mar-2026 01:30:36.600 general: debug 1: create_keydata: managed-keys-zone: enter
16-Mar-2026 01:30:36.601 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
16-Mar-2026 01:30:36.601 general: debug 1: managed-keys-zone: next key refresh: 16-Mar-2026 01:30:36.601
16-Mar-2026 01:30:36.601 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Mar-2026 01:30:36.601 general: debug 1: zone_journal: managed-keys-zone: enter
16-Mar-2026 01:30:36.601 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
16-Mar-2026 01:30:36.660 general: debug 1: zone_needdump: managed-keys-zone: enter
16-Mar-2026 01:30:36.661 general: notice: FIPS mode is disabled
16-Mar-2026 01:30:36.661 general: notice: running
16-Mar-2026 01:30:36.661 general: debug 1: zone__settimer: zone version.bind/CH: enter
16-Mar-2026 01:30:36.661 general: debug 1: zone__settimer: zone id.server/CH: enter
16-Mar-2026 01:30:36.661 general: debug 1: zone__settimer: zone version.bind/CH: enter
16-Mar-2026 01:30:36.661 general: debug 1: zone__settimer: zone id.server/CH: enter
16-Mar-2026 01:30:36.661 general: debug 1: zone_maintenance: zone version.bind/CH: enter
16-Mar-2026 01:30:36.661 general: debug 1: zone_maintenance: managed-keys-zone: enter
16-Mar-2026 01:30:36.661 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
16-Mar-2026 01:30:36.661 general: debug 1: zone_maintenance: zone id.server/CH: enter
16-Mar-2026 01:30:36.661 general: debug 1: zone__settimer: zone version.bind/CH: enter
16-Mar-2026 01:30:36.661 general: debug 1: zone__settimer: zone id.server/CH: enter
16-Mar-2026 01:30:36.661 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
16-Mar-2026 01:30:36.661 general: debug 1: managed-keys-zone: next key refresh: 16-Mar-2026 01:30:36.661
16-Mar-2026 01:30:36.661 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Mar-2026 01:30:36.661 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Mar-2026 01:30:36.661 general: debug 1: zone__settimer: zone authors.bind/CH: enter
16-Mar-2026 01:30:36.661 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Mar-2026 01:30:36.661 resolver: debug 1: fetch: ./DNSKEY
16-Mar-2026 01:30:36.661 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Mar-2026 01:30:36.661 resolver: debug 1: fetch: ./NS
16-Mar-2026 01:30:36.661 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
16-Mar-2026 01:30:36.662 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
16-Mar-2026 01:30:36.663 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
16-Mar-2026 01:30:36.665 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
16-Mar-2026 01:30:36.667 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.
16-Mar-2026 01:30:36.667 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
16-Mar-2026 01:30:36.667 general: debug 1: managed-keys-zone: next key refresh: 17-Mar-2026 01:30:36.667
16-Mar-2026 01:30:36.667 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.
16-Mar-2026 01:30:36.667 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
16-Mar-2026 01:30:36.667 general: debug 1: managed-keys-zone: next key refresh: 17-Mar-2026 01:30:36.667
16-Mar-2026 01:30:36.667 general: debug 1: zone_journal: managed-keys-zone: enter
16-Mar-2026 01:30:36.780 general: debug 1: zone_needdump: managed-keys-zone: enter
16-Mar-2026 01:30:36.780 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Mar-2026 01:30:36.780 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Mar-2026 01:30:36.780 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Mar-2026 01:30:36.787 resolver: debug 1: resolver priming query complete: success
16-Mar-2026 01:31:00.683 general: debug 1: zone_maintenance: managed-keys-zone: enter
16-Mar-2026 01:31:00.683 general: debug 1: zone_dump: managed-keys-zone: enter
16-Mar-2026 01:31:00.689 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Mar-2026 01:31:00.697 general: debug 1: dump_done: managed-keys-zone: enter
16-Mar-2026 01:31:00.697 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
16-Mar-2026 01:31:33.045 network: info: listening on IPv6 interface tapeth0-3046e4, fe80::a01f:c5ff:fe68:f87d%11#53
16-Mar-2026 01:31:33.046 network: info: listening on IPv6 interface tapeth0-0fae70, fe80::94e7:aeff:fec1:d1bf%13#53
16-Mar-2026 01:32:51.275 network: info: listening on IPv4 interface kube-ipvs0, 10.107.204.78#53
16-Mar-2026 01:32:58.636 network: info: listening on IPv6 interface tapeth0-127d33, fe80::e887:1dff:fead:fa51%15#53
16-Mar-2026 01:32:58.645 network: info: listening on IPv6 interface tapeth0-92626c, fe80::ec6f:bdff:fe65:ead7%17#53
16-Mar-2026 01:33:01.057 network: info: listening on IPv6 interface veth1d775f13-f, fe80::10d9:c5ff:fe62:7c98%18#53
16-Mar-2026 01:33:07.380 network: info: listening on IPv6 interface tapeth0-5d2b42, fe80::1026:dfff:feaa:510%20#53
16-Mar-2026 01:33:45.485 network: info: no longer listening on fe80::1026:dfff:feaa:510%20#53
16-Mar-2026 01:33:52.008 network: info: no longer listening on fe80::10d9:c5ff:fe62:7c98%18#53
16-Mar-2026 01:33:52.910 network: info: no longer listening on fe80::ec6f:bdff:fe65:ead7%17#53
16-Mar-2026 01:33:57.891 network: info: no longer listening on fe80::e887:1dff:fead:fa51%15#53
16-Mar-2026 01:34:17.844 network: info: listening on IPv6 interface tapeth0-1b4c3b, fe80::f4c9:b3ff:feb1:6d0f%22#53
16-Mar-2026 01:34:17.847 network: info: listening on IPv6 interface tapeth0-0e4274, fe80::10b0:1aff:fe26:4c0f%24#53
16-Mar-2026 01:34:17.848 network: info: listening on IPv6 interface tapeth0-885684, fe80::b8ad:31ff:fe56:430a%26#53
16-Mar-2026 01:34:23.412 network: info: listening on IPv6 interface tapeth0-fc210a, fe80::486b:4dff:fec1:43%28#53
16-Mar-2026 01:34:23.412 network: info: listening on IPv6 interface tapeth0-3a4db4, fe80::ac31:83ff:fec3:bac9%30#53
16-Mar-2026 01:34:23.413 network: info: listening on IPv6 interface tapeth0-e00f6d, fe80::d08b:6cff:fe3f:7dd1%32#53
16-Mar-2026 01:34:27.572 network: info: listening on IPv6 interface tapeth0-7cdce6, fe80::d4c3:3cff:fe95:a0b2%34#53
16-Mar-2026 01:34:27.576 network: info: listening on IPv6 interface tapeth0-4ac852, fe80::94b8:74ff:fe81:67d4%36#53
16-Mar-2026 01:34:37.208 network: info: listening on IPv4 interface kube-ipvs0, 10.104.206.138#53
16-Mar-2026 01:37:47.216 network: info: no longer listening on fe80::ac31:83ff:fec3:bac9%30#53
16-Mar-2026 01:37:47.232 network: info: no longer listening on fe80::b8ad:31ff:fe56:430a%26#53
16-Mar-2026 01:37:47.257 network: info: no longer listening on fe80::f4c9:b3ff:feb1:6d0f%22#53
16-Mar-2026 01:37:47.279 network: info: no longer listening on fe80::10b0:1aff:fe26:4c0f%24#53
16-Mar-2026 01:38:16.930 network: info: no longer listening on fe80::486b:4dff:fec1:43%28#53
16-Mar-2026 01:38:16.947 network: info: no longer listening on fe80::d08b:6cff:fe3f:7dd1%32#53
16-Mar-2026 01:38:16.975 network: info: no longer listening on fe80::d4c3:3cff:fe95:a0b2%34#53
16-Mar-2026 01:38:16.987 network: info: no longer listening on fe80::94b8:74ff:fe81:67d4%36#53
16-Mar-2026 01:38:32.658 network: info: no longer listening on 10.104.206.138#53