26-Oct-2026 01:48:29.921 general: debug 1: now using logging configuration from config file
26-Oct-2026 01:48:29.921 general: debug 1: loop exclusive mode: ending
26-Oct-2026 01:48:29.921 general: debug 1: loop exclusive mode: ended
26-Oct-2026 01:48:29.921 general: notice: command channel listening on 127.0.0.1#8094
26-Oct-2026 01:48:29.921 general: info: VDNS cleanup pass1: 0 departing views cleared
26-Oct-2026 01:48:29.921 general: info: VDNS cleanup pass2: 2 staying views re-checked
26-Oct-2026 01:48:29.921 general: debug 1: load_configuration: success
26-Oct-2026 01:48:29.921 general: debug 1: loop exclusive mode: starting
26-Oct-2026 01:48:29.944 general: debug 1: loop exclusive mode: started
26-Oct-2026 01:48:29.944 zoneload: debug 1: managed-keys-zone: starting load
26-Oct-2026 01:48:29.944 general: debug 1: zone_startload: managed-keys-zone: enter
26-Oct-2026 01:48:29.944 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
26-Oct-2026 01:48:29.944 general: debug 1: managed-keys-zone: creating SOA
26-Oct-2026 01:48:29.944 zoneload: debug 1: managed-keys-zone: loaded; checking validity
26-Oct-2026 01:48:29.944 zoneload: info: managed-keys-zone: loaded serial 0
26-Oct-2026 01:48:29.944 general: debug 1: loop exclusive mode: ending
26-Oct-2026 01:48:29.944 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Oct-2026 01:48:29.944 zoneload: debug 1: zone hostname.bind/CH: starting load
26-Oct-2026 01:48:29.944 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
26-Oct-2026 01:48:29.944 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
26-Oct-2026 01:48:29.944 zoneload: debug 1: zone version.bind/CH: starting load
26-Oct-2026 01:48:29.944 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
26-Oct-2026 01:48:29.944 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
26-Oct-2026 01:48:29.944 zoneload: debug 1: zone id.server/CH: starting load
26-Oct-2026 01:48:29.944 zoneload: debug 1: zone id.server/CH: loaded; checking validity
26-Oct-2026 01:48:29.944 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
26-Oct-2026 01:48:29.944 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
26-Oct-2026 01:48:29.944 general: debug 1: zone__settimer: zone version.bind/CH: enter
26-Oct-2026 01:48:29.944 general: debug 1: zone__settimer: zone id.server/CH: enter
26-Oct-2026 01:48:29.944 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
26-Oct-2026 01:48:29.944 general: debug 1: zone_maintenance: zone version.bind/CH: enter
26-Oct-2026 01:48:29.944 general: debug 1: zone_maintenance: zone id.server/CH: enter
26-Oct-2026 01:48:29.944 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
26-Oct-2026 01:48:29.944 general: debug 1: zone__settimer: zone version.bind/CH: enter
26-Oct-2026 01:48:29.944 general: debug 1: zone__settimer: zone id.server/CH: enter
26-Oct-2026 01:48:29.945 zoneload: debug 1: zone authors.bind/CH: starting load
26-Oct-2026 01:48:29.945 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
26-Oct-2026 01:48:29.945 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
26-Oct-2026 01:48:29.945 general: notice: all zones loaded
26-Oct-2026 01:48:29.945 general: debug 1: managed-keys-zone: synchronizing trusted keys
26-Oct-2026 01:48:29.945 general: debug 1: create_keydata: managed-keys-zone: enter
26-Oct-2026 01:48:29.945 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
26-Oct-2026 01:48:29.945 general: debug 1: managed-keys-zone: next key refresh: 26-Oct-2026 01:48:29.945
26-Oct-2026 01:48:29.945 general: debug 1: zone_journal: managed-keys-zone: enter
26-Oct-2026 01:48:29.945 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
26-Oct-2026 01:48:29.945 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Oct-2026 01:48:29.945 general: debug 1: loop exclusive mode: ended
26-Oct-2026 01:48:29.954 general: debug 1: zone_needdump: managed-keys-zone: enter
26-Oct-2026 01:48:29.954 general: notice: FIPS mode is disabled
26-Oct-2026 01:48:29.954 general: notice: running
26-Oct-2026 01:48:29.954 general: debug 1: debug: t1-cloud-fixed version
26-Oct-2026 01:48:29.954 general: debug 1: zone__settimer: zone authors.bind/CH: enter
26-Oct-2026 01:48:29.954 general: debug 1: zone__settimer: zone authors.bind/CH: enter
26-Oct-2026 01:48:29.954 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
26-Oct-2026 01:48:29.954 general: debug 1: zone__settimer: zone authors.bind/CH: enter
26-Oct-2026 01:48:29.954 general: debug 1: zone_maintenance: managed-keys-zone: enter
26-Oct-2026 01:48:29.954 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
26-Oct-2026 01:48:29.954 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
26-Oct-2026 01:48:29.954 general: debug 1: managed-keys-zone: next key refresh: 26-Oct-2026 01:48:29.954
26-Oct-2026 01:48:29.954 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Oct-2026 01:48:29.954 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Oct-2026 01:48:29.954 general: debug 1: zone__settimer: zone version.bind/CH: enter
26-Oct-2026 01:48:29.954 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
26-Oct-2026 01:48:29.954 general: debug 1: zone__settimer: zone id.server/CH: enter
26-Oct-2026 01:48:29.954 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Oct-2026 01:48:29.954 resolver: debug 1: fetch: ./DNSKEY
26-Oct-2026 01:48:29.954 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Oct-2026 01:48:29.954 resolver: debug 1: fetch: ./NS
26-Oct-2026 01:48:29.954 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
26-Oct-2026 01:48:29.955 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
26-Oct-2026 01:48:29.956 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
26-Oct-2026 01:48:30.004 database: debug 1: delete_node(): 0x1117d70 . (bucket 1)
26-Oct-2026 01:48:30.004 resolver: debug 1: fetch: ./DNSKEY
26-Oct-2026 01:48:30.004 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
26-Oct-2026 01:48:30.004 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
26-Oct-2026 01:48:30.004 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
26-Oct-2026 01:48:30.004 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
26-Oct-2026 01:48:30.026 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.
26-Oct-2026 01:48:30.026 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
26-Oct-2026 01:48:30.026 general: debug 1: managed-keys-zone: next key refresh: 27-Oct-2026 01:48:30.026
26-Oct-2026 01:48:30.026 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.
26-Oct-2026 01:48:30.026 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
26-Oct-2026 01:48:30.026 general: debug 1: managed-keys-zone: next key refresh: 27-Oct-2026 01:48:30.026
26-Oct-2026 01:48:30.026 general: debug 1: zone_journal: managed-keys-zone: enter
26-Oct-2026 01:48:30.046 general: debug 1: zone_needdump: managed-keys-zone: enter
26-Oct-2026 01:48:30.056 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Oct-2026 01:48:30.056 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Oct-2026 01:48:30.056 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Oct-2026 01:48:30.123 resolver: debug 1: resolver priming query complete: success
26-Oct-2026 01:48:55.082 general: debug 1: zone_maintenance: managed-keys-zone: enter
26-Oct-2026 01:48:55.082 general: debug 1: zone_dump: managed-keys-zone: enter
26-Oct-2026 01:48:55.082 general: debug 1: zone__settimer: managed-keys-zone: enter
26-Oct-2026 01:48:55.084 general: debug 1: dump_done: managed-keys-zone: enter
26-Oct-2026 01:48:55.085 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
26-Oct-2026 01:49:17.643 network: info: listening on IPv6 interface tapeth0-c91773, fe80::781b:6dff:fefe:cb89%11#53
26-Oct-2026 01:49:22.827 network: info: listening on IPv6 interface tapeth0-09f1b6, fe80::d0b7:c6ff:fe6c:c83a%13#53
26-Oct-2026 01:50:41.265 network: info: listening on IPv4 interface kube-ipvs0, 10.98.30.137#53
26-Oct-2026 01:50:48.330 network: info: listening on IPv6 interface tapeth0-81d570, fe80::a8b4:d1ff:feb6:58a9%15#53
26-Oct-2026 01:50:48.335 network: info: listening on IPv6 interface tapeth0-ce3231, fe80::48e7:43ff:fe11:b5d3%17#53
26-Oct-2026 01:50:51.923 network: info: listening on IPv6 interface veth9bb3d199-b, fe80::7ce8:ebff:fef3:92a3%18#53
26-Oct-2026 01:50:57.035 network: info: listening on IPv6 interface tapeth0-92f07b, fe80::f481:91ff:feb9:7e58%20#53
26-Oct-2026 01:51:35.283 network: info: no longer listening on fe80::f481:91ff:feb9:7e58%20#53
26-Oct-2026 01:51:42.591 network: info: no longer listening on fe80::7ce8:ebff:fef3:92a3%18#53
26-Oct-2026 01:51:43.587 network: info: no longer listening on fe80::a8b4:d1ff:feb6:58a9%15#53
26-Oct-2026 01:51:48.417 network: info: no longer listening on fe80::48e7:43ff:fe11:b5d3%17#53
26-Oct-2026 01:52:08.779 network: info: listening on IPv6 interface tapeth0-a26d95, fe80::f0a2:35ff:fec3:1424%22#53
26-Oct-2026 01:52:08.783 network: info: listening on IPv6 interface tapeth0-ded1bb, fe80::c440:8dff:fe9f:a737%24#53
26-Oct-2026 01:52:13.386 network: info: listening on IPv6 interface tapeth0-442518, fe80::509c:e8ff:fe5a:738a%26#53
26-Oct-2026 01:52:13.394 network: info: listening on IPv6 interface tapeth0-a70e9b, fe80::785e:70ff:fefc:9a69%28#53
26-Oct-2026 01:52:13.396 network: info: listening on IPv6 interface tapeth0-5dc26f, fe80::60ce:d6ff:fe93:9321%30#53
26-Oct-2026 01:52:13.397 network: info: listening on IPv6 interface tapeth0-88d2b1, fe80::d9:26ff:fe4b:920f%32#53
26-Oct-2026 01:52:18.634 network: info: listening on IPv6 interface tapeth0-2808df, fe80::d8e9:29ff:fe66:696d%34#53
26-Oct-2026 01:52:18.635 network: info: listening on IPv6 interface tapeth0-83755a, fe80::581a:97ff:fee7:a8e%36#53
26-Oct-2026 01:52:27.885 network: info: listening on IPv4 interface kube-ipvs0, 10.100.180.201#53
26-Oct-2026 01:55:37.646 network: info: no longer listening on fe80::d9:26ff:fe4b:920f%32#53
26-Oct-2026 01:55:37.707 network: info: no longer listening on fe80::f0a2:35ff:fec3:1424%22#53
26-Oct-2026 01:55:37.709 network: info: no longer listening on fe80::785e:70ff:fefc:9a69%28#53
26-Oct-2026 01:55:37.716 network: info: no longer listening on fe80::c440:8dff:fe9f:a737%24#53
26-Oct-2026 01:56:07.664 network: info: no longer listening on fe80::d8e9:29ff:fe66:696d%34#53
26-Oct-2026 01:56:07.673 network: info: no longer listening on fe80::581a:97ff:fee7:a8e%36#53
26-Oct-2026 01:56:07.692 network: info: no longer listening on fe80::509c:e8ff:fe5a:738a%26#53
26-Oct-2026 01:56:07.693 network: info: no longer listening on fe80::60ce:d6ff:fe93:9321%30#53
26-Oct-2026 01:56:23.753 network: info: no longer listening on 10.100.180.201#53