18-Jun-2026 01:32:05.516 general: debug 1: now using logging configuration from config file
18-Jun-2026 01:32:05.517 general: debug 1: loop exclusive mode: ending
18-Jun-2026 01:32:05.517 general: debug 1: loop exclusive mode: ended
18-Jun-2026 01:32:05.517 general: notice: command channel listening on 127.0.0.1#8094
18-Jun-2026 01:32:05.517 general: info: VDNS cleanup pass1: 0 departing views cleared
18-Jun-2026 01:32:05.517 general: info: VDNS cleanup pass2: 2 staying views re-checked
18-Jun-2026 01:32:05.517 general: debug 1: load_configuration: success
18-Jun-2026 01:32:05.517 general: debug 1: loop exclusive mode: starting
18-Jun-2026 01:32:05.519 general: debug 1: loop exclusive mode: started
18-Jun-2026 01:32:05.519 zoneload: debug 1: managed-keys-zone: starting load
18-Jun-2026 01:32:05.519 general: debug 1: zone_startload: managed-keys-zone: enter
18-Jun-2026 01:32:05.519 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
18-Jun-2026 01:32:05.519 general: debug 1: managed-keys-zone: creating SOA
18-Jun-2026 01:32:05.519 zoneload: debug 1: managed-keys-zone: loaded; checking validity
18-Jun-2026 01:32:05.519 zoneload: info: managed-keys-zone: loaded serial 0
18-Jun-2026 01:32:05.519 general: debug 1: loop exclusive mode: ending
18-Jun-2026 01:32:05.519 general: debug 1: zone__settimer: managed-keys-zone: enter
18-Jun-2026 01:32:05.519 zoneload: debug 1: zone authors.bind/CH: starting load
18-Jun-2026 01:32:05.519 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
18-Jun-2026 01:32:05.519 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
18-Jun-2026 01:32:05.519 zoneload: debug 1: zone version.bind/CH: starting load
18-Jun-2026 01:32:05.519 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
18-Jun-2026 01:32:05.519 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
18-Jun-2026 01:32:05.519 zoneload: debug 1: zone id.server/CH: starting load
18-Jun-2026 01:32:05.519 zoneload: debug 1: zone id.server/CH: loaded; checking validity
18-Jun-2026 01:32:05.519 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
18-Jun-2026 01:32:05.519 general: debug 1: zone__settimer: zone authors.bind/CH: enter
18-Jun-2026 01:32:05.519 general: debug 1: zone__settimer: zone version.bind/CH: enter
18-Jun-2026 01:32:05.519 general: debug 1: zone__settimer: zone id.server/CH: enter
18-Jun-2026 01:32:05.519 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
18-Jun-2026 01:32:05.519 general: debug 1: zone_maintenance: zone version.bind/CH: enter
18-Jun-2026 01:32:05.519 general: debug 1: zone_maintenance: zone id.server/CH: enter
18-Jun-2026 01:32:05.519 general: debug 1: zone__settimer: zone authors.bind/CH: enter
18-Jun-2026 01:32:05.519 general: debug 1: zone__settimer: zone version.bind/CH: enter
18-Jun-2026 01:32:05.519 general: debug 1: zone__settimer: zone id.server/CH: enter
18-Jun-2026 01:32:05.519 general: debug 1: loop exclusive mode: ended
18-Jun-2026 01:32:05.519 zoneload: debug 1: zone hostname.bind/CH: starting load
18-Jun-2026 01:32:05.519 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
18-Jun-2026 01:32:05.519 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
18-Jun-2026 01:32:05.519 general: notice: all zones loaded
18-Jun-2026 01:32:05.519 general: debug 1: managed-keys-zone: synchronizing trusted keys
18-Jun-2026 01:32:05.519 general: debug 1: create_keydata: managed-keys-zone: enter
18-Jun-2026 01:32:05.519 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
18-Jun-2026 01:32:05.519 general: debug 1: managed-keys-zone: next key refresh: 18-Jun-2026 01:32:05.519
18-Jun-2026 01:32:05.521 general: debug 1: zone__settimer: managed-keys-zone: enter
18-Jun-2026 01:32:05.521 general: debug 1: zone_journal: managed-keys-zone: enter
18-Jun-2026 01:32:05.521 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
18-Jun-2026 01:32:05.565 general: debug 1: zone_needdump: managed-keys-zone: enter
18-Jun-2026 01:32:05.565 general: debug 1: zone_maintenance: managed-keys-zone: enter
18-Jun-2026 01:32:05.565 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
18-Jun-2026 01:32:05.565 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
18-Jun-2026 01:32:05.565 general: debug 1: managed-keys-zone: next key refresh: 18-Jun-2026 01:32:05.565
18-Jun-2026 01:32:05.565 general: debug 1: zone__settimer: managed-keys-zone: enter
18-Jun-2026 01:32:05.565 general: debug 1: zone__settimer: managed-keys-zone: enter
18-Jun-2026 01:32:05.565 resolver: debug 1: fetch: ./DNSKEY
18-Jun-2026 01:32:05.565 general: debug 1: zone__settimer: managed-keys-zone: enter
18-Jun-2026 01:32:05.565 resolver: debug 1: fetch: ./NS
18-Jun-2026 01:32:05.565 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
18-Jun-2026 01:32:05.565 general: notice: FIPS mode is disabled
18-Jun-2026 01:32:05.565 general: notice: running
18-Jun-2026 01:32:05.566 general: debug 1: debug: t1-cloud-fixed version
18-Jun-2026 01:32:05.566 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
18-Jun-2026 01:32:05.566 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
18-Jun-2026 01:32:05.566 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
18-Jun-2026 01:32:05.566 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
18-Jun-2026 01:32:05.566 general: debug 1: zone__settimer: managed-keys-zone: enter
18-Jun-2026 01:32:05.566 general: debug 1: zone__settimer: zone version.bind/CH: enter
18-Jun-2026 01:32:05.566 general: debug 1: zone__settimer: zone authors.bind/CH: enter
18-Jun-2026 01:32:05.566 general: debug 1: zone__settimer: zone id.server/CH: enter
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
18-Jun-2026 01:32:05.566 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
18-Jun-2026 01:32:05.620 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.
18-Jun-2026 01:32:05.620 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
18-Jun-2026 01:32:05.620 general: debug 1: managed-keys-zone: next key refresh: 19-Jun-2026 01:32:05.620
18-Jun-2026 01:32:05.620 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.
18-Jun-2026 01:32:05.620 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
18-Jun-2026 01:32:05.620 general: debug 1: managed-keys-zone: next key refresh: 19-Jun-2026 01:32:05.620
18-Jun-2026 01:32:05.620 general: debug 1: zone_journal: managed-keys-zone: enter
18-Jun-2026 01:32:05.654 general: debug 1: zone_needdump: managed-keys-zone: enter
18-Jun-2026 01:32:05.654 general: debug 1: zone__settimer: managed-keys-zone: enter
18-Jun-2026 01:32:05.654 general: debug 1: zone__settimer: managed-keys-zone: enter
18-Jun-2026 01:32:05.654 general: debug 1: zone__settimer: managed-keys-zone: enter
18-Jun-2026 01:32:05.657 resolver: debug 1: resolver priming query complete: success
18-Jun-2026 01:32:32.681 general: debug 1: zone_maintenance: managed-keys-zone: enter
18-Jun-2026 01:32:32.681 general: debug 1: zone_dump: managed-keys-zone: enter
18-Jun-2026 01:32:32.684 general: debug 1: zone__settimer: managed-keys-zone: enter
18-Jun-2026 01:32:32.699 general: debug 1: dump_done: managed-keys-zone: enter
18-Jun-2026 01:32:32.699 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
18-Jun-2026 01:32:55.853 network: info: listening on IPv6 interface tapeth0-b10db1, fe80::1852:55ff:feec:ec3f%11#53
18-Jun-2026 01:32:55.854 network: info: listening on IPv6 interface tapeth0-1fa135, fe80::e8a1:20ff:fe93:5078%13#53
18-Jun-2026 01:34:32.117 network: info: listening on IPv4 interface kube-ipvs0, 10.98.85.139#53
18-Jun-2026 01:34:39.727 network: info: listening on IPv6 interface tapeth0-eb987c, fe80::c40a:d2ff:fee2:3b2e%15#53
18-Jun-2026 01:34:42.542 network: info: listening on IPv6 interface tapeth0-a431c5, fe80::785f:f9ff:fe2e:faac%17#53
18-Jun-2026 01:34:42.618 network: info: listening on IPv6 interface veth923a0ba4-b, fe80::18bc:6cff:fed3:2813%18#53
18-Jun-2026 01:34:47.916 network: info: listening on IPv6 interface tapeth0-7cf5e9, fe80::307e:3aff:fe0d:b95b%20#53
18-Jun-2026 01:35:31.086 network: info: no longer listening on fe80::307e:3aff:fe0d:b95b%20#53
18-Jun-2026 01:35:37.542 network: info: no longer listening on fe80::18bc:6cff:fed3:2813%18#53
18-Jun-2026 01:35:38.637 network: info: no longer listening on fe80::785f:f9ff:fe2e:faac%17#53
18-Jun-2026 01:35:43.674 network: info: no longer listening on fe80::c40a:d2ff:fee2:3b2e%15#53
18-Jun-2026 01:36:03.693 network: info: listening on IPv6 interface tapeth0-27b052, fe80::64d9:66ff:febb:b108%22#53
18-Jun-2026 01:36:03.697 network: info: listening on IPv6 interface tapeth0-02b626, fe80::f459:d0ff:fe77:6d6b%24#53
18-Jun-2026 01:36:03.697 network: info: listening on IPv6 interface tapeth0-bd1fac, fe80::1884:39ff:fe91:8b99%26#53
18-Jun-2026 01:36:08.686 network: info: listening on IPv6 interface tapeth0-97f1ba, fe80::30fb:cff:fe5a:2505%28#53
18-Jun-2026 01:36:08.687 network: info: listening on IPv6 interface tapeth0-468f2b, fe80::5485:deff:fee3:aaec%30#53
18-Jun-2026 01:36:08.689 network: info: listening on IPv6 interface tapeth0-082350, fe80::3c79:f6ff:fe96:a2e0%32#53
18-Jun-2026 01:36:08.689 network: info: listening on IPv6 interface tapeth0-145594, fe80::a862:5ff:fe51:9bf0%34#53
18-Jun-2026 01:36:14.382 network: info: listening on IPv6 interface tapeth0-234438, fe80::1c1e:3eff:fed2:ff0e%36#53
18-Jun-2026 01:36:17.734 network: info: listening on IPv4 interface kube-ipvs0, 10.99.57.50#53
18-Jun-2026 01:39:27.500 network: info: no longer listening on fe80::f459:d0ff:fe77:6d6b%24#53
18-Jun-2026 01:39:27.538 network: info: no longer listening on fe80::64d9:66ff:febb:b108%22#53
18-Jun-2026 01:39:27.539 network: info: no longer listening on fe80::1884:39ff:fe91:8b99%26#53
18-Jun-2026 01:39:27.568 network: info: no longer listening on fe80::3c79:f6ff:fe96:a2e0%32#53
18-Jun-2026 01:39:57.605 network: info: no longer listening on fe80::1c1e:3eff:fed2:ff0e%36#53
18-Jun-2026 01:39:57.627 network: info: no longer listening on fe80::30fb:cff:fe5a:2505%28#53
18-Jun-2026 01:39:57.628 network: info: no longer listening on fe80::a862:5ff:fe51:9bf0%34#53
18-Jun-2026 01:39:57.638 network: info: no longer listening on fe80::5485:deff:fee3:aaec%30#53
18-Jun-2026 01:40:13.139 network: info: no longer listening on 10.99.57.50#53