20-Apr-2026 01:36:29.191 general: debug 1: now using logging configuration from config file
20-Apr-2026 01:36:29.191 general: debug 1: loop exclusive mode: ending
20-Apr-2026 01:36:29.192 general: debug 1: loop exclusive mode: ended
20-Apr-2026 01:36:29.192 general: notice: command channel listening on 127.0.0.1#8094
20-Apr-2026 01:36:29.192 general: info: VDNS cleanup pass1: 0 departing views cleared
20-Apr-2026 01:36:29.192 general: info: VDNS cleanup pass2: 2 staying views re-checked
20-Apr-2026 01:36:29.192 general: debug 1: load_configuration: success
20-Apr-2026 01:36:29.192 general: debug 1: loop exclusive mode: starting
20-Apr-2026 01:36:29.261 general: debug 1: loop exclusive mode: started
20-Apr-2026 01:36:29.261 zoneload: debug 1: managed-keys-zone: starting load
20-Apr-2026 01:36:29.261 general: debug 1: zone_startload: managed-keys-zone: enter
20-Apr-2026 01:36:29.261 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
20-Apr-2026 01:36:29.261 general: debug 1: managed-keys-zone: creating SOA
20-Apr-2026 01:36:29.261 zoneload: debug 1: managed-keys-zone: loaded; checking validity
20-Apr-2026 01:36:29.261 zoneload: info: managed-keys-zone: loaded serial 0
20-Apr-2026 01:36:29.261 general: debug 1: loop exclusive mode: ending
20-Apr-2026 01:36:29.261 zoneload: debug 1: zone authors.bind/CH: starting load
20-Apr-2026 01:36:29.261 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
20-Apr-2026 01:36:29.261 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
20-Apr-2026 01:36:29.261 general: debug 1: zone__settimer: zone authors.bind/CH: enter
20-Apr-2026 01:36:29.261 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
20-Apr-2026 01:36:29.261 general: debug 1: zone__settimer: zone authors.bind/CH: enter
20-Apr-2026 01:36:29.261 zoneload: debug 1: zone version.bind/CH: starting load
20-Apr-2026 01:36:29.261 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
20-Apr-2026 01:36:29.261 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
20-Apr-2026 01:36:29.261 general: debug 1: zone__settimer: zone version.bind/CH: enter
20-Apr-2026 01:36:29.261 general: debug 1: zone_maintenance: zone version.bind/CH: enter
20-Apr-2026 01:36:29.261 general: debug 1: zone__settimer: zone version.bind/CH: enter
20-Apr-2026 01:36:29.261 zoneload: debug 1: zone hostname.bind/CH: starting load
20-Apr-2026 01:36:29.261 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
20-Apr-2026 01:36:29.261 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
20-Apr-2026 01:36:29.261 zoneload: debug 1: zone id.server/CH: starting load
20-Apr-2026 01:36:29.261 zoneload: debug 1: zone id.server/CH: loaded; checking validity
20-Apr-2026 01:36:29.261 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
20-Apr-2026 01:36:29.261 general: notice: all zones loaded
20-Apr-2026 01:36:29.261 general: debug 1: managed-keys-zone: synchronizing trusted keys
20-Apr-2026 01:36:29.261 general: debug 1: create_keydata: managed-keys-zone: enter
20-Apr-2026 01:36:29.261 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
20-Apr-2026 01:36:29.261 general: debug 1: managed-keys-zone: next key refresh: 20-Apr-2026 01:36:29.261
20-Apr-2026 01:36:29.261 general: debug 1: zone_journal: managed-keys-zone: enter
20-Apr-2026 01:36:29.261 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
20-Apr-2026 01:36:29.261 general: debug 1: loop exclusive mode: ended
20-Apr-2026 01:36:29.262 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 01:36:29.275 general: debug 1: zone_needdump: managed-keys-zone: enter
20-Apr-2026 01:36:29.275 general: notice: FIPS mode is disabled
20-Apr-2026 01:36:29.275 general: notice: running
20-Apr-2026 01:36:29.275 general: debug 1: debug: t1-cloud-fixed version
20-Apr-2026 01:36:29.275 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
20-Apr-2026 01:36:29.275 general: debug 1: zone__settimer: zone id.server/CH: enter
20-Apr-2026 01:36:29.275 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
20-Apr-2026 01:36:29.275 general: debug 1: zone__settimer: zone id.server/CH: enter
20-Apr-2026 01:36:29.275 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
20-Apr-2026 01:36:29.275 general: debug 1: zone_maintenance: zone id.server/CH: enter
20-Apr-2026 01:36:29.275 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
20-Apr-2026 01:36:29.275 general: debug 1: zone__settimer: zone id.server/CH: enter
20-Apr-2026 01:36:29.275 general: debug 1: zone__settimer: zone version.bind/CH: enter
20-Apr-2026 01:36:29.275 general: debug 1: zone__settimer: zone authors.bind/CH: enter
20-Apr-2026 01:36:29.275 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 01:36:29.275 general: debug 1: zone_maintenance: managed-keys-zone: enter
20-Apr-2026 01:36:29.275 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
20-Apr-2026 01:36:29.275 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
20-Apr-2026 01:36:29.275 general: debug 1: managed-keys-zone: next key refresh: 20-Apr-2026 01:36:29.275
20-Apr-2026 01:36:29.275 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 01:36:29.275 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 01:36:29.275 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 01:36:29.275 resolver: debug 1: fetch: ./DNSKEY
20-Apr-2026 01:36:29.275 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 01:36:29.275 resolver: debug 1: fetch: ./NS
20-Apr-2026 01:36:29.275 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
20-Apr-2026 01:36:29.276 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
20-Apr-2026 01:36:29.319 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.
20-Apr-2026 01:36:29.319 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
20-Apr-2026 01:36:29.319 general: debug 1: managed-keys-zone: next key refresh: 21-Apr-2026 01:36:29.319
20-Apr-2026 01:36:29.319 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.
20-Apr-2026 01:36:29.319 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
20-Apr-2026 01:36:29.319 general: debug 1: managed-keys-zone: next key refresh: 21-Apr-2026 01:36:29.319
20-Apr-2026 01:36:29.319 general: debug 1: zone_journal: managed-keys-zone: enter
20-Apr-2026 01:36:29.329 general: debug 1: zone_needdump: managed-keys-zone: enter
20-Apr-2026 01:36:29.329 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 01:36:29.329 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 01:36:29.329 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 01:36:29.329 resolver: debug 1: resolver priming query complete: success
20-Apr-2026 01:36:54.299 general: debug 1: zone_maintenance: managed-keys-zone: enter
20-Apr-2026 01:36:54.299 general: debug 1: zone_dump: managed-keys-zone: enter
20-Apr-2026 01:36:54.299 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 01:36:54.305 general: debug 1: dump_done: managed-keys-zone: enter
20-Apr-2026 01:36:54.305 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
20-Apr-2026 01:37:15.861 network: info: listening on IPv6 interface tapeth0-585913, fe80::7cec:86ff:fe1d:2405%11#53
20-Apr-2026 01:37:15.871 network: info: listening on IPv6 interface tapeth0-0122b5, fe80::8487:8ff:febb:f537%13#53
20-Apr-2026 01:38:39.697 network: info: listening on IPv4 interface kube-ipvs0, 10.108.243.199#53
20-Apr-2026 01:38:47.636 network: info: listening on IPv6 interface tapeth0-efc720, fe80::545d:15ff:fe28:1e28%15#53
20-Apr-2026 01:38:47.655 network: info: listening on IPv6 interface tapeth0-b59966, fe80::f01e:4cff:fe95:162b%17#53
20-Apr-2026 01:38:51.220 network: info: listening on IPv6 interface veth58bda1a8-8, fe80::34d1:aaff:feb9:72ba%18#53
20-Apr-2026 01:38:57.621 network: info: listening on IPv6 interface tapeth0-9b97c0, fe80::5c57:4ff:fe34:7499%20#53
20-Apr-2026 01:39:40.264 network: info: no longer listening on fe80::5c57:4ff:fe34:7499%20#53
20-Apr-2026 01:39:47.168 network: info: no longer listening on fe80::34d1:aaff:feb9:72ba%18#53
20-Apr-2026 01:39:48.075 network: info: no longer listening on fe80::f01e:4cff:fe95:162b%17#53
20-Apr-2026 01:39:52.832 network: info: no longer listening on fe80::545d:15ff:fe28:1e28%15#53
20-Apr-2026 01:40:12.629 network: info: listening on IPv6 interface tapeth0-abbdc4, fe80::e03b:16ff:fe0d:549%22#53
20-Apr-2026 01:40:12.631 network: info: listening on IPv6 interface tapeth0-9d708d, fe80::b494:e0ff:fe0f:1183%24#53
20-Apr-2026 01:40:17.174 network: info: listening on IPv6 interface tapeth0-8b14aa, fe80::8422:f4ff:fe9a:accd%26#53
20-Apr-2026 01:40:17.176 network: info: listening on IPv6 interface tapeth0-5fb98a, fe80::9c49:37ff:feda:8eda%28#53
20-Apr-2026 01:40:17.177 network: info: listening on IPv6 interface tapeth0-248fb9, fe80::94e2:fdff:fef4:6b3e%30#53
20-Apr-2026 01:40:17.177 network: info: listening on IPv6 interface tapeth0-437721, fe80::4cff:5ff:fe80:dcbc%32#53
20-Apr-2026 01:40:22.741 network: info: listening on IPv6 interface tapeth0-b95dfc, fe80::1884:c0ff:fedf:dc98%34#53
20-Apr-2026 01:40:22.741 network: info: listening on IPv6 interface tapeth0-d3c2d4, fe80::8c68:74ff:fedf:bfb9%36#53
20-Apr-2026 01:40:31.930 network: info: listening on IPv4 interface kube-ipvs0, 10.100.17.98#53
20-Apr-2026 01:43:41.028 network: info: no longer listening on fe80::8422:f4ff:fe9a:accd%26#53
20-Apr-2026 01:43:41.059 network: info: no longer listening on fe80::e03b:16ff:fe0d:549%22#53
20-Apr-2026 01:43:41.070 network: info: no longer listening on fe80::b494:e0ff:fe0f:1183%24#53
20-Apr-2026 01:43:41.080 network: info: no longer listening on fe80::4cff:5ff:fe80:dcbc%32#53
20-Apr-2026 01:44:11.398 network: info: no longer listening on fe80::8c68:74ff:fedf:bfb9%36#53
20-Apr-2026 01:44:11.415 network: info: no longer listening on fe80::1884:c0ff:fedf:dc98%34#53
20-Apr-2026 01:44:11.439 network: info: no longer listening on fe80::9c49:37ff:feda:8eda%28#53
20-Apr-2026 01:44:11.442 network: info: no longer listening on fe80::94e2:fdff:fef4:6b3e%30#53
20-Apr-2026 01:44:26.941 network: info: no longer listening on 10.100.17.98#53