26-Mar-2026 01:44:30.079 general: debug 1: now using logging configuration from config file
26-Mar-2026 01:44:30.079 general: debug 1: loop exclusive mode: ending
26-Mar-2026 01:44:30.079 general: debug 1: loop exclusive mode: ended
26-Mar-2026 01:44:30.079 general: notice: command channel listening on 127.0.0.1#8094
26-Mar-2026 01:44:30.079 general: info: VDNS cleanup pass1: 0 departing views cleared
26-Mar-2026 01:44:30.079 general: info: VDNS cleanup pass2: 2 staying views re-checked
26-Mar-2026 01:44:30.080 general: debug 1: load_configuration: success
26-Mar-2026 01:44:30.080 general: debug 1: loop exclusive mode: starting
26-Mar-2026 01:44:30.107 general: debug 1: loop exclusive mode: started
26-Mar-2026 01:44:30.107 zoneload: debug 1: managed-keys-zone: starting load
26-Mar-2026 01:44:30.107 general: debug 1: zone_startload: managed-keys-zone: enter
26-Mar-2026 01:44:30.107 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
26-Mar-2026 01:44:30.107 general: debug 1: managed-keys-zone: creating SOA
26-Mar-2026 01:44:30.107 zoneload: debug 1: managed-keys-zone: loaded; checking validity
26-Mar-2026 01:44:30.107 zoneload: info: managed-keys-zone: loaded serial 0
26-Mar-2026 01:44:30.107 general: debug 1: loop exclusive mode: ending
26-Mar-2026 01:44:30.107 zoneload: debug 1: zone authors.bind/CH: starting load
26-Mar-2026 01:44:30.107 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
26-Mar-2026 01:44:30.107 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Mar-2026 01:44:30.107 zoneload: debug 1: zone id.server/CH: starting load
26-Mar-2026 01:44:30.108 zoneload: debug 1: zone hostname.bind/CH: starting load
26-Mar-2026 01:44:30.108 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
26-Mar-2026 01:44:30.108 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
26-Mar-2026 01:44:30.108 zoneload: debug 1: zone id.server/CH: loaded; checking validity
26-Mar-2026 01:44:30.108 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
26-Mar-2026 01:44:30.108 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
26-Mar-2026 01:44:30.108 general: debug 1: zone__settimer: zone authors.bind/CH: enter
26-Mar-2026 01:44:30.108 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
26-Mar-2026 01:44:30.108 zoneload: debug 1: zone version.bind/CH: starting load
26-Mar-2026 01:44:30.108 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
26-Mar-2026 01:44:30.108 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
26-Mar-2026 01:44:30.108 general: debug 1: zone__settimer: zone id.server/CH: enter
26-Mar-2026 01:44:30.108 general: debug 1: zone_maintenance: zone id.server/CH: enter
26-Mar-2026 01:44:30.108 general: debug 1: zone__settimer: zone id.server/CH: enter
26-Mar-2026 01:44:30.108 general: notice: all zones loaded
26-Mar-2026 01:44:30.108 general: debug 1: managed-keys-zone: synchronizing trusted keys
26-Mar-2026 01:44:30.108 general: debug 1: create_keydata: managed-keys-zone: enter
26-Mar-2026 01:44:30.108 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
26-Mar-2026 01:44:30.108 general: debug 1: managed-keys-zone: next key refresh: 26-Mar-2026 01:44:30.108
26-Mar-2026 01:44:30.108 general: debug 1: zone_journal: managed-keys-zone: enter
26-Mar-2026 01:44:30.108 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
26-Mar-2026 01:44:30.108 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Mar-2026 01:44:30.108 general: debug 1: zone__settimer: zone authors.bind/CH: enter
26-Mar-2026 01:44:30.108 general: debug 1: loop exclusive mode: ended
26-Mar-2026 01:44:30.118 general: debug 1: zone_needdump: managed-keys-zone: enter
26-Mar-2026 01:44:30.118 general: notice: FIPS mode is disabled
26-Mar-2026 01:44:30.118 general: notice: running
26-Mar-2026 01:44:30.118 general: debug 1: debug: t1-cloud-fixed version
26-Mar-2026 01:44:30.118 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
26-Mar-2026 01:44:30.118 general: debug 1: zone__settimer: zone version.bind/CH: enter
26-Mar-2026 01:44:30.118 general: debug 1: zone__settimer: zone version.bind/CH: enter
26-Mar-2026 01:44:30.118 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
26-Mar-2026 01:44:30.118 general: debug 1: zone_maintenance: zone version.bind/CH: enter
26-Mar-2026 01:44:30.118 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
26-Mar-2026 01:44:30.118 general: debug 1: zone__settimer: zone version.bind/CH: enter
26-Mar-2026 01:44:30.118 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
26-Mar-2026 01:44:30.118 general: debug 1: zone_maintenance: managed-keys-zone: enter
26-Mar-2026 01:44:30.118 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
26-Mar-2026 01:44:30.118 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
26-Mar-2026 01:44:30.118 general: debug 1: managed-keys-zone: next key refresh: 26-Mar-2026 01:44:30.118
26-Mar-2026 01:44:30.118 general: debug 1: zone__settimer: zone authors.bind/CH: enter
26-Mar-2026 01:44:30.118 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Mar-2026 01:44:30.118 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Mar-2026 01:44:30.118 general: debug 1: zone__settimer: zone id.server/CH: enter
26-Mar-2026 01:44:30.118 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Mar-2026 01:44:30.118 resolver: debug 1: fetch: ./DNSKEY
26-Mar-2026 01:44:30.118 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Mar-2026 01:44:30.118 resolver: debug 1: fetch: ./NS
26-Mar-2026 01:44:30.118 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
26-Mar-2026 01:44:30.119 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
26-Mar-2026 01:44:30.122 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
26-Mar-2026 01:44:30.122 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
26-Mar-2026 01:44:30.123 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
26-Mar-2026 01:44:30.123 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
26-Mar-2026 01:44:30.123 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
26-Mar-2026 01:44:30.123 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
26-Mar-2026 01:44:30.123 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
26-Mar-2026 01:44:30.123 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
26-Mar-2026 01:44:30.123 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
26-Mar-2026 01:44:30.125 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
26-Mar-2026 01:44:30.125 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
26-Mar-2026 01:44:30.125 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
26-Mar-2026 01:44:30.125 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
26-Mar-2026 01:44:30.125 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
26-Mar-2026 01:44:30.125 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
26-Mar-2026 01:44:30.125 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
26-Mar-2026 01:44:30.125 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
26-Mar-2026 01:44:30.125 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
26-Mar-2026 01:44:30.125 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
26-Mar-2026 01:44:30.125 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
26-Mar-2026 01:44:30.125 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
26-Mar-2026 01:44:30.125 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
26-Mar-2026 01:44:30.125 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
26-Mar-2026 01:44:30.145 lame-servers: info: SERVFAIL unexpected RCODE resolving './NS/IN': 192.36.148.17#53
26-Mar-2026 01:44:30.145 lame-servers: info: SERVFAIL unexpected RCODE resolving './DNSKEY/IN': 192.36.148.17#53
26-Mar-2026 01:44:30.220 database: debug 1: delete_node(): 0xfeecb0 . (bucket 3)
26-Mar-2026 01:44:30.220 resolver: debug 1: fetch: ./DNSKEY
26-Mar-2026 01:44:30.220 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
26-Mar-2026 01:44:30.220 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
26-Mar-2026 01:44:30.318 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-Mar-2026 01:44:30.318 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
26-Mar-2026 01:44:30.318 general: debug 1: managed-keys-zone: next key refresh: 27-Mar-2026 01:44:30.318
26-Mar-2026 01:44:30.318 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-Mar-2026 01:44:30.318 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
26-Mar-2026 01:44:30.318 general: debug 1: managed-keys-zone: next key refresh: 27-Mar-2026 01:44:30.318
26-Mar-2026 01:44:30.318 general: debug 1: zone_journal: managed-keys-zone: enter
26-Mar-2026 01:44:30.391 general: debug 1: zone_needdump: managed-keys-zone: enter
26-Mar-2026 01:44:30.391 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Mar-2026 01:44:30.391 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Mar-2026 01:44:30.391 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Mar-2026 01:44:30.391 resolver: debug 1: resolver priming query complete: success
26-Mar-2026 01:44:56.143 general: debug 1: zone_maintenance: managed-keys-zone: enter
26-Mar-2026 01:44:56.143 general: debug 1: zone_dump: managed-keys-zone: enter
26-Mar-2026 01:44:56.148 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Mar-2026 01:44:56.167 general: debug 1: dump_done: managed-keys-zone: enter
26-Mar-2026 01:44:56.167 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
26-Mar-2026 01:45:21.933 network: info: listening on IPv6 interface tapeth0-13788c, fe80::6428:2fff:fe8c:fdd%11#53
26-Mar-2026 01:45:21.934 network: info: listening on IPv6 interface tapeth0-462c9f, fe80::ec09:f4ff:fe81:befb%13#53
26-Mar-2026 01:46:49.458 network: info: listening on IPv4 interface kube-ipvs0, 10.106.241.240#53
26-Mar-2026 01:46:56.909 network: info: listening on IPv6 interface tapeth0-91f2e2, fe80::9063:9dff:fea5:8ebd%15#53
26-Mar-2026 01:46:57.006 network: info: listening on IPv6 interface tapeth0-3a3509, fe80::5451:aaff:fe41:36e2%17#53
26-Mar-2026 01:47:01.070 network: info: listening on IPv6 interface veth4ecb389a-f, fe80::c86b:caff:fe9e:5ff%18#53
26-Mar-2026 01:47:08.173 network: info: listening on IPv6 interface tapeth0-330704, fe80::9c8c:6bff:fe93:1f32%20#53
26-Mar-2026 01:47:49.973 network: info: no longer listening on fe80::9c8c:6bff:fe93:1f32%20#53
26-Mar-2026 01:47:56.765 network: info: no longer listening on fe80::c86b:caff:fe9e:5ff%18#53
26-Mar-2026 01:47:57.515 network: info: no longer listening on fe80::9063:9dff:fea5:8ebd%15#53
26-Mar-2026 01:48:02.337 network: info: no longer listening on fe80::5451:aaff:fe41:36e2%17#53
26-Mar-2026 01:48:22.093 network: info: listening on IPv6 interface tapeth0-144d51, fe80::d402:7ff:fe39:5f69%22#53
26-Mar-2026 01:48:22.095 network: info: listening on IPv6 interface tapeth0-360749, fe80::8bb:98ff:fe75:8158%24#53
26-Mar-2026 01:48:22.096 network: info: listening on IPv6 interface tapeth0-275132, fe80::f8a3:e2ff:fecf:8ec8%26#53
26-Mar-2026 01:48:27.085 network: info: listening on IPv6 interface tapeth0-bbd8b3, fe80::9cbf:3eff:fefb:69cf%28#53
26-Mar-2026 01:48:27.086 network: info: listening on IPv6 interface tapeth0-542bf3, fe80::d4f7:64ff:fe42:53b1%30#53
26-Mar-2026 01:48:27.087 network: info: listening on IPv6 interface tapeth0-16ee75, fe80::28f7:e2ff:fe0a:6d62%32#53
26-Mar-2026 01:48:27.088 network: info: listening on IPv6 interface tapeth0-458e4a, fe80::ec93:3ff:fe05:47ca%34#53
26-Mar-2026 01:48:32.589 network: info: listening on IPv6 interface tapeth0-6df4c9, fe80::80c4:6fff:fe55:60ba%36#53
26-Mar-2026 01:48:41.324 network: info: listening on IPv4 interface kube-ipvs0, 10.100.245.24#53
26-Mar-2026 01:51:49.783 network: info: no longer listening on fe80::8bb:98ff:fe75:8158%24#53
26-Mar-2026 01:51:49.793 network: info: no longer listening on fe80::d402:7ff:fe39:5f69%22#53
26-Mar-2026 01:51:49.808 network: info: no longer listening on fe80::f8a3:e2ff:fecf:8ec8%26#53
26-Mar-2026 01:51:49.823 network: info: no longer listening on fe80::ec93:3ff:fe05:47ca%34#53
26-Mar-2026 01:52:20.215 network: info: no longer listening on fe80::9cbf:3eff:fefb:69cf%28#53
26-Mar-2026 01:52:20.240 network: info: no longer listening on fe80::80c4:6fff:fe55:60ba%36#53
26-Mar-2026 01:52:20.250 network: info: no longer listening on fe80::d4f7:64ff:fe42:53b1%30#53
26-Mar-2026 01:52:20.259 network: info: no longer listening on fe80::28f7:e2ff:fe0a:6d62%32#53
26-Mar-2026 01:52:35.764 network: info: no longer listening on 10.100.245.24#53