27-Apr-2026 01:58:09.855 general: debug 1: now using logging configuration from config file
27-Apr-2026 01:58:09.855 general: debug 1: loop exclusive mode: ending
27-Apr-2026 01:58:09.855 general: debug 1: loop exclusive mode: ended
27-Apr-2026 01:58:09.856 general: notice: command channel listening on 127.0.0.1#8094
27-Apr-2026 01:58:09.856 general: info: VDNS cleanup pass1: 0 departing views cleared
27-Apr-2026 01:58:09.856 general: info: VDNS cleanup pass2: 2 staying views re-checked
27-Apr-2026 01:58:09.856 general: debug 1: load_configuration: success
27-Apr-2026 01:58:09.856 general: debug 1: loop exclusive mode: starting
27-Apr-2026 01:58:09.861 general: debug 1: loop exclusive mode: started
27-Apr-2026 01:58:09.861 zoneload: debug 1: managed-keys-zone: starting load
27-Apr-2026 01:58:09.861 general: debug 1: zone_startload: managed-keys-zone: enter
27-Apr-2026 01:58:09.861 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
27-Apr-2026 01:58:09.861 general: debug 1: managed-keys-zone: creating SOA
27-Apr-2026 01:58:09.862 zoneload: debug 1: managed-keys-zone: loaded; checking validity
27-Apr-2026 01:58:09.862 zoneload: info: managed-keys-zone: loaded serial 0
27-Apr-2026 01:58:09.862 general: debug 1: loop exclusive mode: ending
27-Apr-2026 01:58:09.862 general: debug 1: loop exclusive mode: ended
27-Apr-2026 01:58:09.862 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Apr-2026 01:58:09.862 zoneload: debug 1: zone authors.bind/CH: starting load
27-Apr-2026 01:58:09.862 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
27-Apr-2026 01:58:09.862 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
27-Apr-2026 01:58:09.862 general: debug 1: zone__settimer: zone authors.bind/CH: enter
27-Apr-2026 01:58:09.862 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
27-Apr-2026 01:58:09.862 general: debug 1: zone__settimer: zone authors.bind/CH: enter
27-Apr-2026 01:58:09.862 zoneload: debug 1: zone hostname.bind/CH: starting load
27-Apr-2026 01:58:09.862 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
27-Apr-2026 01:58:09.862 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
27-Apr-2026 01:58:09.862 zoneload: debug 1: zone id.server/CH: starting load
27-Apr-2026 01:58:09.862 zoneload: debug 1: zone id.server/CH: loaded; checking validity
27-Apr-2026 01:58:09.862 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
27-Apr-2026 01:58:09.862 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
27-Apr-2026 01:58:09.862 general: debug 1: zone__settimer: zone id.server/CH: enter
27-Apr-2026 01:58:09.862 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
27-Apr-2026 01:58:09.862 general: debug 1: zone_maintenance: zone id.server/CH: enter
27-Apr-2026 01:58:09.862 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
27-Apr-2026 01:58:09.862 general: debug 1: zone__settimer: zone id.server/CH: enter
27-Apr-2026 01:58:09.862 zoneload: debug 1: zone version.bind/CH: starting load
27-Apr-2026 01:58:09.862 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
27-Apr-2026 01:58:09.862 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
27-Apr-2026 01:58:09.862 general: notice: all zones loaded
27-Apr-2026 01:58:09.862 general: debug 1: managed-keys-zone: synchronizing trusted keys
27-Apr-2026 01:58:09.862 general: debug 1: create_keydata: managed-keys-zone: enter
27-Apr-2026 01:58:09.862 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
27-Apr-2026 01:58:09.862 general: debug 1: managed-keys-zone: next key refresh: 27-Apr-2026 01:58:09.862
27-Apr-2026 01:58:09.862 general: debug 1: zone_journal: managed-keys-zone: enter
27-Apr-2026 01:58:09.862 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
27-Apr-2026 01:58:09.863 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Apr-2026 01:58:09.957 general: debug 1: zone_needdump: managed-keys-zone: enter
27-Apr-2026 01:58:09.962 general: notice: FIPS mode is disabled
27-Apr-2026 01:58:09.962 general: notice: running
27-Apr-2026 01:58:09.962 general: debug 1: debug: t1-cloud-fixed version
27-Apr-2026 01:58:09.962 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
27-Apr-2026 01:58:09.962 general: debug 1: zone__settimer: zone id.server/CH: enter
27-Apr-2026 01:58:09.962 general: debug 1: zone__settimer: zone version.bind/CH: enter
27-Apr-2026 01:58:09.962 general: debug 1: zone__settimer: zone version.bind/CH: enter
27-Apr-2026 01:58:09.962 general: debug 1: zone_maintenance: zone version.bind/CH: enter
27-Apr-2026 01:58:09.962 general: debug 1: zone__settimer: zone version.bind/CH: enter
27-Apr-2026 01:58:09.962 general: debug 1: zone_maintenance: managed-keys-zone: enter
27-Apr-2026 01:58:09.962 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
27-Apr-2026 01:58:09.962 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
27-Apr-2026 01:58:09.962 general: debug 1: managed-keys-zone: next key refresh: 27-Apr-2026 01:58:09.962
27-Apr-2026 01:58:09.962 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Apr-2026 01:58:09.962 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Apr-2026 01:58:09.962 general: debug 1: zone__settimer: zone authors.bind/CH: enter
27-Apr-2026 01:58:09.962 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Apr-2026 01:58:09.962 resolver: debug 1: fetch: ./DNSKEY
27-Apr-2026 01:58:09.962 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Apr-2026 01:58:09.962 resolver: debug 1: fetch: ./NS
27-Apr-2026 01:58:09.963 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
27-Apr-2026 01:58:09.964 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
27-Apr-2026 01:58:09.965 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
27-Apr-2026 01:58:09.965 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
27-Apr-2026 01:58:09.965 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
27-Apr-2026 01:58:09.965 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
27-Apr-2026 01:58:09.965 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
27-Apr-2026 01:58:09.969 database: debug 1: delete_node(): 0x16ce1e0 . (bucket 3)
27-Apr-2026 01:58:09.969 resolver: debug 1: fetch: ./DNSKEY
27-Apr-2026 01:58:09.969 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
27-Apr-2026 01:58:09.969 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
27-Apr-2026 01:58:09.969 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
27-Apr-2026 01:58:09.972 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.
27-Apr-2026 01:58:09.972 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
27-Apr-2026 01:58:09.972 general: debug 1: managed-keys-zone: next key refresh: 28-Apr-2026 01:58:09.972
27-Apr-2026 01:58:09.972 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.
27-Apr-2026 01:58:09.972 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
27-Apr-2026 01:58:09.972 general: debug 1: managed-keys-zone: next key refresh: 28-Apr-2026 01:58:09.972
27-Apr-2026 01:58:09.972 general: debug 1: zone_journal: managed-keys-zone: enter
27-Apr-2026 01:58:09.989 general: debug 1: zone_needdump: managed-keys-zone: enter
27-Apr-2026 01:58:09.989 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Apr-2026 01:58:09.989 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Apr-2026 01:58:09.989 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Apr-2026 01:58:10.109 resolver: debug 1: resolver priming query complete: success
27-Apr-2026 01:58:37.985 general: debug 1: zone_maintenance: managed-keys-zone: enter
27-Apr-2026 01:58:37.985 general: debug 1: zone_dump: managed-keys-zone: enter
27-Apr-2026 01:58:37.988 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Apr-2026 01:58:37.993 general: debug 1: dump_done: managed-keys-zone: enter
27-Apr-2026 01:58:37.993 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
27-Apr-2026 01:58:57.517 network: info: listening on IPv6 interface tapeth0-8972ca, fe80::882e:20ff:fe7e:4577%11#53
27-Apr-2026 01:59:01.037 network: info: listening on IPv6 interface tapeth0-11cd09, fe80::a45b:4fff:fe85:9030%13#53
27-Apr-2026 02:00:25.023 network: info: listening on IPv4 interface kube-ipvs0, 10.111.38.36#53
27-Apr-2026 02:00:32.813 network: info: listening on IPv6 interface tapeth0-f5d069, fe80::cc9e:fbff:fe47:465c%15#53
27-Apr-2026 02:00:32.820 network: info: listening on IPv6 interface tapeth0-07a323, fe80::f85e:c1ff:fee0:90f0%17#53
27-Apr-2026 02:00:37.166 network: info: listening on IPv6 interface veth088a41b8-d, fe80::1457:5ff:fe4f:d1f4%18#53
27-Apr-2026 02:00:42.541 network: info: listening on IPv6 interface tapeth0-d75ab7, fe80::2811:c6ff:fe59:1250%20#53
27-Apr-2026 02:01:40.883 network: info: no longer listening on fe80::2811:c6ff:fe59:1250%20#53
27-Apr-2026 02:01:48.016 network: info: no longer listening on fe80::1457:5ff:fe4f:d1f4%18#53
27-Apr-2026 02:01:48.660 network: info: no longer listening on fe80::cc9e:fbff:fe47:465c%15#53
27-Apr-2026 02:01:53.558 network: info: no longer listening on fe80::f85e:c1ff:fee0:90f0%17#53
27-Apr-2026 02:02:14.767 network: info: listening on IPv6 interface tapeth0-877382, fe80::7023:38ff:fec4:bdf4%22#53
27-Apr-2026 02:02:14.771 network: info: listening on IPv6 interface tapeth0-29a613, fe80::d43c:77ff:fea5:f519%24#53
27-Apr-2026 02:02:19.565 network: info: listening on IPv6 interface tapeth0-1092b3, fe80::d458:d6ff:fe57:79a6%26#53
27-Apr-2026 02:02:19.566 network: info: listening on IPv6 interface tapeth0-fbe1b0, fe80::20b4:64ff:fe36:396%28#53
27-Apr-2026 02:02:19.567 network: info: listening on IPv6 interface tapeth0-a8f29e, fe80::886f:5eff:fe56:bc0%30#53
27-Apr-2026 02:02:24.814 network: info: listening on IPv6 interface tapeth0-cfcc0b, fe80::e42d:f4ff:fe20:6aca%32#53
27-Apr-2026 02:02:24.814 network: info: listening on IPv6 interface tapeth0-e406f9, fe80::2034:d5ff:fee6:76f4%34#53
27-Apr-2026 02:02:24.815 network: info: listening on IPv6 interface tapeth0-aa9726, fe80::f0a2:dbff:fe59:2746%36#53
27-Apr-2026 02:02:33.462 network: info: listening on IPv4 interface kube-ipvs0, 10.109.143.209#53
27-Apr-2026 02:05:42.624 network: info: no longer listening on fe80::7023:38ff:fec4:bdf4%22#53
27-Apr-2026 02:05:42.665 network: info: no longer listening on fe80::d43c:77ff:fea5:f519%24#53
27-Apr-2026 02:05:42.666 network: info: no longer listening on fe80::20b4:64ff:fe36:396%28#53
27-Apr-2026 02:05:42.690 network: info: no longer listening on fe80::d458:d6ff:fe57:79a6%26#53
27-Apr-2026 02:06:13.613 network: info: no longer listening on fe80::f0a2:dbff:fe59:2746%36#53
27-Apr-2026 02:06:13.658 network: info: no longer listening on fe80::886f:5eff:fe56:bc0%30#53
27-Apr-2026 02:06:13.659 network: info: no longer listening on fe80::e42d:f4ff:fe20:6aca%32#53
27-Apr-2026 02:06:13.672 network: info: no longer listening on fe80::2034:d5ff:fee6:76f4%34#53
27-Apr-2026 02:06:28.833 network: info: no longer listening on 10.109.143.209#53