04-Jun-2026 01:56:59.481 general: debug 1: now using logging configuration from config file
04-Jun-2026 01:56:59.481 general: debug 1: loop exclusive mode: ending
04-Jun-2026 01:56:59.485 general: debug 1: loop exclusive mode: ended
04-Jun-2026 01:56:59.485 general: notice: command channel listening on 127.0.0.1#8094
04-Jun-2026 01:56:59.485 general: info: VDNS cleanup pass1: 0 departing views cleared
04-Jun-2026 01:56:59.485 general: info: VDNS cleanup pass2: 2 staying views re-checked
04-Jun-2026 01:56:59.485 general: debug 1: load_configuration: success
04-Jun-2026 01:56:59.485 general: debug 1: loop exclusive mode: starting
04-Jun-2026 01:56:59.518 general: debug 1: loop exclusive mode: started
04-Jun-2026 01:56:59.518 zoneload: debug 1: managed-keys-zone: starting load
04-Jun-2026 01:56:59.518 general: debug 1: zone_startload: managed-keys-zone: enter
04-Jun-2026 01:56:59.518 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
04-Jun-2026 01:56:59.518 general: debug 1: managed-keys-zone: creating SOA
04-Jun-2026 01:56:59.518 zoneload: debug 1: managed-keys-zone: loaded; checking validity
04-Jun-2026 01:56:59.518 zoneload: info: managed-keys-zone: loaded serial 0
04-Jun-2026 01:56:59.518 general: debug 1: loop exclusive mode: ending
04-Jun-2026 01:56:59.518 general: debug 1: zone__settimer: managed-keys-zone: enter
04-Jun-2026 01:56:59.518 zoneload: debug 1: zone authors.bind/CH: starting load
04-Jun-2026 01:56:59.518 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
04-Jun-2026 01:56:59.518 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
04-Jun-2026 01:56:59.518 zoneload: debug 1: zone hostname.bind/CH: starting load
04-Jun-2026 01:56:59.518 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
04-Jun-2026 01:56:59.518 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
04-Jun-2026 01:56:59.518 general: debug 1: zone__settimer: zone authors.bind/CH: enter
04-Jun-2026 01:56:59.518 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
04-Jun-2026 01:56:59.518 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
04-Jun-2026 01:56:59.518 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
04-Jun-2026 01:56:59.518 general: debug 1: zone__settimer: zone authors.bind/CH: enter
04-Jun-2026 01:56:59.518 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
04-Jun-2026 01:56:59.518 zoneload: debug 1: zone version.bind/CH: starting load
04-Jun-2026 01:56:59.518 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
04-Jun-2026 01:56:59.518 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
04-Jun-2026 01:56:59.518 general: debug 1: zone__settimer: zone version.bind/CH: enter
04-Jun-2026 01:56:59.518 general: debug 1: zone_maintenance: zone version.bind/CH: enter
04-Jun-2026 01:56:59.518 general: debug 1: zone__settimer: zone version.bind/CH: enter
04-Jun-2026 01:56:59.518 zoneload: debug 1: zone id.server/CH: starting load
04-Jun-2026 01:56:59.518 zoneload: debug 1: zone id.server/CH: loaded; checking validity
04-Jun-2026 01:56:59.518 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
04-Jun-2026 01:56:59.518 general: notice: all zones loaded
04-Jun-2026 01:56:59.518 general: debug 1: managed-keys-zone: synchronizing trusted keys
04-Jun-2026 01:56:59.518 general: debug 1: create_keydata: managed-keys-zone: enter
04-Jun-2026 01:56:59.518 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
04-Jun-2026 01:56:59.518 general: debug 1: managed-keys-zone: next key refresh: 04-Jun-2026 01:56:59.518
04-Jun-2026 01:56:59.518 general: debug 1: zone_journal: managed-keys-zone: enter
04-Jun-2026 01:56:59.518 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
04-Jun-2026 01:56:59.518 general: debug 1: zone__settimer: managed-keys-zone: enter
04-Jun-2026 01:56:59.518 general: debug 1: loop exclusive mode: ended
04-Jun-2026 01:56:59.557 general: debug 1: zone_needdump: managed-keys-zone: enter
04-Jun-2026 01:56:59.557 general: notice: FIPS mode is disabled
04-Jun-2026 01:56:59.557 general: notice: running
04-Jun-2026 01:56:59.557 general: debug 1: debug: t1-cloud-fixed version
04-Jun-2026 01:56:59.557 general: debug 1: zone__settimer: zone id.server/CH: enter
04-Jun-2026 01:56:59.557 general: debug 1: zone__settimer: zone id.server/CH: enter
04-Jun-2026 01:56:59.557 general: debug 1: zone_maintenance: zone id.server/CH: enter
04-Jun-2026 01:56:59.557 general: debug 1: zone__settimer: zone id.server/CH: enter
04-Jun-2026 01:56:59.557 general: debug 1: zone__settimer: zone version.bind/CH: enter
04-Jun-2026 01:56:59.557 general: debug 1: zone_maintenance: managed-keys-zone: enter
04-Jun-2026 01:56:59.557 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
04-Jun-2026 01:56:59.557 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
04-Jun-2026 01:56:59.557 general: debug 1: managed-keys-zone: next key refresh: 04-Jun-2026 01:56:59.557
04-Jun-2026 01:56:59.557 general: debug 1: zone__settimer: managed-keys-zone: enter
04-Jun-2026 01:56:59.557 general: debug 1: zone__settimer: managed-keys-zone: enter
04-Jun-2026 01:56:59.557 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
04-Jun-2026 01:56:59.557 general: debug 1: zone__settimer: zone authors.bind/CH: enter
04-Jun-2026 01:56:59.557 general: debug 1: zone__settimer: managed-keys-zone: enter
04-Jun-2026 01:56:59.557 resolver: debug 1: fetch: ./DNSKEY
04-Jun-2026 01:56:59.557 general: debug 1: zone__settimer: managed-keys-zone: enter
04-Jun-2026 01:56:59.557 resolver: debug 1: fetch: ./NS
04-Jun-2026 01:56:59.558 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
04-Jun-2026 01:56:59.558 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
04-Jun-2026 01:56:59.558 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
04-Jun-2026 01:56:59.558 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
04-Jun-2026 01:56:59.558 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
04-Jun-2026 01:56:59.558 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
04-Jun-2026 01:56:59.558 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
04-Jun-2026 01:56:59.558 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
04-Jun-2026 01:56:59.558 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
04-Jun-2026 01:56:59.558 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
04-Jun-2026 01:56:59.558 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
04-Jun-2026 01:56:59.558 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
04-Jun-2026 01:56:59.558 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
04-Jun-2026 01:56:59.558 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
04-Jun-2026 01:56:59.558 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
04-Jun-2026 01:56:59.559 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
04-Jun-2026 01:56:59.559 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
04-Jun-2026 01:56:59.559 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
04-Jun-2026 01:56:59.559 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
04-Jun-2026 01:56:59.559 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
04-Jun-2026 01:56:59.559 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
04-Jun-2026 01:56:59.559 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
04-Jun-2026 01:56:59.559 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
04-Jun-2026 01:56:59.559 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
04-Jun-2026 01:56:59.559 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
04-Jun-2026 01:56:59.604 database: debug 1: delete_node(): 0x7f7660002220 . (bucket 3)
04-Jun-2026 01:56:59.604 resolver: debug 1: fetch: ./DNSKEY
04-Jun-2026 01:56:59.604 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
04-Jun-2026 01:56:59.604 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
04-Jun-2026 01:56:59.604 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
04-Jun-2026 01:56:59.604 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
04-Jun-2026 01:56:59.604 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
04-Jun-2026 01:56:59.604 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
04-Jun-2026 01:56:59.609 database: debug 1: delete_node(): 0x7f76600db050 . (bucket 1)
04-Jun-2026 01:56:59.609 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.
04-Jun-2026 01:56:59.609 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
04-Jun-2026 01:56:59.609 general: debug 1: managed-keys-zone: next key refresh: 05-Jun-2026 01:56:59.609
04-Jun-2026 01:56:59.609 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.
04-Jun-2026 01:56:59.609 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
04-Jun-2026 01:56:59.609 general: debug 1: managed-keys-zone: next key refresh: 05-Jun-2026 01:56:59.609
04-Jun-2026 01:56:59.609 general: debug 1: zone_journal: managed-keys-zone: enter
04-Jun-2026 01:56:59.779 general: debug 1: zone_needdump: managed-keys-zone: enter
04-Jun-2026 01:56:59.779 general: debug 1: zone__settimer: managed-keys-zone: enter
04-Jun-2026 01:56:59.779 general: debug 1: zone__settimer: managed-keys-zone: enter
04-Jun-2026 01:56:59.779 general: debug 1: zone__settimer: managed-keys-zone: enter
04-Jun-2026 01:56:59.779 resolver: debug 1: resolver priming query complete: success
04-Jun-2026 01:57:27.808 general: debug 1: zone_maintenance: managed-keys-zone: enter
04-Jun-2026 01:57:27.808 general: debug 1: zone_dump: managed-keys-zone: enter
04-Jun-2026 01:57:27.811 general: debug 1: zone__settimer: managed-keys-zone: enter
04-Jun-2026 01:57:27.815 general: debug 1: dump_done: managed-keys-zone: enter
04-Jun-2026 01:57:27.815 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
04-Jun-2026 01:57:45.933 network: info: listening on IPv6 interface tapeth0-d0c5e9, fe80::70eb:d8ff:fed7:5fcb%11#53
04-Jun-2026 01:57:51.117 network: info: listening on IPv6 interface tapeth0-5e86a5, fe80::4016:71ff:fe34:1ce6%13#53
04-Jun-2026 01:59:11.551 network: info: listening on IPv4 interface kube-ipvs0, 10.106.203.118#53
04-Jun-2026 01:59:19.501 network: info: listening on IPv6 interface tapeth0-4acf75, fe80::2417:cbff:fe01:291e%15#53
04-Jun-2026 01:59:19.511 network: info: listening on IPv6 interface tapeth0-014c6d, fe80::458:bcff:fe46:c0a6%17#53
04-Jun-2026 01:59:23.792 network: info: listening on IPv6 interface veth919ad694-4, fe80::b0e2:6eff:fe02:eea6%18#53
04-Jun-2026 01:59:29.935 network: info: listening on IPv6 interface tapeth0-8cff4f, fe80::982a:d8ff:fef0:9871%20#53
04-Jun-2026 02:00:12.273 network: info: no longer listening on fe80::982a:d8ff:fef0:9871%20#53
04-Jun-2026 02:00:18.724 network: info: no longer listening on fe80::b0e2:6eff:fe02:eea6%18#53
04-Jun-2026 02:00:19.878 network: info: no longer listening on fe80::458:bcff:fe46:c0a6%17#53
04-Jun-2026 02:00:24.702 network: info: no longer listening on fe80::2417:cbff:fe01:291e%15#53
04-Jun-2026 02:00:44.942 network: info: listening on IPv6 interface tapeth0-6502bc, fe80::2041:ccff:fe5d:a152%22#53
04-Jun-2026 02:00:44.949 network: info: listening on IPv6 interface tapeth0-aabb85, fe80::8888:b9ff:fe92:fffd%24#53
04-Jun-2026 02:00:44.956 network: info: listening on IPv6 interface tapeth0-b9d0e8, fe80::700c:dbff:fe23:6ca1%26#53
04-Jun-2026 02:00:49.934 network: info: listening on IPv6 interface tapeth0-472b18, fe80::303f:23ff:fe48:eacd%28#53
04-Jun-2026 02:00:49.934 network: info: listening on IPv6 interface tapeth0-138024, fe80::d450:9eff:fe59:aa58%30#53
04-Jun-2026 02:00:49.935 network: info: listening on IPv6 interface tapeth0-533f2f, fe80::54bb:30ff:fe2d:8cc2%32#53
04-Jun-2026 02:00:54.670 network: info: listening on IPv6 interface tapeth0-481263, fe80::4869:2ff:feef:57dc%34#53
04-Jun-2026 02:00:54.670 network: info: listening on IPv6 interface tapeth0-b318eb, fe80::7cd9:27ff:fe13:6f3f%36#53
04-Jun-2026 02:01:04.051 network: info: listening on IPv4 interface kube-ipvs0, 10.98.222.172#53
04-Jun-2026 02:04:14.718 network: info: no longer listening on fe80::54bb:30ff:fe2d:8cc2%32#53
04-Jun-2026 02:04:14.727 network: info: no longer listening on fe80::700c:dbff:fe23:6ca1%26#53
04-Jun-2026 02:04:14.741 network: info: no longer listening on fe80::8888:b9ff:fe92:fffd%24#53
04-Jun-2026 02:04:14.775 network: info: no longer listening on fe80::2041:ccff:fe5d:a152%22#53
04-Jun-2026 02:04:44.412 network: info: no longer listening on fe80::7cd9:27ff:fe13:6f3f%36#53
04-Jun-2026 02:04:44.436 network: info: no longer listening on fe80::d450:9eff:fe59:aa58%30#53
04-Jun-2026 02:04:44.483 network: info: no longer listening on fe80::303f:23ff:fe48:eacd%28#53
04-Jun-2026 02:04:44.485 network: info: no longer listening on fe80::4869:2ff:feef:57dc%34#53
04-Jun-2026 02:05:00.313 network: info: no longer listening on 10.98.222.172#53