27-Oct-2025 01:39:13.798 general: debug 1: now using logging configuration from config file
27-Oct-2025 01:39:13.798 general: debug 1: loop exclusive mode: ending
27-Oct-2025 01:39:13.798 general: debug 1: loop exclusive mode: ended
27-Oct-2025 01:39:13.798 general: notice: command channel listening on 127.0.0.1#8094
27-Oct-2025 01:39:13.798 general: debug 1: load_configuration: success
27-Oct-2025 01:39:13.798 general: debug 1: loop exclusive mode: starting
27-Oct-2025 01:39:13.816 general: debug 1: loop exclusive mode: started
27-Oct-2025 01:39:13.816 zoneload: debug 1: managed-keys-zone: starting load
27-Oct-2025 01:39:13.816 general: debug 1: zone_startload: managed-keys-zone: enter
27-Oct-2025 01:39:13.816 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
27-Oct-2025 01:39:13.816 general: debug 1: managed-keys-zone: creating SOA
27-Oct-2025 01:39:13.816 zoneload: debug 1: managed-keys-zone: loaded; checking validity
27-Oct-2025 01:39:13.816 zoneload: info: managed-keys-zone: loaded serial 0
27-Oct-2025 01:39:13.816 general: debug 1: loop exclusive mode: ending
27-Oct-2025 01:39:13.816 zoneload: debug 1: zone hostname.bind/CH: starting load
27-Oct-2025 01:39:13.817 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
27-Oct-2025 01:39:13.817 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
27-Oct-2025 01:39:13.817 zoneload: debug 1: zone id.server/CH: starting load
27-Oct-2025 01:39:13.817 zoneload: debug 1: zone id.server/CH: loaded; checking validity
27-Oct-2025 01:39:13.817 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
27-Oct-2025 01:39:13.820 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
27-Oct-2025 01:39:13.820 general: debug 1: zone__settimer: zone id.server/CH: enter
27-Oct-2025 01:39:13.820 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
27-Oct-2025 01:39:13.820 general: debug 1: zone_maintenance: zone id.server/CH: enter
27-Oct-2025 01:39:13.820 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
27-Oct-2025 01:39:13.820 general: debug 1: zone__settimer: zone id.server/CH: enter
27-Oct-2025 01:39:13.820 general: debug 1: loop exclusive mode: ended
27-Oct-2025 01:39:13.820 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Oct-2025 01:39:13.820 zoneload: debug 1: zone authors.bind/CH: starting load
27-Oct-2025 01:39:13.820 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
27-Oct-2025 01:39:13.820 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
27-Oct-2025 01:39:13.820 zoneload: debug 1: zone version.bind/CH: starting load
27-Oct-2025 01:39:13.820 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
27-Oct-2025 01:39:13.820 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
27-Oct-2025 01:39:13.820 general: notice: all zones loaded
27-Oct-2025 01:39:13.820 general: debug 1: managed-keys-zone: synchronizing trusted keys
27-Oct-2025 01:39:13.821 general: debug 1: create_keydata: managed-keys-zone: enter
27-Oct-2025 01:39:13.821 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
27-Oct-2025 01:39:13.821 general: debug 1: managed-keys-zone: next key refresh: 27-Oct-2025 01:39:13.821
27-Oct-2025 01:39:13.821 general: debug 1: zone_journal: managed-keys-zone: enter
27-Oct-2025 01:39:13.821 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
27-Oct-2025 01:39:13.835 general: debug 1: zone_needdump: managed-keys-zone: enter
27-Oct-2025 01:39:13.837 general: notice: FIPS mode is disabled
27-Oct-2025 01:39:13.838 general: notice: running
27-Oct-2025 01:39:13.838 general: debug 1: zone__settimer: zone authors.bind/CH: enter
27-Oct-2025 01:39:13.838 general: debug 1: zone__settimer: zone version.bind/CH: enter
27-Oct-2025 01:39:13.838 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Oct-2025 01:39:13.838 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Oct-2025 01:39:13.838 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Oct-2025 01:39:13.838 general: debug 1: zone__settimer: zone version.bind/CH: enter
27-Oct-2025 01:39:13.838 general: debug 1: zone__settimer: zone authors.bind/CH: enter
27-Oct-2025 01:39:13.838 general: debug 1: zone_maintenance: managed-keys-zone: enter
27-Oct-2025 01:39:13.838 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
27-Oct-2025 01:39:13.838 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
27-Oct-2025 01:39:13.838 general: debug 1: managed-keys-zone: next key refresh: 27-Oct-2025 01:39:13.838
27-Oct-2025 01:39:13.838 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
27-Oct-2025 01:39:13.838 general: debug 1: zone__settimer: zone id.server/CH: enter
27-Oct-2025 01:39:13.838 general: debug 1: zone_maintenance: zone version.bind/CH: enter
27-Oct-2025 01:39:13.838 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
27-Oct-2025 01:39:13.838 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Oct-2025 01:39:13.838 resolver: debug 1: fetch: ./DNSKEY
27-Oct-2025 01:39:13.838 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Oct-2025 01:39:13.838 general: debug 1: zone__settimer: zone version.bind/CH: enter
27-Oct-2025 01:39:13.838 general: debug 1: zone__settimer: zone authors.bind/CH: enter
27-Oct-2025 01:39:13.838 resolver: debug 1: fetch: ./NS
27-Oct-2025 01:39:13.838 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
27-Oct-2025 01:39:13.839 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
27-Oct-2025 01:39:13.840 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
27-Oct-2025 01:39:13.840 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
27-Oct-2025 01:39:13.840 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
27-Oct-2025 01:39:13.840 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
27-Oct-2025 01:39:13.854 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.
27-Oct-2025 01:39:13.854 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
27-Oct-2025 01:39:13.854 general: debug 1: managed-keys-zone: next key refresh: 28-Oct-2025 01:39:13.854
27-Oct-2025 01:39:13.854 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.
27-Oct-2025 01:39:13.854 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
27-Oct-2025 01:39:13.854 general: debug 1: managed-keys-zone: next key refresh: 28-Oct-2025 01:39:13.854
27-Oct-2025 01:39:13.854 general: debug 1: zone_journal: managed-keys-zone: enter
27-Oct-2025 01:39:13.888 general: debug 1: zone_needdump: managed-keys-zone: enter
27-Oct-2025 01:39:13.888 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Oct-2025 01:39:13.888 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Oct-2025 01:39:13.888 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Oct-2025 01:39:13.922 resolver: debug 1: resolver priming query complete: success
27-Oct-2025 01:39:42.863 general: debug 1: zone_maintenance: managed-keys-zone: enter
27-Oct-2025 01:39:42.863 general: debug 1: zone_dump: managed-keys-zone: enter
27-Oct-2025 01:39:42.863 general: debug 1: zone__settimer: managed-keys-zone: enter
27-Oct-2025 01:39:42.866 general: debug 1: dump_done: managed-keys-zone: enter
27-Oct-2025 01:39:42.866 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
27-Oct-2025 01:39:54.006 network: info: listening on IPv6 interface tapeth0-04a2cc, fe80::f839:43ff:fe8e:ffad%11#53
27-Oct-2025 01:39:54.007 network: info: listening on IPv6 interface tapeth0-cd1a6d, fe80::7460:a9ff:feef:af2b%13#53
27-Oct-2025 01:41:43.936 network: info: listening on IPv4 interface kube-ipvs0, 10.101.207.79#53
27-Oct-2025 01:41:51.895 network: info: listening on IPv6 interface tapeth0-08809d, fe80::9c94:78ff:fe02:1f3a%15#53
27-Oct-2025 01:41:51.902 network: info: listening on IPv6 interface tapeth0-d3bbe0, fe80::188c:5ff:fe64:61f0%17#53
27-Oct-2025 01:41:56.183 network: info: listening on IPv6 interface veth719e36ba-0, fe80::58ab:76ff:fe4e:f755%18#53
27-Oct-2025 01:42:01.173 network: info: listening on IPv6 interface tapeth0-1cf64b, fe80::a428:abff:fe47:eeff%20#53
27-Oct-2025 01:42:39.793 network: info: no longer listening on fe80::a428:abff:fe47:eeff%20#53
27-Oct-2025 01:42:47.339 network: info: no longer listening on fe80::58ab:76ff:fe4e:f755%18#53
27-Oct-2025 01:42:47.675 network: info: no longer listening on fe80::188c:5ff:fe64:61f0%17#53
27-Oct-2025 01:42:52.436 network: info: no longer listening on fe80::9c94:78ff:fe02:1f3a%15#53
27-Oct-2025 01:43:13.175 network: info: listening on IPv6 interface tapeth0-34feb9, fe80::e820:70ff:fe6d:6011%22#53
27-Oct-2025 01:43:13.176 network: info: listening on IPv6 interface tapeth0-10afc3, fe80::6014:c5ff:fe2c:a1f3%24#53
27-Oct-2025 01:43:13.176 network: info: listening on IPv6 interface tapeth0-d9884b, fe80::b5ff:fe6d:10fd%26#53
27-Oct-2025 01:43:18.614 network: info: listening on IPv6 interface tapeth0-27d930, fe80::f4ec:6dff:fea9:5955%28#53
27-Oct-2025 01:43:18.615 network: info: listening on IPv6 interface tapeth0-3a168c, fe80::ecda:b5ff:fed5:5120%30#53
27-Oct-2025 01:43:18.616 network: info: listening on IPv6 interface tapeth0-17daff, fe80::305b:32ff:fe8c:ba58%32#53
27-Oct-2025 01:43:23.798 network: info: listening on IPv6 interface tapeth0-589721, fe80::acc4:a2ff:fe41:45e4%34#53
27-Oct-2025 01:43:23.803 network: info: listening on IPv6 interface tapeth0-2f96e2, fe80::4eb:d0ff:fe3b:a5ea%36#53
27-Oct-2025 01:43:32.979 network: info: listening on IPv4 interface kube-ipvs0, 10.97.150.144#53
27-Oct-2025 01:46:44.859 network: info: no longer listening on fe80::6014:c5ff:fe2c:a1f3%24#53
27-Oct-2025 01:46:44.931 network: info: no longer listening on fe80::e820:70ff:fe6d:6011%22#53
27-Oct-2025 01:46:44.943 network: info: no longer listening on fe80::b5ff:fe6d:10fd%26#53
27-Oct-2025 01:46:44.944 network: info: no longer listening on fe80::305b:32ff:fe8c:ba58%32#53
27-Oct-2025 01:47:15.114 network: info: no longer listening on fe80::ecda:b5ff:fed5:5120%30#53
27-Oct-2025 01:47:15.150 network: info: no longer listening on fe80::f4ec:6dff:fea9:5955%28#53
27-Oct-2025 01:47:15.158 network: info: no longer listening on fe80::acc4:a2ff:fe41:45e4%34#53
27-Oct-2025 01:47:15.162 network: info: no longer listening on fe80::4eb:d0ff:fe3b:a5ea%36#53
27-Oct-2025 01:47:30.819 network: info: no longer listening on 10.97.150.144#53