16-Apr-2026 01:38:46.976 general: debug 1: now using logging configuration from config file
16-Apr-2026 01:38:46.988 general: debug 1: loop exclusive mode: ending
16-Apr-2026 01:38:46.988 general: debug 1: loop exclusive mode: ended
16-Apr-2026 01:38:46.988 general: notice: command channel listening on 127.0.0.1#8094
16-Apr-2026 01:38:46.988 general: info: VDNS cleanup pass1: 0 departing views cleared
16-Apr-2026 01:38:46.988 general: info: VDNS cleanup pass2: 2 staying views re-checked
16-Apr-2026 01:38:46.988 general: debug 1: load_configuration: success
16-Apr-2026 01:38:46.988 general: debug 1: loop exclusive mode: starting
16-Apr-2026 01:38:47.087 general: debug 1: loop exclusive mode: started
16-Apr-2026 01:38:47.087 zoneload: debug 1: managed-keys-zone: starting load
16-Apr-2026 01:38:47.087 general: debug 1: zone_startload: managed-keys-zone: enter
16-Apr-2026 01:38:47.087 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
16-Apr-2026 01:38:47.087 general: debug 1: managed-keys-zone: creating SOA
16-Apr-2026 01:38:47.087 zoneload: debug 1: managed-keys-zone: loaded; checking validity
16-Apr-2026 01:38:47.087 zoneload: info: managed-keys-zone: loaded serial 0
16-Apr-2026 01:38:47.087 general: debug 1: loop exclusive mode: ending
16-Apr-2026 01:38:47.087 zoneload: debug 1: zone hostname.bind/CH: starting load
16-Apr-2026 01:38:47.087 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
16-Apr-2026 01:38:47.087 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
16-Apr-2026 01:38:47.087 zoneload: debug 1: zone id.server/CH: starting load
16-Apr-2026 01:38:47.087 zoneload: debug 1: zone id.server/CH: loaded; checking validity
16-Apr-2026 01:38:47.087 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
16-Apr-2026 01:38:47.087 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
16-Apr-2026 01:38:47.087 general: debug 1: zone__settimer: zone id.server/CH: enter
16-Apr-2026 01:38:47.087 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
16-Apr-2026 01:38:47.087 general: debug 1: zone_maintenance: zone id.server/CH: enter
16-Apr-2026 01:38:47.087 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
16-Apr-2026 01:38:47.087 general: debug 1: zone__settimer: zone id.server/CH: enter
16-Apr-2026 01:38:47.087 zoneload: debug 1: zone authors.bind/CH: starting load
16-Apr-2026 01:38:47.087 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
16-Apr-2026 01:38:47.087 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
16-Apr-2026 01:38:47.087 zoneload: debug 1: zone version.bind/CH: starting load
16-Apr-2026 01:38:47.087 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
16-Apr-2026 01:38:47.087 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
16-Apr-2026 01:38:47.087 general: notice: all zones loaded
16-Apr-2026 01:38:47.087 general: debug 1: managed-keys-zone: synchronizing trusted keys
16-Apr-2026 01:38:47.087 general: debug 1: create_keydata: managed-keys-zone: enter
16-Apr-2026 01:38:47.087 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
16-Apr-2026 01:38:47.087 general: debug 1: managed-keys-zone: next key refresh: 16-Apr-2026 01:38:47.087
16-Apr-2026 01:38:47.087 general: debug 1: zone_journal: managed-keys-zone: enter
16-Apr-2026 01:38:47.087 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
16-Apr-2026 01:38:47.088 general: debug 1: loop exclusive mode: ended
16-Apr-2026 01:38:47.088 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Apr-2026 01:38:47.095 general: debug 1: zone_needdump: managed-keys-zone: enter
16-Apr-2026 01:38:47.095 general: notice: FIPS mode is disabled
16-Apr-2026 01:38:47.095 general: notice: running
16-Apr-2026 01:38:47.095 general: debug 1: debug: t1-cloud-fixed version
16-Apr-2026 01:38:47.095 general: debug 1: zone__settimer: zone authors.bind/CH: enter
16-Apr-2026 01:38:47.095 general: debug 1: zone__settimer: zone version.bind/CH: enter
16-Apr-2026 01:38:47.095 general: debug 1: zone__settimer: zone version.bind/CH: enter
16-Apr-2026 01:38:47.095 general: debug 1: zone__settimer: zone authors.bind/CH: enter
16-Apr-2026 01:38:47.095 general: debug 1: zone_maintenance: zone version.bind/CH: enter
16-Apr-2026 01:38:47.095 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
16-Apr-2026 01:38:47.095 general: debug 1: zone__settimer: zone version.bind/CH: enter
16-Apr-2026 01:38:47.095 general: debug 1: zone__settimer: zone authors.bind/CH: enter
16-Apr-2026 01:38:47.095 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
16-Apr-2026 01:38:47.095 general: debug 1: zone__settimer: zone id.server/CH: enter
16-Apr-2026 01:38:47.095 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Apr-2026 01:38:47.095 general: debug 1: zone_maintenance: managed-keys-zone: enter
16-Apr-2026 01:38:47.095 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
16-Apr-2026 01:38:47.095 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
16-Apr-2026 01:38:47.095 general: debug 1: managed-keys-zone: next key refresh: 16-Apr-2026 01:38:47.095
16-Apr-2026 01:38:47.095 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Apr-2026 01:38:47.095 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Apr-2026 01:38:47.095 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Apr-2026 01:38:47.095 resolver: debug 1: fetch: ./DNSKEY
16-Apr-2026 01:38:47.095 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Apr-2026 01:38:47.095 resolver: debug 1: fetch: ./NS
16-Apr-2026 01:38:47.095 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
16-Apr-2026 01:38:47.096 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
16-Apr-2026 01:38:47.161 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-Apr-2026 01:38:47.161 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
16-Apr-2026 01:38:47.161 general: debug 1: managed-keys-zone: next key refresh: 17-Apr-2026 01:38:47.161
16-Apr-2026 01:38:47.161 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-Apr-2026 01:38:47.161 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
16-Apr-2026 01:38:47.161 general: debug 1: managed-keys-zone: next key refresh: 17-Apr-2026 01:38:47.161
16-Apr-2026 01:38:47.161 general: debug 1: zone_journal: managed-keys-zone: enter
16-Apr-2026 01:38:47.222 general: debug 1: zone_needdump: managed-keys-zone: enter
16-Apr-2026 01:38:47.222 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Apr-2026 01:38:47.222 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Apr-2026 01:38:47.222 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Apr-2026 01:38:47.273 resolver: debug 1: resolver priming query complete: success
16-Apr-2026 01:39:12.246 general: debug 1: zone_maintenance: managed-keys-zone: enter
16-Apr-2026 01:39:12.246 general: debug 1: zone_dump: managed-keys-zone: enter
16-Apr-2026 01:39:12.251 general: debug 1: zone__settimer: managed-keys-zone: enter
16-Apr-2026 01:39:12.256 general: debug 1: dump_done: managed-keys-zone: enter
16-Apr-2026 01:39:12.256 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
16-Apr-2026 01:39:35.331 network: info: listening on IPv6 interface tapeth0-22cf83, fe80::b431:d9ff:fe0f:c76f%11#53
16-Apr-2026 01:39:39.810 network: info: listening on IPv6 interface tapeth0-7480b6, fe80::8014:7aff:fee7:ab02%13#53
16-Apr-2026 01:41:13.312 network: info: listening on IPv4 interface kube-ipvs0, 10.100.87.224#53
16-Apr-2026 01:41:21.123 network: info: listening on IPv6 interface tapeth0-3c3cce, fe80::643a:a3ff:fe29:ec6e%15#53
16-Apr-2026 01:41:21.135 network: info: listening on IPv6 interface tapeth0-02e8f5, fe80::2838:31ff:fe76:1b4e%17#53
16-Apr-2026 01:41:26.253 network: info: listening on IPv6 interface vetheff91cd9-d, fe80::8836:7bff:fe7e:43eb%18#53
16-Apr-2026 01:41:31.425 network: info: listening on IPv6 interface tapeth0-919600, fe80::b8a7:3bff:fe24:21d%20#53
16-Apr-2026 01:42:09.181 network: info: no longer listening on fe80::b8a7:3bff:fe24:21d%20#53
16-Apr-2026 01:42:15.638 network: info: no longer listening on fe80::8836:7bff:fe7e:43eb%18#53
16-Apr-2026 01:42:16.760 network: info: no longer listening on fe80::643a:a3ff:fe29:ec6e%15#53
16-Apr-2026 01:42:21.769 network: info: no longer listening on fe80::2838:31ff:fe76:1b4e%17#53
16-Apr-2026 01:42:41.891 network: info: listening on IPv6 interface tapeth0-5cd749, fe80::182c:4dff:fe50:b277%22#53
16-Apr-2026 01:42:41.895 network: info: listening on IPv6 interface tapeth0-0b15a5, fe80::1406:b2ff:fe1d:d428%24#53
16-Apr-2026 01:42:41.896 network: info: listening on IPv6 interface tapeth0-2e0346, fe80::8cd:59ff:fee6:85bc%26#53
16-Apr-2026 01:42:46.947 network: info: listening on IPv6 interface tapeth0-5ac02c, fe80::3064:cdff:fe20:422b%28#53
16-Apr-2026 01:42:46.953 network: info: listening on IPv6 interface tapeth0-2aaec9, fe80::c01d:bdff:fe9a:d082%30#53
16-Apr-2026 01:42:46.953 network: info: listening on IPv6 interface tapeth0-d24687, fe80::d834:dcff:feb7:6824%32#53
16-Apr-2026 01:42:52.001 network: info: listening on IPv6 interface tapeth0-728043, fe80::ec02:b8ff:fe65:425a%34#53
16-Apr-2026 01:42:52.004 network: info: listening on IPv6 interface tapeth0-501988, fe80::ac14:d1ff:fe7f:63a7%36#53
16-Apr-2026 01:43:01.556 network: info: listening on IPv4 interface kube-ipvs0, 10.109.255.230#53
16-Apr-2026 01:46:12.930 network: info: no longer listening on fe80::8cd:59ff:fee6:85bc%26#53
16-Apr-2026 01:46:12.932 network: info: no longer listening on fe80::c01d:bdff:fe9a:d082%30#53
16-Apr-2026 01:46:12.948 network: info: no longer listening on fe80::182c:4dff:fe50:b277%22#53
16-Apr-2026 01:46:12.960 network: info: no longer listening on fe80::1406:b2ff:fe1d:d428%24#53
16-Apr-2026 01:46:42.602 network: info: no longer listening on fe80::ac14:d1ff:fe7f:63a7%36#53
16-Apr-2026 01:46:42.629 network: info: no longer listening on fe80::ec02:b8ff:fe65:425a%34#53
16-Apr-2026 01:46:42.640 network: info: no longer listening on fe80::d834:dcff:feb7:6824%32#53
16-Apr-2026 01:46:42.656 network: info: no longer listening on fe80::3064:cdff:fe20:422b%28#53
16-Apr-2026 01:46:58.311 network: info: no longer listening on 10.109.255.230#53