20-Apr-2026 16:00:37.410 general: debug 1: now using logging configuration from config file
20-Apr-2026 16:00:37.410 general: debug 1: loop exclusive mode: ending
20-Apr-2026 16:00:37.410 general: debug 1: loop exclusive mode: ended
20-Apr-2026 16:00:37.410 general: notice: command channel listening on 127.0.0.1#8094
20-Apr-2026 16:00:37.410 general: info: VDNS cleanup pass1: 0 departing views cleared
20-Apr-2026 16:00:37.410 general: info: VDNS cleanup pass2: 2 staying views re-checked
20-Apr-2026 16:00:37.410 general: debug 1: load_configuration: success
20-Apr-2026 16:00:37.410 general: debug 1: loop exclusive mode: starting
20-Apr-2026 16:00:37.411 general: debug 1: loop exclusive mode: started
20-Apr-2026 16:00:37.411 zoneload: debug 1: managed-keys-zone: starting load
20-Apr-2026 16:00:37.411 general: debug 1: zone_startload: managed-keys-zone: enter
20-Apr-2026 16:00:37.411 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
20-Apr-2026 16:00:37.411 general: debug 1: managed-keys-zone: creating SOA
20-Apr-2026 16:00:37.411 zoneload: debug 1: managed-keys-zone: loaded; checking validity
20-Apr-2026 16:00:37.411 zoneload: info: managed-keys-zone: loaded serial 0
20-Apr-2026 16:00:37.411 general: debug 1: loop exclusive mode: ending
20-Apr-2026 16:00:37.411 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 16:00:37.411 zoneload: debug 1: zone authors.bind/CH: starting load
20-Apr-2026 16:00:37.411 general: debug 1: loop exclusive mode: ended
20-Apr-2026 16:00:37.411 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
20-Apr-2026 16:00:37.411 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
20-Apr-2026 16:00:37.411 zoneload: debug 1: zone hostname.bind/CH: starting load
20-Apr-2026 16:00:37.411 general: debug 1: zone__settimer: zone authors.bind/CH: enter
20-Apr-2026 16:00:37.411 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
20-Apr-2026 16:00:37.411 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
20-Apr-2026 16:00:37.411 zoneload: debug 1: zone version.bind/CH: starting load
20-Apr-2026 16:00:37.411 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
20-Apr-2026 16:00:37.411 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
20-Apr-2026 16:00:37.411 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
20-Apr-2026 16:00:37.411 zoneload: debug 1: zone id.server/CH: starting load
20-Apr-2026 16:00:37.411 zoneload: debug 1: zone id.server/CH: loaded; checking validity
20-Apr-2026 16:00:37.411 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
20-Apr-2026 16:00:37.411 general: debug 1: zone__settimer: zone version.bind/CH: enter
20-Apr-2026 16:00:37.411 general: debug 1: zone__settimer: zone id.server/CH: enter
20-Apr-2026 16:00:37.411 general: notice: all zones loaded
20-Apr-2026 16:00:37.411 general: debug 1: zone_maintenance: zone version.bind/CH: enter
20-Apr-2026 16:00:37.411 general: debug 1: zone_maintenance: zone id.server/CH: enter
20-Apr-2026 16:00:37.411 general: debug 1: zone__settimer: zone version.bind/CH: enter
20-Apr-2026 16:00:37.411 general: debug 1: zone__settimer: zone id.server/CH: enter
20-Apr-2026 16:00:37.411 general: debug 1: zone__settimer: zone authors.bind/CH: enter
20-Apr-2026 16:00:37.412 general: debug 1: managed-keys-zone: synchronizing trusted keys
20-Apr-2026 16:00:37.412 general: debug 1: create_keydata: managed-keys-zone: enter
20-Apr-2026 16:00:37.412 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
20-Apr-2026 16:00:37.412 general: debug 1: managed-keys-zone: next key refresh: 20-Apr-2026 16:00:37.412
20-Apr-2026 16:00:37.412 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 16:00:37.412 general: debug 1: zone_journal: managed-keys-zone: enter
20-Apr-2026 16:00:37.412 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
20-Apr-2026 16:00:37.422 general: debug 1: zone_needdump: managed-keys-zone: enter
20-Apr-2026 16:00:37.422 general: notice: FIPS mode is disabled
20-Apr-2026 16:00:37.422 general: notice: running
20-Apr-2026 16:00:37.422 general: debug 1: debug: t1-cloud-fixed version
20-Apr-2026 16:00:37.422 general: debug 1: zone_maintenance: managed-keys-zone: enter
20-Apr-2026 16:00:37.423 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
20-Apr-2026 16:00:37.423 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
20-Apr-2026 16:00:37.423 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
20-Apr-2026 16:00:37.423 general: debug 1: managed-keys-zone: next key refresh: 20-Apr-2026 16:00:37.423
20-Apr-2026 16:00:37.423 general: debug 1: zone__settimer: zone version.bind/CH: enter
20-Apr-2026 16:00:37.423 general: debug 1: zone__settimer: zone id.server/CH: enter
20-Apr-2026 16:00:37.423 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 16:00:37.423 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 16:00:37.423 general: debug 1: zone__settimer: zone authors.bind/CH: enter
20-Apr-2026 16:00:37.423 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 16:00:37.423 resolver: debug 1: fetch: ./DNSKEY
20-Apr-2026 16:00:37.423 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 16:00:37.423 resolver: debug 1: fetch: ./NS
20-Apr-2026 16:00:37.423 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
20-Apr-2026 16:00:37.423 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
20-Apr-2026 16:00:37.423 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
20-Apr-2026 16:00:37.423 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
20-Apr-2026 16:00:37.423 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
20-Apr-2026 16:00:37.423 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
20-Apr-2026 16:00:37.423 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
20-Apr-2026 16:00:37.423 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
20-Apr-2026 16:00:37.423 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
20-Apr-2026 16:00:37.423 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
20-Apr-2026 16:00:37.423 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
20-Apr-2026 16:00:37.423 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
20-Apr-2026 16:00:37.423 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
20-Apr-2026 16:00:37.423 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
20-Apr-2026 16:00:37.423 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
20-Apr-2026 16:00:37.423 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
20-Apr-2026 16:00:37.424 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
20-Apr-2026 16:00:37.424 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
20-Apr-2026 16:00:37.424 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
20-Apr-2026 16:00:37.424 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
20-Apr-2026 16:00:37.424 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
20-Apr-2026 16:00:37.424 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
20-Apr-2026 16:00:37.424 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
20-Apr-2026 16:00:37.424 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
20-Apr-2026 16:00:37.424 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
20-Apr-2026 16:00:37.424 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
20-Apr-2026 16:00:37.424 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
20-Apr-2026 16:00:37.424 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
20-Apr-2026 16:00:37.473 database: debug 1: delete_node(): 0x7f7768002220 . (bucket 1)
20-Apr-2026 16:00:37.474 resolver: debug 1: fetch: ./DNSKEY
20-Apr-2026 16:00:37.474 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
20-Apr-2026 16:00:37.474 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
20-Apr-2026 16:00:37.474 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
20-Apr-2026 16:00:37.474 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
20-Apr-2026 16:00:37.476 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 16:00:37.476 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
20-Apr-2026 16:00:37.476 general: debug 1: managed-keys-zone: next key refresh: 21-Apr-2026 16:00:37.476
20-Apr-2026 16:00:37.476 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 16:00:37.476 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
20-Apr-2026 16:00:37.476 general: debug 1: managed-keys-zone: next key refresh: 21-Apr-2026 16:00:37.476
20-Apr-2026 16:00:37.476 general: debug 1: zone_journal: managed-keys-zone: enter
20-Apr-2026 16:00:37.494 general: debug 1: zone_needdump: managed-keys-zone: enter
20-Apr-2026 16:00:37.494 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 16:00:37.494 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 16:00:37.494 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 16:00:37.520 resolver: debug 1: resolver priming query complete: success
20-Apr-2026 16:01:02.525 general: debug 1: zone_maintenance: managed-keys-zone: enter
20-Apr-2026 16:01:02.525 general: debug 1: zone_dump: managed-keys-zone: enter
20-Apr-2026 16:01:02.533 general: debug 1: zone__settimer: managed-keys-zone: enter
20-Apr-2026 16:01:02.553 general: debug 1: dump_done: managed-keys-zone: enter
20-Apr-2026 16:01:02.553 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
20-Apr-2026 16:01:30.436 network: info: listening on IPv6 interface tapeth0-b4dd2c, fe80::14d3:1dff:fe95:59ef%11#53
20-Apr-2026 16:01:39.972 network: info: listening on IPv6 interface tapeth0-e31a43, fe80::dc50:edff:fe16:4dc0%13#53
20-Apr-2026 16:03:11.950 network: info: listening on IPv4 interface kube-ipvs0, 10.104.92.91#53
20-Apr-2026 16:03:19.557 network: info: listening on IPv6 interface tapeth0-31e622, fe80::bc05:84ff:fe1b:63c5%15#53
20-Apr-2026 16:03:19.574 network: info: listening on IPv6 interface tapeth0-7da796, fe80::bc56:2cff:feb3:28c4%17#53
20-Apr-2026 16:03:22.567 network: info: listening on IPv6 interface veth09f7ec55-b, fe80::a8bc:7eff:fed1:33f6%18#53
20-Apr-2026 16:03:28.708 network: info: listening on IPv6 interface tapeth0-c358ec, fe80::ec41:b1ff:fe0b:ae4b%20#53
20-Apr-2026 16:04:11.522 network: info: no longer listening on fe80::ec41:b1ff:fe0b:ae4b%20#53
20-Apr-2026 16:04:18.453 network: info: no longer listening on fe80::a8bc:7eff:fed1:33f6%18#53
20-Apr-2026 16:04:19.195 network: info: no longer listening on fe80::bc05:84ff:fe1b:63c5%15#53
20-Apr-2026 16:04:24.042 network: info: no longer listening on fe80::bc56:2cff:feb3:28c4%17#53
20-Apr-2026 16:04:44.163 network: info: listening on IPv6 interface tapeth0-7e915f, fe80::e0cd:2bff:fe7b:d993%22#53
20-Apr-2026 16:04:44.163 network: info: listening on IPv6 interface tapeth0-2cef2c, fe80::186e:8dff:fef4:1fae%24#53
20-Apr-2026 16:04:44.164 network: info: listening on IPv6 interface tapeth0-8acebf, fe80::3406:caff:fe1b:bd98%26#53
20-Apr-2026 16:04:49.988 network: info: listening on IPv6 interface tapeth0-4d326a, fe80::1073:34ff:fe95:4893%28#53
20-Apr-2026 16:04:49.989 network: info: listening on IPv6 interface tapeth0-425198, fe80::c835:3fff:feee:4349%30#53
20-Apr-2026 16:04:49.989 network: info: listening on IPv6 interface tapeth0-8bdc8c, fe80::4051:37ff:fe60:5bc2%32#53
20-Apr-2026 16:04:54.212 network: info: listening on IPv6 interface tapeth0-346495, fe80::2016:53ff:fe9d:e61b%34#53
20-Apr-2026 16:04:54.221 network: info: listening on IPv6 interface tapeth0-b24416, fe80::ce0:3dff:fef9:8d6%36#53
20-Apr-2026 16:05:03.517 network: info: listening on IPv4 interface kube-ipvs0, 10.99.12.170#53
20-Apr-2026 16:08:13.276 network: info: no longer listening on fe80::186e:8dff:fef4:1fae%24#53
20-Apr-2026 16:08:13.294 network: info: no longer listening on fe80::e0cd:2bff:fe7b:d993%22#53
20-Apr-2026 16:08:13.314 network: info: no longer listening on fe80::3406:caff:fe1b:bd98%26#53
20-Apr-2026 16:08:13.314 network: info: no longer listening on fe80::1073:34ff:fe95:4893%28#53
20-Apr-2026 16:08:43.222 network: info: no longer listening on fe80::ce0:3dff:fef9:8d6%36#53
20-Apr-2026 16:08:43.263 network: info: no longer listening on fe80::2016:53ff:fe9d:e61b%34#53
20-Apr-2026 16:08:43.275 network: info: no longer listening on fe80::c835:3fff:feee:4349%30#53
20-Apr-2026 16:08:43.295 network: info: no longer listening on fe80::4051:37ff:fe60:5bc2%32#53
20-Apr-2026 16:08:58.899 network: info: no longer listening on 10.99.12.170#53