11-Jun-2026 01:40:30.088 general: debug 1: now using logging configuration from config file
11-Jun-2026 01:40:30.088 general: debug 1: loop exclusive mode: ending
11-Jun-2026 01:40:30.088 general: debug 1: loop exclusive mode: ended
11-Jun-2026 01:40:30.088 general: notice: command channel listening on 127.0.0.1#8094
11-Jun-2026 01:40:30.088 general: info: VDNS cleanup pass1: 0 departing views cleared
11-Jun-2026 01:40:30.088 general: info: VDNS cleanup pass2: 2 staying views re-checked
11-Jun-2026 01:40:30.088 general: debug 1: load_configuration: success
11-Jun-2026 01:40:30.088 general: debug 1: loop exclusive mode: starting
11-Jun-2026 01:40:30.089 general: debug 1: loop exclusive mode: started
11-Jun-2026 01:40:30.089 zoneload: debug 1: managed-keys-zone: starting load
11-Jun-2026 01:40:30.089 general: debug 1: zone_startload: managed-keys-zone: enter
11-Jun-2026 01:40:30.089 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
11-Jun-2026 01:40:30.089 general: debug 1: managed-keys-zone: creating SOA
11-Jun-2026 01:40:30.089 zoneload: debug 1: managed-keys-zone: loaded; checking validity
11-Jun-2026 01:40:30.089 zoneload: info: managed-keys-zone: loaded serial 0
11-Jun-2026 01:40:30.089 general: debug 1: loop exclusive mode: ending
11-Jun-2026 01:40:30.089 general: debug 1: zone__settimer: managed-keys-zone: enter
11-Jun-2026 01:40:30.089 zoneload: debug 1: zone authors.bind/CH: starting load
11-Jun-2026 01:40:30.089 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
11-Jun-2026 01:40:30.089 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
11-Jun-2026 01:40:30.089 zoneload: debug 1: zone hostname.bind/CH: starting load
11-Jun-2026 01:40:30.090 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
11-Jun-2026 01:40:30.090 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
11-Jun-2026 01:40:30.090 zoneload: debug 1: zone id.server/CH: starting load
11-Jun-2026 01:40:30.090 zoneload: debug 1: zone id.server/CH: loaded; checking validity
11-Jun-2026 01:40:30.090 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
11-Jun-2026 01:40:30.090 general: debug 1: zone__settimer: zone authors.bind/CH: enter
11-Jun-2026 01:40:30.090 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
11-Jun-2026 01:40:30.090 general: debug 1: zone__settimer: zone id.server/CH: enter
11-Jun-2026 01:40:30.090 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
11-Jun-2026 01:40:30.090 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
11-Jun-2026 01:40:30.090 general: debug 1: zone_maintenance: zone id.server/CH: enter
11-Jun-2026 01:40:30.090 general: debug 1: zone__settimer: zone authors.bind/CH: enter
11-Jun-2026 01:40:30.090 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
11-Jun-2026 01:40:30.090 general: debug 1: zone__settimer: zone id.server/CH: enter
11-Jun-2026 01:40:30.090 zoneload: debug 1: zone version.bind/CH: starting load
11-Jun-2026 01:40:30.090 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
11-Jun-2026 01:40:30.090 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
11-Jun-2026 01:40:30.090 general: notice: all zones loaded
11-Jun-2026 01:40:30.090 general: debug 1: managed-keys-zone: synchronizing trusted keys
11-Jun-2026 01:40:30.090 general: debug 1: create_keydata: managed-keys-zone: enter
11-Jun-2026 01:40:30.090 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
11-Jun-2026 01:40:30.090 general: debug 1: managed-keys-zone: next key refresh: 11-Jun-2026 01:40:30.090
11-Jun-2026 01:40:30.090 general: debug 1: zone_journal: managed-keys-zone: enter
11-Jun-2026 01:40:30.090 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
11-Jun-2026 01:40:30.090 general: debug 1: zone__settimer: managed-keys-zone: enter
11-Jun-2026 01:40:30.090 general: debug 1: loop exclusive mode: ended
11-Jun-2026 01:40:30.189 general: debug 1: zone_needdump: managed-keys-zone: enter
11-Jun-2026 01:40:30.189 general: notice: FIPS mode is disabled
11-Jun-2026 01:40:30.189 general: notice: running
11-Jun-2026 01:40:30.189 general: debug 1: debug: t1-cloud-fixed version
11-Jun-2026 01:40:30.189 general: debug 1: zone__settimer: zone version.bind/CH: enter
11-Jun-2026 01:40:30.189 general: debug 1: zone__settimer: zone version.bind/CH: enter
11-Jun-2026 01:40:30.189 general: debug 1: zone_maintenance: zone version.bind/CH: enter
11-Jun-2026 01:40:30.189 general: debug 1: zone__settimer: zone version.bind/CH: enter
11-Jun-2026 01:40:30.189 general: debug 1: zone_maintenance: managed-keys-zone: enter
11-Jun-2026 01:40:30.189 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
11-Jun-2026 01:40:30.189 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
11-Jun-2026 01:40:30.189 general: debug 1: managed-keys-zone: next key refresh: 11-Jun-2026 01:40:30.189
11-Jun-2026 01:40:30.190 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
11-Jun-2026 01:40:30.190 general: debug 1: zone__settimer: zone authors.bind/CH: enter
11-Jun-2026 01:40:30.190 general: debug 1: zone__settimer: zone id.server/CH: enter
11-Jun-2026 01:40:30.190 general: debug 1: zone__settimer: managed-keys-zone: enter
11-Jun-2026 01:40:30.190 general: debug 1: zone__settimer: managed-keys-zone: enter
11-Jun-2026 01:40:30.190 general: debug 1: zone__settimer: managed-keys-zone: enter
11-Jun-2026 01:40:30.190 resolver: debug 1: fetch: ./DNSKEY
11-Jun-2026 01:40:30.190 general: debug 1: zone__settimer: managed-keys-zone: enter
11-Jun-2026 01:40:30.190 resolver: debug 1: fetch: ./NS
11-Jun-2026 01:40:30.190 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
11-Jun-2026 01:40:30.190 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
11-Jun-2026 01:40:30.190 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
11-Jun-2026 01:40:30.190 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
11-Jun-2026 01:40:30.190 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
11-Jun-2026 01:40:30.190 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
11-Jun-2026 01:40:30.190 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
11-Jun-2026 01:40:30.190 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
11-Jun-2026 01:40:30.190 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
11-Jun-2026 01:40:30.190 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
11-Jun-2026 01:40:30.190 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
11-Jun-2026 01:40:30.190 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
11-Jun-2026 01:40:30.190 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
11-Jun-2026 01:40:30.190 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
11-Jun-2026 01:40:30.190 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
11-Jun-2026 01:40:30.191 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
11-Jun-2026 01:40:30.191 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
11-Jun-2026 01:40:30.191 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
11-Jun-2026 01:40:30.191 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
11-Jun-2026 01:40:30.191 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
11-Jun-2026 01:40:30.191 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
11-Jun-2026 01:40:30.191 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
11-Jun-2026 01:40:30.191 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
11-Jun-2026 01:40:30.191 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
11-Jun-2026 01:40:30.191 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
11-Jun-2026 01:40:30.192 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
11-Jun-2026 01:40:30.238 database: debug 1: delete_node(): 0xb60cb0 . (bucket 2)
11-Jun-2026 01:40:30.238 resolver: debug 1: fetch: ./DNSKEY
11-Jun-2026 01:40:30.238 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
11-Jun-2026 01:40:30.238 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
11-Jun-2026 01:40:30.243 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.
11-Jun-2026 01:40:30.243 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
11-Jun-2026 01:40:30.243 general: debug 1: managed-keys-zone: next key refresh: 12-Jun-2026 01:40:30.243
11-Jun-2026 01:40:30.243 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.
11-Jun-2026 01:40:30.243 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
11-Jun-2026 01:40:30.243 general: debug 1: managed-keys-zone: next key refresh: 12-Jun-2026 01:40:30.243
11-Jun-2026 01:40:30.243 general: debug 1: zone_journal: managed-keys-zone: enter
11-Jun-2026 01:40:30.252 general: debug 1: zone_needdump: managed-keys-zone: enter
11-Jun-2026 01:40:30.252 general: debug 1: zone__settimer: managed-keys-zone: enter
11-Jun-2026 01:40:30.252 general: debug 1: zone__settimer: managed-keys-zone: enter
11-Jun-2026 01:40:30.252 general: debug 1: zone__settimer: managed-keys-zone: enter
11-Jun-2026 01:40:30.301 resolver: debug 1: resolver priming query complete: success
11-Jun-2026 01:40:59.217 general: debug 1: zone_maintenance: managed-keys-zone: enter
11-Jun-2026 01:40:59.217 general: debug 1: zone_dump: managed-keys-zone: enter
11-Jun-2026 01:40:59.217 general: debug 1: zone__settimer: managed-keys-zone: enter
11-Jun-2026 01:40:59.219 general: debug 1: dump_done: managed-keys-zone: enter
11-Jun-2026 01:40:59.219 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
11-Jun-2026 01:41:24.582 network: info: listening on IPv6 interface tapeth0-f75e6e, fe80::74e1:3cff:fe4b:1a13%11#53
11-Jun-2026 01:41:24.583 network: info: listening on IPv6 interface tapeth0-e8bde4, fe80::9061:10ff:fe84:9f5c%13#53
11-Jun-2026 01:42:33.932 network: info: listening on IPv4 interface kube-ipvs0, 10.101.158.85#53
11-Jun-2026 01:42:41.574 network: info: listening on IPv6 interface tapeth0-a44b81, fe80::386d:f4ff:fe2a:c4df%15#53
11-Jun-2026 01:42:41.582 network: info: listening on IPv6 interface tapeth0-b08283, fe80::c036:d1ff:fe6d:5bac%17#53
11-Jun-2026 01:42:45.033 network: info: listening on IPv6 interface veth1da93dcf-3, fe80::f4a2:23ff:fefe:514e%18#53
11-Jun-2026 01:42:50.601 network: info: listening on IPv6 interface tapeth0-1dc9f9, fe80::74df:a8ff:fef1:630e%20#53
11-Jun-2026 01:43:34.013 network: info: no longer listening on fe80::74df:a8ff:fef1:630e%20#53
11-Jun-2026 01:43:40.331 network: info: no longer listening on fe80::f4a2:23ff:fefe:514e%18#53
11-Jun-2026 01:43:41.406 network: info: no longer listening on fe80::c036:d1ff:fe6d:5bac%17#53
11-Jun-2026 01:43:46.393 network: info: no longer listening on fe80::386d:f4ff:fe2a:c4df%15#53
11-Jun-2026 01:44:05.862 network: info: listening on IPv6 interface tapeth0-397e2a, fe80::a004:abff:fe22:a8e5%22#53
11-Jun-2026 01:44:05.866 network: info: listening on IPv6 interface tapeth0-5f7ff8, fe80::80bb:5fff:fe96:781e%24#53
11-Jun-2026 01:44:05.866 network: info: listening on IPv6 interface tapeth0-0ffe00, fe80::c096:a7ff:fe86:ce7f%26#53
11-Jun-2026 01:44:11.431 network: info: listening on IPv6 interface tapeth0-751a36, fe80::f0c6:d4ff:fe8c:d580%28#53
11-Jun-2026 01:44:11.434 network: info: listening on IPv6 interface tapeth0-1b26d6, fe80::109c:b8ff:fe6f:623b%30#53
11-Jun-2026 01:44:11.438 network: info: listening on IPv6 interface tapeth0-7a8f36, fe80::cc9d:48ff:fed1:6162%32#53
11-Jun-2026 01:44:11.439 network: info: listening on IPv6 interface tapeth0-700055, fe80::14ae:d6ff:fe9e:e622%34#53
11-Jun-2026 01:44:15.974 network: info: listening on IPv6 interface tapeth0-06f2e0, fe80::2c7f:acff:fe33:b30c%36#53
11-Jun-2026 01:44:25.425 network: info: listening on IPv4 interface kube-ipvs0, 10.100.113.192#53
11-Jun-2026 01:47:34.039 network: info: no longer listening on fe80::a004:abff:fe22:a8e5%22#53
11-Jun-2026 01:47:34.044 network: info: no longer listening on fe80::80bb:5fff:fe96:781e%24#53
11-Jun-2026 01:47:34.051 network: info: no longer listening on fe80::c096:a7ff:fe86:ce7f%26#53
11-Jun-2026 01:47:34.052 network: info: no longer listening on fe80::f0c6:d4ff:fe8c:d580%28#53
11-Jun-2026 01:48:04.432 network: info: no longer listening on fe80::2c7f:acff:fe33:b30c%36#53
11-Jun-2026 01:48:04.453 network: info: no longer listening on fe80::109c:b8ff:fe6f:623b%30#53
11-Jun-2026 01:48:04.456 network: info: no longer listening on fe80::14ae:d6ff:fe9e:e622%34#53
11-Jun-2026 01:48:04.466 network: info: no longer listening on fe80::cc9d:48ff:fed1:6162%32#53
11-Jun-2026 01:48:19.571 network: info: no longer listening on 10.100.113.192#53