02-Apr-2026 01:39:38.537 general: debug 1: now using logging configuration from config file
02-Apr-2026 01:39:38.537 general: debug 1: loop exclusive mode: ending
02-Apr-2026 01:39:38.537 general: debug 1: loop exclusive mode: ended
02-Apr-2026 01:39:38.537 general: notice: command channel listening on 127.0.0.1#8094
02-Apr-2026 01:39:38.537 general: info: VDNS cleanup pass1: 0 departing views cleared
02-Apr-2026 01:39:38.537 general: info: VDNS cleanup pass2: 2 staying views re-checked
02-Apr-2026 01:39:38.537 general: debug 1: load_configuration: success
02-Apr-2026 01:39:38.537 general: debug 1: loop exclusive mode: starting
02-Apr-2026 01:39:38.563 general: debug 1: loop exclusive mode: started
02-Apr-2026 01:39:38.563 zoneload: debug 1: managed-keys-zone: starting load
02-Apr-2026 01:39:38.563 general: debug 1: zone_startload: managed-keys-zone: enter
02-Apr-2026 01:39:38.563 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
02-Apr-2026 01:39:38.563 general: debug 1: managed-keys-zone: creating SOA
02-Apr-2026 01:39:38.563 zoneload: debug 1: managed-keys-zone: loaded; checking validity
02-Apr-2026 01:39:38.563 zoneload: info: managed-keys-zone: loaded serial 0
02-Apr-2026 01:39:38.563 general: debug 1: loop exclusive mode: ending
02-Apr-2026 01:39:38.566 zoneload: debug 1: zone id.server/CH: starting load
02-Apr-2026 01:39:38.566 zoneload: debug 1: zone id.server/CH: loaded; checking validity
02-Apr-2026 01:39:38.566 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
02-Apr-2026 01:39:38.566 general: debug 1: zone__settimer: zone id.server/CH: enter
02-Apr-2026 01:39:38.566 general: debug 1: zone_maintenance: zone id.server/CH: enter
02-Apr-2026 01:39:38.566 general: debug 1: zone__settimer: zone id.server/CH: enter
02-Apr-2026 01:39:38.567 general: debug 1: loop exclusive mode: ended
02-Apr-2026 01:39:38.567 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Apr-2026 01:39:38.567 zoneload: debug 1: zone authors.bind/CH: starting load
02-Apr-2026 01:39:38.567 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
02-Apr-2026 01:39:38.567 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
02-Apr-2026 01:39:38.567 zoneload: debug 1: zone hostname.bind/CH: starting load
02-Apr-2026 01:39:38.567 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
02-Apr-2026 01:39:38.567 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
02-Apr-2026 01:39:38.567 zoneload: debug 1: zone version.bind/CH: starting load
02-Apr-2026 01:39:38.567 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
02-Apr-2026 01:39:38.567 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
02-Apr-2026 01:39:38.567 general: notice: all zones loaded
02-Apr-2026 01:39:38.567 general: debug 1: managed-keys-zone: synchronizing trusted keys
02-Apr-2026 01:39:38.567 general: debug 1: create_keydata: managed-keys-zone: enter
02-Apr-2026 01:39:38.568 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
02-Apr-2026 01:39:38.568 general: debug 1: managed-keys-zone: next key refresh: 02-Apr-2026 01:39:38.568
02-Apr-2026 01:39:38.568 general: debug 1: zone_journal: managed-keys-zone: enter
02-Apr-2026 01:39:38.568 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
02-Apr-2026 01:39:38.596 general: debug 1: zone_needdump: managed-keys-zone: enter
02-Apr-2026 01:39:38.610 general: notice: FIPS mode is disabled
02-Apr-2026 01:39:38.610 general: notice: running
02-Apr-2026 01:39:38.610 general: debug 1: debug: t1-cloud-fixed version
02-Apr-2026 01:39:38.610 general: debug 1: zone__settimer: zone authors.bind/CH: enter
02-Apr-2026 01:39:38.611 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
02-Apr-2026 01:39:38.611 general: debug 1: zone__settimer: zone id.server/CH: enter
02-Apr-2026 01:39:38.611 general: debug 1: zone__settimer: zone version.bind/CH: enter
02-Apr-2026 01:39:38.611 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Apr-2026 01:39:38.611 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Apr-2026 01:39:38.611 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Apr-2026 01:39:38.611 general: debug 1: zone__settimer: zone version.bind/CH: enter
02-Apr-2026 01:39:38.611 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
02-Apr-2026 01:39:38.611 general: debug 1: zone__settimer: zone authors.bind/CH: enter
02-Apr-2026 01:39:38.611 general: debug 1: zone_maintenance: managed-keys-zone: enter
02-Apr-2026 01:39:38.611 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
02-Apr-2026 01:39:38.611 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
02-Apr-2026 01:39:38.611 general: debug 1: managed-keys-zone: next key refresh: 02-Apr-2026 01:39:38.611
02-Apr-2026 01:39:38.611 general: debug 1: zone_maintenance: zone version.bind/CH: enter
02-Apr-2026 01:39:38.611 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
02-Apr-2026 01:39:38.611 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
02-Apr-2026 01:39:38.611 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Apr-2026 01:39:38.611 resolver: debug 1: fetch: ./DNSKEY
02-Apr-2026 01:39:38.611 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Apr-2026 01:39:38.611 general: debug 1: zone__settimer: zone version.bind/CH: enter
02-Apr-2026 01:39:38.611 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
02-Apr-2026 01:39:38.611 general: debug 1: zone__settimer: zone authors.bind/CH: enter
02-Apr-2026 01:39:38.611 resolver: debug 1: fetch: ./NS
02-Apr-2026 01:39:38.611 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
02-Apr-2026 01:39:38.611 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
02-Apr-2026 01:39:38.611 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
02-Apr-2026 01:39:38.611 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
02-Apr-2026 01:39:38.611 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
02-Apr-2026 01:39:38.611 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
02-Apr-2026 01:39:38.611 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
02-Apr-2026 01:39:38.611 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
02-Apr-2026 01:39:38.611 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
02-Apr-2026 01:39:38.611 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
02-Apr-2026 01:39:38.611 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
02-Apr-2026 01:39:38.611 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
02-Apr-2026 01:39:38.611 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
02-Apr-2026 01:39:38.611 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
02-Apr-2026 01:39:38.611 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
02-Apr-2026 01:39:38.612 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
02-Apr-2026 01:39:38.612 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
02-Apr-2026 01:39:38.612 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
02-Apr-2026 01:39:38.612 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
02-Apr-2026 01:39:38.612 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
02-Apr-2026 01:39:38.612 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
02-Apr-2026 01:39:38.612 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
02-Apr-2026 01:39:38.612 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
02-Apr-2026 01:39:38.612 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
02-Apr-2026 01:39:38.612 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
02-Apr-2026 01:39:38.671 database: debug 1: delete_node(): 0xbc6110 . (bucket 0)
02-Apr-2026 01:39:38.672 resolver: debug 1: fetch: ./DNSKEY
02-Apr-2026 01:39:38.672 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
02-Apr-2026 01:39:38.692 database: debug 1: delete_node(): 0xd9b070 . (bucket 3)
02-Apr-2026 01:39:38.750 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.
02-Apr-2026 01:39:38.750 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
02-Apr-2026 01:39:38.750 general: debug 1: managed-keys-zone: next key refresh: 03-Apr-2026 01:39:38.750
02-Apr-2026 01:39:38.750 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.
02-Apr-2026 01:39:38.750 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
02-Apr-2026 01:39:38.750 general: debug 1: managed-keys-zone: next key refresh: 03-Apr-2026 01:39:38.750
02-Apr-2026 01:39:38.750 general: debug 1: zone_journal: managed-keys-zone: enter
02-Apr-2026 01:39:38.764 general: debug 1: zone_needdump: managed-keys-zone: enter
02-Apr-2026 01:39:38.770 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Apr-2026 01:39:38.770 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Apr-2026 01:39:38.770 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Apr-2026 01:39:38.770 resolver: debug 1: resolver priming query complete: success
02-Apr-2026 01:40:06.628 general: debug 1: zone_maintenance: managed-keys-zone: enter
02-Apr-2026 01:40:06.628 general: debug 1: zone_dump: managed-keys-zone: enter
02-Apr-2026 01:40:06.633 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Apr-2026 01:40:06.637 general: debug 1: dump_done: managed-keys-zone: enter
02-Apr-2026 01:40:06.637 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
02-Apr-2026 01:40:34.296 network: info: listening on IPv6 interface tapeth0-dbe445, fe80::94b5:a5ff:fe86:2e76%11#53
02-Apr-2026 01:40:43.192 network: info: listening on IPv6 interface tapeth0-b4b855, fe80::8051:66ff:feaa:2a0e%13#53
02-Apr-2026 01:42:21.964 network: info: listening on IPv4 interface kube-ipvs0, 10.109.52.108#53
02-Apr-2026 01:42:30.327 network: info: listening on IPv6 interface tapeth0-fadff0, fe80::7433:68ff:fe0d:ea2e%15#53
02-Apr-2026 01:42:30.332 network: info: listening on IPv6 interface tapeth0-b5454b, fe80::824:48ff:fe39:39e8%17#53
02-Apr-2026 01:42:34.744 network: info: listening on IPv6 interface veth1aac81ff-2, fe80::9445:21ff:fe70:4904%18#53
02-Apr-2026 01:42:43.959 network: info: listening on IPv6 interface tapeth0-6b6292, fe80::4cf:5dff:fe2f:d066%20#53
02-Apr-2026 01:43:22.115 network: info: no longer listening on fe80::4cf:5dff:fe2f:d066%20#53
02-Apr-2026 01:43:29.501 network: info: no longer listening on fe80::9445:21ff:fe70:4904%18#53
02-Apr-2026 01:43:30.852 network: info: no longer listening on fe80::7433:68ff:fe0d:ea2e%15#53
02-Apr-2026 01:43:35.628 network: info: no longer listening on fe80::824:48ff:fe39:39e8%17#53
02-Apr-2026 01:43:55.766 network: info: listening on IPv6 interface tapeth0-ca8f33, fe80::b415:12ff:fed3:648f%22#53
02-Apr-2026 01:43:55.768 network: info: listening on IPv6 interface tapeth0-ab4022, fe80::cc5d:caff:fe13:522a%24#53
02-Apr-2026 01:44:01.272 network: info: listening on IPv6 interface tapeth0-6106e1, fe80::44d:4fff:fe75:10e8%26#53
02-Apr-2026 01:44:01.275 network: info: listening on IPv6 interface tapeth0-754273, fe80::d8bc:24ff:fee8:e5f9%28#53
02-Apr-2026 01:44:01.280 network: info: listening on IPv6 interface tapeth0-31864b, fe80::4484:96ff:fe40:f852%30#53
02-Apr-2026 01:44:05.942 network: info: listening on IPv6 interface tapeth0-c215f8, fe80::48b0:4fff:fec4:1b91%32#53
02-Apr-2026 01:44:05.945 network: info: listening on IPv6 interface tapeth0-ce4c25, fe80::8bb:7fff:fe3b:3c43%34#53
02-Apr-2026 01:44:05.946 network: info: listening on IPv6 interface tapeth0-c9052d, fe80::fe:95ff:fe3d:7a54%36#53
02-Apr-2026 01:44:16.962 network: info: listening on IPv4 interface kube-ipvs0, 10.102.4.78#53
02-Apr-2026 01:47:31.767 network: info: no longer listening on fe80::cc5d:caff:fe13:522a%24#53
02-Apr-2026 01:47:31.776 network: info: no longer listening on fe80::d8bc:24ff:fee8:e5f9%28#53
02-Apr-2026 01:47:31.805 network: info: no longer listening on fe80::b415:12ff:fed3:648f%22#53
02-Apr-2026 01:47:31.813 network: info: no longer listening on fe80::44d:4fff:fe75:10e8%26#53
02-Apr-2026 01:48:01.779 network: info: no longer listening on fe80::48b0:4fff:fec4:1b91%32#53
02-Apr-2026 01:48:01.786 network: info: no longer listening on fe80::8bb:7fff:fe3b:3c43%34#53
02-Apr-2026 01:48:01.830 network: info: no longer listening on fe80::fe:95ff:fe3d:7a54%36#53
02-Apr-2026 01:48:01.880 network: info: no longer listening on fe80::4484:96ff:fe40:f852%30#53
02-Apr-2026 01:48:17.310 network: info: no longer listening on 10.102.4.78#53