30-Apr-2026 01:58:24.009 general: debug 1: now using logging configuration from config file
30-Apr-2026 01:58:24.009 general: debug 1: loop exclusive mode: ending
30-Apr-2026 01:58:24.009 general: debug 1: loop exclusive mode: ended
30-Apr-2026 01:58:24.009 general: notice: command channel listening on 127.0.0.1#8094
30-Apr-2026 01:58:24.009 general: info: VDNS cleanup pass1: 0 departing views cleared
30-Apr-2026 01:58:24.009 general: info: VDNS cleanup pass2: 2 staying views re-checked
30-Apr-2026 01:58:24.009 general: debug 1: load_configuration: success
30-Apr-2026 01:58:24.009 general: debug 1: loop exclusive mode: starting
30-Apr-2026 01:58:24.014 general: debug 1: loop exclusive mode: started
30-Apr-2026 01:58:24.014 zoneload: debug 1: managed-keys-zone: starting load
30-Apr-2026 01:58:24.014 general: debug 1: zone_startload: managed-keys-zone: enter
30-Apr-2026 01:58:24.014 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
30-Apr-2026 01:58:24.014 general: debug 1: managed-keys-zone: creating SOA
30-Apr-2026 01:58:24.014 zoneload: debug 1: managed-keys-zone: loaded; checking validity
30-Apr-2026 01:58:24.015 zoneload: info: managed-keys-zone: loaded serial 0
30-Apr-2026 01:58:24.015 general: debug 1: loop exclusive mode: ending
30-Apr-2026 01:58:24.015 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 01:58:24.015 zoneload: debug 1: zone authors.bind/CH: starting load
30-Apr-2026 01:58:24.015 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
30-Apr-2026 01:58:24.015 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
30-Apr-2026 01:58:24.015 zoneload: debug 1: zone version.bind/CH: starting load
30-Apr-2026 01:58:24.015 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
30-Apr-2026 01:58:24.015 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
30-Apr-2026 01:58:24.015 general: debug 1: zone__settimer: zone authors.bind/CH: enter
30-Apr-2026 01:58:24.015 general: debug 1: zone__settimer: zone version.bind/CH: enter
30-Apr-2026 01:58:24.015 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
30-Apr-2026 01:58:24.015 general: debug 1: zone_maintenance: zone version.bind/CH: enter
30-Apr-2026 01:58:24.015 general: debug 1: zone__settimer: zone authors.bind/CH: enter
30-Apr-2026 01:58:24.015 general: debug 1: zone__settimer: zone version.bind/CH: enter
30-Apr-2026 01:58:24.015 general: debug 1: loop exclusive mode: ended
30-Apr-2026 01:58:24.015 zoneload: debug 1: zone hostname.bind/CH: starting load
30-Apr-2026 01:58:24.015 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
30-Apr-2026 01:58:24.015 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
30-Apr-2026 01:58:24.015 zoneload: debug 1: zone id.server/CH: starting load
30-Apr-2026 01:58:24.015 zoneload: debug 1: zone id.server/CH: loaded; checking validity
30-Apr-2026 01:58:24.015 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
30-Apr-2026 01:58:24.015 general: notice: all zones loaded
30-Apr-2026 01:58:24.015 general: debug 1: managed-keys-zone: synchronizing trusted keys
30-Apr-2026 01:58:24.015 general: debug 1: create_keydata: managed-keys-zone: enter
30-Apr-2026 01:58:24.015 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
30-Apr-2026 01:58:24.015 general: debug 1: managed-keys-zone: next key refresh: 30-Apr-2026 01:58:24.015
30-Apr-2026 01:58:24.020 general: debug 1: zone_journal: managed-keys-zone: enter
30-Apr-2026 01:58:24.021 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
30-Apr-2026 01:58:24.021 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 01:58:24.035 general: debug 1: zone_needdump: managed-keys-zone: enter
30-Apr-2026 01:58:24.035 general: debug 1: zone_maintenance: managed-keys-zone: enter
30-Apr-2026 01:58:24.035 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
30-Apr-2026 01:58:24.035 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
30-Apr-2026 01:58:24.035 general: debug 1: managed-keys-zone: next key refresh: 30-Apr-2026 01:58:24.035
30-Apr-2026 01:58:24.035 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 01:58:24.035 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 01:58:24.035 resolver: debug 1: fetch: ./DNSKEY
30-Apr-2026 01:58:24.035 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 01:58:24.035 resolver: debug 1: fetch: ./NS
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
30-Apr-2026 01:58:24.036 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
30-Apr-2026 01:58:24.038 general: notice: FIPS mode is disabled
30-Apr-2026 01:58:24.038 general: notice: running
30-Apr-2026 01:58:24.038 general: debug 1: debug: t1-cloud-fixed version
30-Apr-2026 01:58:24.038 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
30-Apr-2026 01:58:24.038 general: debug 1: zone__settimer: zone id.server/CH: enter
30-Apr-2026 01:58:24.038 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
30-Apr-2026 01:58:24.038 general: debug 1: zone__settimer: zone id.server/CH: enter
30-Apr-2026 01:58:24.038 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
30-Apr-2026 01:58:24.038 general: debug 1: zone_maintenance: zone id.server/CH: enter
30-Apr-2026 01:58:24.038 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
30-Apr-2026 01:58:24.038 general: debug 1: zone__settimer: zone id.server/CH: enter
30-Apr-2026 01:58:24.038 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 01:58:24.038 general: debug 1: zone__settimer: zone version.bind/CH: enter
30-Apr-2026 01:58:24.038 general: debug 1: zone__settimer: zone authors.bind/CH: enter
30-Apr-2026 01:58:24.085 database: debug 1: delete_node(): 0x7f71cc002220 . (bucket 3)
30-Apr-2026 01:58:24.085 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.
30-Apr-2026 01:58:24.085 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
30-Apr-2026 01:58:24.085 general: debug 1: managed-keys-zone: next key refresh: 01-May-2026 01:58:24.085
30-Apr-2026 01:58:24.085 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.
30-Apr-2026 01:58:24.085 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
30-Apr-2026 01:58:24.085 general: debug 1: managed-keys-zone: next key refresh: 01-May-2026 01:58:24.085
30-Apr-2026 01:58:24.085 general: debug 1: zone_journal: managed-keys-zone: enter
30-Apr-2026 01:58:24.098 general: debug 1: zone_needdump: managed-keys-zone: enter
30-Apr-2026 01:58:24.099 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 01:58:24.099 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 01:58:24.099 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 01:58:24.100 resolver: debug 1: resolver priming query complete: success
30-Apr-2026 01:58:51.127 general: debug 1: zone_maintenance: managed-keys-zone: enter
30-Apr-2026 01:58:51.127 general: debug 1: zone_dump: managed-keys-zone: enter
30-Apr-2026 01:58:51.133 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Apr-2026 01:58:51.146 general: debug 1: dump_done: managed-keys-zone: enter
30-Apr-2026 01:58:51.146 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
30-Apr-2026 01:59:28.501 network: info: listening on IPv6 interface tapeth0-130156, fe80::b7:b7ff:fedb:e1c1%11#53
30-Apr-2026 01:59:28.502 network: info: listening on IPv6 interface tapeth0-ec7098, fe80::1cc7:caff:fed0:5bfd%13#53
30-Apr-2026 02:01:06.194 network: info: listening on IPv4 interface kube-ipvs0, 10.100.156.186#53
30-Apr-2026 02:01:14.036 network: info: listening on IPv6 interface tapeth0-c76150, fe80::dcf8:28ff:fe73:e09b%15#53
30-Apr-2026 02:01:14.054 network: info: listening on IPv6 interface tapeth0-e41e55, fe80::b481:dcff:fe97:1488%17#53
30-Apr-2026 02:01:18.964 network: info: listening on IPv6 interface veth8985aacf-7, fe80::1c03:79ff:feb1:5ac7%18#53
30-Apr-2026 02:01:24.538 network: info: listening on IPv6 interface tapeth0-d850e5, fe80::2c25:1bff:fe83:6594%20#53
30-Apr-2026 02:02:07.209 network: info: no longer listening on fe80::2c25:1bff:fe83:6594%20#53
30-Apr-2026 02:02:14.297 network: info: no longer listening on fe80::1c03:79ff:feb1:5ac7%18#53
30-Apr-2026 02:02:15.063 network: info: no longer listening on fe80::b481:dcff:fe97:1488%17#53
30-Apr-2026 02:02:20.246 network: info: no longer listening on fe80::dcf8:28ff:fe73:e09b%15#53
30-Apr-2026 02:02:40.629 network: info: listening on IPv6 interface tapeth0-5f6323, fe80::2047:94ff:fe09:8230%22#53
30-Apr-2026 02:02:40.662 network: info: listening on IPv6 interface tapeth0-5c9dad, fe80::7c65:feff:fe20:afa7%24#53
30-Apr-2026 02:02:40.665 network: info: listening on IPv6 interface tapeth0-dfd6f2, fe80::44d1:9dff:fe89:b7e6%26#53
30-Apr-2026 02:02:45.236 network: info: listening on IPv6 interface tapeth0-3d40d4, fe80::3ce8:3bff:fea1:3183%28#53
30-Apr-2026 02:02:45.238 network: info: listening on IPv6 interface tapeth0-6f32d8, fe80::106a:14ff:fe25:5227%30#53
30-Apr-2026 02:02:45.240 network: info: listening on IPv6 interface tapeth0-f5373b, fe80::68e4:cff:fec6:ab2d%32#53
30-Apr-2026 02:02:49.909 network: info: listening on IPv6 interface tapeth0-628534, fe80::3044:5dff:fe8e:452e%34#53
30-Apr-2026 02:02:49.913 network: info: listening on IPv6 interface tapeth0-0d1bf5, fe80::84db:ebff:fea3:17%36#53
30-Apr-2026 02:03:00.878 network: info: listening on IPv4 interface kube-ipvs0, 10.108.107.245#53
30-Apr-2026 02:06:11.347 network: info: no longer listening on fe80::7c65:feff:fe20:afa7%24#53
30-Apr-2026 02:06:11.355 network: info: no longer listening on fe80::44d1:9dff:fe89:b7e6%26#53
30-Apr-2026 02:06:11.360 network: info: no longer listening on fe80::3ce8:3bff:fea1:3183%28#53
30-Apr-2026 02:06:11.371 network: info: no longer listening on fe80::2047:94ff:fe09:8230%22#53
30-Apr-2026 02:06:40.762 network: info: no longer listening on fe80::68e4:cff:fec6:ab2d%32#53
30-Apr-2026 02:06:40.802 network: info: no longer listening on fe80::106a:14ff:fe25:5227%30#53
30-Apr-2026 02:06:40.803 network: info: no longer listening on fe80::84db:ebff:fea3:17%36#53
30-Apr-2026 02:06:40.813 network: info: no longer listening on fe80::3044:5dff:fe8e:452e%34#53
30-Apr-2026 02:06:56.893 network: info: no longer listening on 10.108.107.245#53