30-Mar-2026 01:36:26.691 general: debug 1: now using logging configuration from config file
30-Mar-2026 01:36:26.691 general: debug 1: loop exclusive mode: ending
30-Mar-2026 01:36:26.691 general: debug 1: loop exclusive mode: ended
30-Mar-2026 01:36:26.692 general: notice: command channel listening on 127.0.0.1#8094
30-Mar-2026 01:36:26.693 general: info: VDNS cleanup pass1: 0 departing views cleared
30-Mar-2026 01:36:26.693 general: info: VDNS cleanup pass2: 2 staying views re-checked
30-Mar-2026 01:36:26.694 general: debug 1: load_configuration: success
30-Mar-2026 01:36:26.694 general: debug 1: loop exclusive mode: starting
30-Mar-2026 01:36:26.753 general: debug 1: loop exclusive mode: started
30-Mar-2026 01:36:26.753 zoneload: debug 1: managed-keys-zone: starting load
30-Mar-2026 01:36:26.753 general: debug 1: zone_startload: managed-keys-zone: enter
30-Mar-2026 01:36:26.753 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
30-Mar-2026 01:36:26.753 general: debug 1: managed-keys-zone: creating SOA
30-Mar-2026 01:36:26.756 zoneload: debug 1: managed-keys-zone: loaded; checking validity
30-Mar-2026 01:36:26.756 zoneload: info: managed-keys-zone: loaded serial 0
30-Mar-2026 01:36:26.756 general: debug 1: loop exclusive mode: ending
30-Mar-2026 01:36:26.756 zoneload: debug 1: zone hostname.bind/CH: starting load
30-Mar-2026 01:36:26.756 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
30-Mar-2026 01:36:26.756 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
30-Mar-2026 01:36:26.756 zoneload: debug 1: zone id.server/CH: starting load
30-Mar-2026 01:36:26.756 zoneload: debug 1: zone id.server/CH: loaded; checking validity
30-Mar-2026 01:36:26.756 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
30-Mar-2026 01:36:26.756 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
30-Mar-2026 01:36:26.756 general: debug 1: zone__settimer: zone id.server/CH: enter
30-Mar-2026 01:36:26.756 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
30-Mar-2026 01:36:26.756 general: debug 1: zone_maintenance: zone id.server/CH: enter
30-Mar-2026 01:36:26.756 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
30-Mar-2026 01:36:26.756 general: debug 1: zone__settimer: zone id.server/CH: enter
30-Mar-2026 01:36:26.756 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 01:36:26.756 zoneload: debug 1: zone authors.bind/CH: starting load
30-Mar-2026 01:36:26.756 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
30-Mar-2026 01:36:26.756 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
30-Mar-2026 01:36:26.756 general: debug 1: zone__settimer: zone authors.bind/CH: enter
30-Mar-2026 01:36:26.756 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
30-Mar-2026 01:36:26.757 general: debug 1: zone__settimer: zone authors.bind/CH: enter
30-Mar-2026 01:36:26.757 general: debug 1: loop exclusive mode: ended
30-Mar-2026 01:36:26.757 zoneload: debug 1: zone version.bind/CH: starting load
30-Mar-2026 01:36:26.757 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
30-Mar-2026 01:36:26.757 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
30-Mar-2026 01:36:26.757 general: notice: all zones loaded
30-Mar-2026 01:36:26.757 general: debug 1: managed-keys-zone: synchronizing trusted keys
30-Mar-2026 01:36:26.757 general: debug 1: create_keydata: managed-keys-zone: enter
30-Mar-2026 01:36:26.757 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
30-Mar-2026 01:36:26.757 general: debug 1: managed-keys-zone: next key refresh: 30-Mar-2026 01:36:26.757
30-Mar-2026 01:36:26.781 general: debug 1: zone_journal: managed-keys-zone: enter
30-Mar-2026 01:36:26.781 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
30-Mar-2026 01:36:26.783 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 01:36:26.796 general: debug 1: zone_needdump: managed-keys-zone: enter
30-Mar-2026 01:36:26.796 general: debug 1: zone_maintenance: managed-keys-zone: enter
30-Mar-2026 01:36:26.796 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
30-Mar-2026 01:36:26.796 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
30-Mar-2026 01:36:26.796 general: debug 1: managed-keys-zone: next key refresh: 30-Mar-2026 01:36:26.796
30-Mar-2026 01:36:26.796 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 01:36:26.796 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 01:36:26.796 resolver: debug 1: fetch: ./DNSKEY
30-Mar-2026 01:36:26.796 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 01:36:26.796 resolver: debug 1: fetch: ./NS
30-Mar-2026 01:36:26.796 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
30-Mar-2026 01:36:26.796 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
30-Mar-2026 01:36:26.796 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
30-Mar-2026 01:36:26.796 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
30-Mar-2026 01:36:26.796 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
30-Mar-2026 01:36:26.796 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
30-Mar-2026 01:36:26.796 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
30-Mar-2026 01:36:26.796 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
30-Mar-2026 01:36:26.797 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
30-Mar-2026 01:36:26.797 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
30-Mar-2026 01:36:26.797 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
30-Mar-2026 01:36:26.797 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
30-Mar-2026 01:36:26.797 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
30-Mar-2026 01:36:26.797 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
30-Mar-2026 01:36:26.797 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
30-Mar-2026 01:36:26.797 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
30-Mar-2026 01:36:26.797 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
30-Mar-2026 01:36:26.797 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
30-Mar-2026 01:36:26.797 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
30-Mar-2026 01:36:26.797 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
30-Mar-2026 01:36:26.797 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
30-Mar-2026 01:36:26.797 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
30-Mar-2026 01:36:26.797 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
30-Mar-2026 01:36:26.797 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
30-Mar-2026 01:36:26.797 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
30-Mar-2026 01:36:26.831 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 01:36:26.831 lame-servers: info: SERVFAIL unexpected RCODE resolving './NS/IN': 192.36.148.17#53
30-Mar-2026 01:36:26.831 lame-servers: info: SERVFAIL unexpected RCODE resolving './DNSKEY/IN': 192.36.148.17#53
30-Mar-2026 01:36:26.854 database: debug 1: delete_node(): 0x7f4544002220 . (bucket 2)
30-Mar-2026 01:36:26.854 resolver: debug 1: fetch: ./DNSKEY
30-Mar-2026 01:36:26.854 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
30-Mar-2026 01:36:26.854 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
30-Mar-2026 01:36:26.854 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
30-Mar-2026 01:36:26.855 general: notice: FIPS mode is disabled
30-Mar-2026 01:36:26.855 general: notice: running
30-Mar-2026 01:36:26.855 general: debug 1: debug: t1-cloud-fixed version
30-Mar-2026 01:36:26.855 general: debug 1: zone__settimer: zone version.bind/CH: enter
30-Mar-2026 01:36:26.855 general: debug 1: zone__settimer: zone version.bind/CH: enter
30-Mar-2026 01:36:26.855 general: debug 1: zone_maintenance: zone version.bind/CH: enter
30-Mar-2026 01:36:26.855 general: debug 1: zone__settimer: zone version.bind/CH: enter
30-Mar-2026 01:36:26.855 general: debug 1: zone__settimer: zone authors.bind/CH: enter
30-Mar-2026 01:36:26.855 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
30-Mar-2026 01:36:26.855 general: debug 1: zone__settimer: zone id.server/CH: enter
30-Mar-2026 01:36:26.874 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.
30-Mar-2026 01:36:26.875 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
30-Mar-2026 01:36:26.875 general: debug 1: managed-keys-zone: next key refresh: 31-Mar-2026 01:36:26.875
30-Mar-2026 01:36:26.875 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.
30-Mar-2026 01:36:26.875 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
30-Mar-2026 01:36:26.875 general: debug 1: managed-keys-zone: next key refresh: 31-Mar-2026 01:36:26.875
30-Mar-2026 01:36:26.875 general: debug 1: zone_journal: managed-keys-zone: enter
30-Mar-2026 01:36:26.898 general: debug 1: zone_needdump: managed-keys-zone: enter
30-Mar-2026 01:36:26.898 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 01:36:26.898 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 01:36:26.898 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 01:36:27.025 resolver: debug 1: resolver priming query complete: success
30-Mar-2026 01:36:54.927 general: debug 1: zone_maintenance: managed-keys-zone: enter
30-Mar-2026 01:36:54.927 general: debug 1: zone_dump: managed-keys-zone: enter
30-Mar-2026 01:36:54.929 general: debug 1: zone__settimer: managed-keys-zone: enter
30-Mar-2026 01:36:54.933 general: debug 1: dump_done: managed-keys-zone: enter
30-Mar-2026 01:36:54.933 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
30-Mar-2026 01:37:18.752 network: info: listening on IPv6 interface tapeth0-e8d2c4, fe80::e896:4dff:fea5:c419%11#53
30-Mar-2026 01:37:20.992 network: info: listening on IPv6 interface tapeth0-e4a04b, fe80::584b:2ff:fe33:2fb0%13#53
30-Mar-2026 01:38:32.454 network: info: listening on IPv4 interface kube-ipvs0, 10.102.215.188#53
30-Mar-2026 01:38:40.032 network: info: listening on IPv6 interface tapeth0-ce6df8, fe80::a46c:c1ff:fec2:2d89%15#53
30-Mar-2026 01:38:40.062 network: info: listening on IPv6 interface tapeth0-d56d13, fe80::f430:10ff:fe1f:8056%17#53
30-Mar-2026 01:38:44.896 network: info: listening on IPv6 interface vethebf1b330-9, fe80::4c65:8bff:fe6e:9f68%18#53
30-Mar-2026 01:38:50.335 network: info: listening on IPv6 interface tapeth0-f0ab12, fe80::b0f8:43ff:fe8e:3e0a%20#53
30-Mar-2026 01:39:28.151 network: info: no longer listening on fe80::b0f8:43ff:fe8e:3e0a%20#53
30-Mar-2026 01:39:34.863 network: info: no longer listening on fe80::4c65:8bff:fe6e:9f68%18#53
30-Mar-2026 01:39:35.981 network: info: no longer listening on fe80::f430:10ff:fe1f:8056%17#53
30-Mar-2026 01:39:40.873 network: info: no longer listening on fe80::a46c:c1ff:fec2:2d89%15#53
30-Mar-2026 01:40:00.479 network: info: listening on IPv6 interface tapeth0-02eb5a, fe80::c98:1dff:fec6:18ae%22#53
30-Mar-2026 01:40:03.807 network: info: listening on IPv6 interface tapeth0-5c04ba, fe80::84cd:54ff:fe2b:f80%24#53
30-Mar-2026 01:40:03.812 network: info: listening on IPv6 interface tapeth0-d60edc, fe80::5c9e:adff:fedc:a6a4%26#53
30-Mar-2026 01:40:03.812 network: info: listening on IPv6 interface tapeth0-54ccc7, fe80::9475:28ff:fec4:9522%28#53
30-Mar-2026 01:40:03.813 network: info: listening on IPv6 interface tapeth0-71083b, fe80::4076:eeff:fed4:3254%30#53
30-Mar-2026 01:40:09.119 network: info: listening on IPv6 interface tapeth0-72316e, fe80::3885:8eff:fe3b:ba08%32#53
30-Mar-2026 01:40:09.121 network: info: listening on IPv6 interface tapeth0-71837a, fe80::e4fe:1bff:fe43:2168%34#53
30-Mar-2026 01:40:09.122 network: info: listening on IPv6 interface tapeth0-939793, fe80::ca2:b7ff:fe6f:1190%36#53
30-Mar-2026 01:40:18.549 network: info: listening on IPv4 interface kube-ipvs0, 10.108.149.61#53
30-Mar-2026 01:43:27.861 network: info: no longer listening on fe80::84cd:54ff:fe2b:f80%24#53
30-Mar-2026 01:43:27.888 network: info: no longer listening on fe80::9475:28ff:fec4:9522%28#53
30-Mar-2026 01:43:27.916 network: info: no longer listening on fe80::5c9e:adff:fedc:a6a4%26#53
30-Mar-2026 01:43:27.932 network: info: no longer listening on fe80::c98:1dff:fec6:18ae%22#53
30-Mar-2026 01:43:58.337 network: info: no longer listening on fe80::ca2:b7ff:fe6f:1190%36#53
30-Mar-2026 01:43:58.364 network: info: no longer listening on fe80::3885:8eff:fe3b:ba08%32#53
30-Mar-2026 01:43:58.379 network: info: no longer listening on fe80::4076:eeff:fed4:3254%30#53
30-Mar-2026 01:43:58.397 network: info: no longer listening on fe80::e4fe:1bff:fe43:2168%34#53
30-Mar-2026 01:44:14.000 network: info: no longer listening on 10.108.149.61#53