19-Feb-2026 01:58:19.032 general: debug 1: now using logging configuration from config file
19-Feb-2026 01:58:19.032 general: debug 1: loop exclusive mode: ending
19-Feb-2026 01:58:19.032 general: debug 1: loop exclusive mode: ended
19-Feb-2026 01:58:19.032 general: notice: command channel listening on 127.0.0.1#8094
19-Feb-2026 01:58:19.032 general: debug 1: load_configuration: success
19-Feb-2026 01:58:19.032 general: debug 1: loop exclusive mode: starting
19-Feb-2026 01:58:19.048 general: debug 1: loop exclusive mode: started
19-Feb-2026 01:58:19.048 zoneload: debug 1: managed-keys-zone: starting load
19-Feb-2026 01:58:19.048 general: debug 1: zone_startload: managed-keys-zone: enter
19-Feb-2026 01:58:19.048 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
19-Feb-2026 01:58:19.048 general: debug 1: managed-keys-zone: creating SOA
19-Feb-2026 01:58:19.048 zoneload: debug 1: managed-keys-zone: loaded; checking validity
19-Feb-2026 01:58:19.048 zoneload: info: managed-keys-zone: loaded serial 0
19-Feb-2026 01:58:19.048 general: debug 1: loop exclusive mode: ending
19-Feb-2026 01:58:19.048 zoneload: debug 1: zone id.server/CH: starting load
19-Feb-2026 01:58:19.048 zoneload: debug 1: zone id.server/CH: loaded; checking validity
19-Feb-2026 01:58:19.048 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
19-Feb-2026 01:58:19.048 general: debug 1: zone__settimer: zone id.server/CH: enter
19-Feb-2026 01:58:19.048 general: debug 1: zone_maintenance: zone id.server/CH: enter
19-Feb-2026 01:58:19.048 general: debug 1: zone__settimer: zone id.server/CH: enter
19-Feb-2026 01:58:19.048 zoneload: debug 1: zone version.bind/CH: starting load
19-Feb-2026 01:58:19.048 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
19-Feb-2026 01:58:19.048 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
19-Feb-2026 01:58:19.048 general: debug 1: zone__settimer: zone version.bind/CH: enter
19-Feb-2026 01:58:19.048 general: debug 1: zone_maintenance: zone version.bind/CH: enter
19-Feb-2026 01:58:19.048 general: debug 1: zone__settimer: zone version.bind/CH: enter
19-Feb-2026 01:58:19.048 zoneload: debug 1: zone authors.bind/CH: starting load
19-Feb-2026 01:58:19.048 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
19-Feb-2026 01:58:19.048 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
19-Feb-2026 01:58:19.048 zoneload: debug 1: zone hostname.bind/CH: starting load
19-Feb-2026 01:58:19.048 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
19-Feb-2026 01:58:19.048 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
19-Feb-2026 01:58:19.048 general: notice: all zones loaded
19-Feb-2026 01:58:19.048 general: debug 1: managed-keys-zone: synchronizing trusted keys
19-Feb-2026 01:58:19.048 general: debug 1: create_keydata: managed-keys-zone: enter
19-Feb-2026 01:58:19.048 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
19-Feb-2026 01:58:19.048 general: debug 1: managed-keys-zone: next key refresh: 19-Feb-2026 01:58:19.048
19-Feb-2026 01:58:19.048 general: debug 1: zone_journal: managed-keys-zone: enter
19-Feb-2026 01:58:19.048 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
19-Feb-2026 01:58:19.048 general: debug 1: loop exclusive mode: ended
19-Feb-2026 01:58:19.048 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:58:19.056 general: debug 1: zone_needdump: managed-keys-zone: enter
19-Feb-2026 01:58:19.056 general: notice: FIPS mode is disabled
19-Feb-2026 01:58:19.056 general: notice: running
19-Feb-2026 01:58:19.056 general: debug 1: zone__settimer: zone authors.bind/CH: enter
19-Feb-2026 01:58:19.056 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
19-Feb-2026 01:58:19.056 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
19-Feb-2026 01:58:19.056 general: debug 1: zone__settimer: zone authors.bind/CH: enter
19-Feb-2026 01:58:19.056 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
19-Feb-2026 01:58:19.056 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
19-Feb-2026 01:58:19.056 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
19-Feb-2026 01:58:19.056 general: debug 1: zone__settimer: zone authors.bind/CH: enter
19-Feb-2026 01:58:19.056 general: debug 1: zone__settimer: zone version.bind/CH: enter
19-Feb-2026 01:58:19.056 general: debug 1: zone__settimer: zone id.server/CH: enter
19-Feb-2026 01:58:19.056 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:58:19.056 general: debug 1: zone_maintenance: managed-keys-zone: enter
19-Feb-2026 01:58:19.056 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
19-Feb-2026 01:58:19.056 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
19-Feb-2026 01:58:19.056 general: debug 1: managed-keys-zone: next key refresh: 19-Feb-2026 01:58:19.056
19-Feb-2026 01:58:19.056 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:58:19.056 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:58:19.056 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:58:19.056 resolver: debug 1: fetch: ./DNSKEY
19-Feb-2026 01:58:19.056 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:58:19.056 resolver: debug 1: fetch: ./NS
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
19-Feb-2026 01:58:19.056 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
19-Feb-2026 01:58:19.072 database: debug 1: delete_node(): 0x7fd1680cb070 . (bucket 0)
19-Feb-2026 01:58:19.072 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.
19-Feb-2026 01:58:19.072 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
19-Feb-2026 01:58:19.072 general: debug 1: managed-keys-zone: next key refresh: 20-Feb-2026 01:58:19.072
19-Feb-2026 01:58:19.072 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.
19-Feb-2026 01:58:19.072 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
19-Feb-2026 01:58:19.072 general: debug 1: managed-keys-zone: next key refresh: 20-Feb-2026 01:58:19.072
19-Feb-2026 01:58:19.072 general: debug 1: zone_journal: managed-keys-zone: enter
19-Feb-2026 01:58:19.076 general: debug 1: zone_needdump: managed-keys-zone: enter
19-Feb-2026 01:58:19.076 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:58:19.076 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:58:19.076 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Feb-2026 01:58:19.076 resolver: debug 1: resolver priming query complete: success
19-Feb-2026 01:58:20.312 general: info: received control channel command 'reconfig'
19-Feb-2026 01:58:20.312 general: debug 1: loop exclusive mode: starting
19-Feb-2026 01:58:20.312 general: debug 1: loop exclusive mode: started
19-Feb-2026 01:58:20.312 general: info: loading configuration from '/etc/contrail/dns/contrail-named.conf'
19-Feb-2026 01:58:20.312 general: info: the working directory is now '/etc/contrail/dns'
19-Feb-2026 01:58:20.312 general: info: using default UDP/IPv4 port range: [32768, 60999]
19-Feb-2026 01:58:20.312 general: info: using default UDP/IPv6 port range: [32768, 60999]
19-Feb-2026 01:58:20.312 general: info: Disabling periodic interface re-scans timer
19-Feb-2026 01:58:20.312 config: debug 1: none:215: dnssec-policy: load policy 'default'
19-Feb-2026 01:58:20.312 config: debug 1: none:238: dnssec-policy: load policy 'insecure'
19-Feb-2026 01:58:20.312 security: info: using built-in root key for view _default_view_
19-Feb-2026 01:58:20.312 general: info: set up managed keys zone for view _default_view_, file '/etc/contrail/dns/_default_view_.mkeys'
19-Feb-2026 01:58:20.312 general: debug 1: now using logging configuration from config file
19-Feb-2026 01:58:20.312 general: debug 1: loop exclusive mode: ending
19-Feb-2026 01:58:20.312 general: debug 1: loop exclusive mode: ended
19-Feb-2026 01:58:20.316 general: debug 1: managed-keys-zone: final reference detached
19-Feb-2026 01:58:20.316 database: debug 1: calling free_qpdb(.)
19-Feb-2026 01:58:20.316 database: debug 1: done free_qpdb(.)
19-Feb-2026 01:58:20.316 general: debug 1: load_configuration: success
19-Feb-2026 01:58:20.316 general: info: reloading configuration succeeded
19-Feb-2026 01:58:20.316 general: debug 1: loop exclusive mode: starting
19-Feb-2026 01:58:20.316 database: debug 1: calling free_qpdb(.)
19-Feb-2026 01:58:20.316 database: debug 1: called free_qpdb(.)
19-Feb-2026 01:58:20.316 general: debug 1: loop exclusive mode: started
19-Feb-2026 01:58:20.316 zoneload: debug 1: managed-keys-zone/_default_view_: starting load
19-Feb-2026 01:58:20.316 general: debug 1: zone_startload: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.316 zoneload: debug 1: managed-keys-zone/_default_view_: loading from master file /etc/contrail/dns/_default_view_.mkeys failed: file not found
19-Feb-2026 01:58:20.316 general: debug 1: managed-keys-zone/_default_view_: creating SOA
19-Feb-2026 01:58:20.316 zoneload: debug 1: managed-keys-zone/_default_view_: loaded; checking validity
19-Feb-2026 01:58:20.316 zoneload: info: managed-keys-zone/_default_view_: loaded serial 0
19-Feb-2026 01:58:20.316 general: debug 1: loop exclusive mode: ending
19-Feb-2026 01:58:20.316 general: debug 1: loop exclusive mode: ended
19-Feb-2026 01:58:20.316 general: info: scheduled loading new zones
19-Feb-2026 01:58:20.316 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.316 general: info: any newly configured zones are now loaded
19-Feb-2026 01:58:20.316 general: debug 1: managed-keys-zone/_default_view_: synchronizing trusted keys
19-Feb-2026 01:58:20.316 general: debug 1: create_keydata: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.316 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.316 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 19-Feb-2026 01:58:20.316
19-Feb-2026 01:58:20.316 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.316 general: debug 1: zone_journal: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.316 general: debug 1: journal file /etc/contrail/dns/_default_view_.mkeys.jnl does not exist, creating it
19-Feb-2026 01:58:20.320 general: debug 1: zone_needdump: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.320 general: debug 1: zone_maintenance: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.320 general: debug 1: zone__settimer: zone id.server/CH: enter
19-Feb-2026 01:58:20.320 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
19-Feb-2026 01:58:20.320 general: debug 1: zone__settimer: zone authors.bind/CH: enter
19-Feb-2026 01:58:20.320 general: notice: FIPS mode is disabled
19-Feb-2026 01:58:20.320 general: notice: running
19-Feb-2026 01:58:20.320 general: debug 1: zone_refreshkeys: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.320 general: debug 1: zone__settimer: zone version.bind/CH: enter
19-Feb-2026 01:58:20.320 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.320 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 19-Feb-2026 01:58:20.320
19-Feb-2026 01:58:20.320 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.320 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.320 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.320 resolver: debug 1: fetch: ./DNSKEY
19-Feb-2026 01:58:20.320 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.320 resolver: debug 1: fetch: ./NS
19-Feb-2026 01:58:20.324 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
19-Feb-2026 01:58:20.324 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
19-Feb-2026 01:58:20.324 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
19-Feb-2026 01:58:20.324 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
19-Feb-2026 01:58:20.324 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
19-Feb-2026 01:58:20.324 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
19-Feb-2026 01:58:20.324 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
19-Feb-2026 01:58:20.324 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
19-Feb-2026 01:58:20.324 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
19-Feb-2026 01:58:20.324 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
19-Feb-2026 01:58:20.324 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
19-Feb-2026 01:58:20.324 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
19-Feb-2026 01:58:20.324 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
19-Feb-2026 01:58:20.324 dnssec: warning: managed-keys-zone/_default_view_: Initializing automatic trust anchor management for zone '.'; DNSKEY ID 20326 is now trusted, waiving the normal 30-day waiting period.
19-Feb-2026 01:58:20.324 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.324 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 20-Feb-2026 01:58:20.324
19-Feb-2026 01:58:20.324 dnssec: warning: managed-keys-zone/_default_view_: Initializing automatic trust anchor management for zone '.'; DNSKEY ID 38696 is now trusted, waiving the normal 30-day waiting period.
19-Feb-2026 01:58:20.324 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.324 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 20-Feb-2026 01:58:20.324
19-Feb-2026 01:58:20.324 general: debug 1: zone_journal: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.328 general: debug 1: zone_needdump: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.328 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.328 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.328 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:20.332 resolver: debug 1: resolver priming query complete: success
19-Feb-2026 01:58:44.340 general: debug 1: zone_maintenance: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:44.340 general: debug 1: zone_dump: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:44.340 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:44.344 general: debug 1: dump_done: managed-keys-zone/_default_view_: enter
19-Feb-2026 01:58:44.344 general: debug 1: zone_journal_compact: managed-keys-zone/_default_view_: target journal size 0
19-Feb-2026 02:01:26.855 network: info: listening on IPv6 interface vhost0, fe80::f816:3eff:fe94:daeb%8#53
19-Feb-2026 02:01:26.855 network: info: no longer listening on 10.20.0.25#53
19-Feb-2026 02:01:26.859 network: info: listening on IPv4 interface vhost0, 10.20.0.25#53
19-Feb-2026 02:01:26.863 network: info: no longer listening on fe80::f816:3eff:fe94:daeb%3#53
19-Feb-2026 02:01:29.219 network: info: listening on IPv6 interface pkt0, fe80::4c28:8fff:fe89:284f%9#53
19-Feb-2026 02:03:12.289 network: info: listening on IPv6 interface veth4da1c71d-e, fe80::6800:6cff:fef1:31ce%12#53
19-Feb-2026 02:03:12.289 network: info: listening on IPv6 interface vethad8ae708-4, fe80::e0fd:91ff:fe0c:c407%13#53
19-Feb-2026 02:03:31.777 network: info: listening on IPv6 interface vethe89ddd0d-f, fe80::98cd:6bff:fec3:25cd%14#53
19-Feb-2026 02:03:31.805 network: info: listening on IPv6 interface veth18c1a8e7-3, fe80::3c1f:ecff:fe5d:5974%15#53
19-Feb-2026 02:03:35.397 network: info: listening on IPv6 interface vethc8b30111-a, fe80::447b:c2ff:fe3e:9e5c%16#53
19-Feb-2026 02:03:35.397 network: info: listening on IPv6 interface vethcf543789-9, fe80::781d:f1ff:fe02:c8d3%17#53
19-Feb-2026 02:03:36.593 network: info: no longer listening on fe80::98cd:6bff:fec3:25cd%14#53
19-Feb-2026 02:03:36.637 network: info: no longer listening on fe80::3c1f:ecff:fe5d:5974%15#53
19-Feb-2026 02:04:13.022 network: info: listening on IPv6 interface vethcb67b1e2-1, fe80::b4ea:e3ff:fe16:94e1%18#53
19-Feb-2026 02:04:13.022 network: info: listening on IPv6 interface vethcad54bfd-1, fe80::7813:8eff:fe9e:4fef%19#53