18-May-2026 02:01:16.509 general: debug 1: now using logging configuration from config file
18-May-2026 02:01:16.509 general: debug 1: loop exclusive mode: ending
18-May-2026 02:01:16.509 general: debug 1: loop exclusive mode: ended
18-May-2026 02:01:16.509 general: notice: command channel listening on 127.0.0.1#8094
18-May-2026 02:01:16.509 general: info: VDNS cleanup pass1: 0 departing views cleared
18-May-2026 02:01:16.509 general: info: VDNS cleanup pass2: 2 staying views re-checked
18-May-2026 02:01:16.509 general: debug 1: load_configuration: success
18-May-2026 02:01:16.509 general: debug 1: loop exclusive mode: starting
18-May-2026 02:01:16.525 general: debug 1: loop exclusive mode: started
18-May-2026 02:01:16.525 zoneload: debug 1: managed-keys-zone: starting load
18-May-2026 02:01:16.525 general: debug 1: zone_startload: managed-keys-zone: enter
18-May-2026 02:01:16.525 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
18-May-2026 02:01:16.525 general: debug 1: managed-keys-zone: creating SOA
18-May-2026 02:01:16.525 zoneload: debug 1: managed-keys-zone: loaded; checking validity
18-May-2026 02:01:16.525 zoneload: info: managed-keys-zone: loaded serial 0
18-May-2026 02:01:16.525 general: debug 1: loop exclusive mode: ending
18-May-2026 02:01:16.525 general: debug 1: loop exclusive mode: ended
18-May-2026 02:01:16.525 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 02:01:16.525 zoneload: debug 1: zone authors.bind/CH: starting load
18-May-2026 02:01:16.525 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
18-May-2026 02:01:16.525 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
18-May-2026 02:01:16.525 zoneload: debug 1: zone version.bind/CH: starting load
18-May-2026 02:01:16.525 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
18-May-2026 02:01:16.525 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
18-May-2026 02:01:16.525 general: debug 1: zone__settimer: zone authors.bind/CH: enter
18-May-2026 02:01:16.525 general: debug 1: zone__settimer: zone version.bind/CH: enter
18-May-2026 02:01:16.525 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
18-May-2026 02:01:16.525 general: debug 1: zone_maintenance: zone version.bind/CH: enter
18-May-2026 02:01:16.525 general: debug 1: zone__settimer: zone authors.bind/CH: enter
18-May-2026 02:01:16.525 general: debug 1: zone__settimer: zone version.bind/CH: enter
18-May-2026 02:01:16.525 zoneload: debug 1: zone hostname.bind/CH: starting load
18-May-2026 02:01:16.525 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
18-May-2026 02:01:16.525 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
18-May-2026 02:01:16.525 zoneload: debug 1: zone id.server/CH: starting load
18-May-2026 02:01:16.525 zoneload: debug 1: zone id.server/CH: loaded; checking validity
18-May-2026 02:01:16.525 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
18-May-2026 02:01:16.525 general: notice: all zones loaded
18-May-2026 02:01:16.525 general: debug 1: managed-keys-zone: synchronizing trusted keys
18-May-2026 02:01:16.525 general: debug 1: create_keydata: managed-keys-zone: enter
18-May-2026 02:01:16.525 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
18-May-2026 02:01:16.525 general: debug 1: managed-keys-zone: next key refresh: 18-May-2026 02:01:16.525
18-May-2026 02:01:16.525 general: debug 1: zone_journal: managed-keys-zone: enter
18-May-2026 02:01:16.525 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
18-May-2026 02:01:16.525 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 02:01:16.533 general: debug 1: zone_needdump: managed-keys-zone: enter
18-May-2026 02:01:16.533 general: notice: FIPS mode is disabled
18-May-2026 02:01:16.533 general: notice: running
18-May-2026 02:01:16.533 general: debug 1: debug: t1-cloud-fixed version
18-May-2026 02:01:16.533 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
18-May-2026 02:01:16.533 general: debug 1: zone__settimer: zone id.server/CH: enter
18-May-2026 02:01:16.533 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
18-May-2026 02:01:16.533 general: debug 1: zone__settimer: zone id.server/CH: enter
18-May-2026 02:01:16.533 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
18-May-2026 02:01:16.533 general: debug 1: zone_maintenance: zone id.server/CH: enter
18-May-2026 02:01:16.533 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
18-May-2026 02:01:16.533 general: debug 1: zone__settimer: zone id.server/CH: enter
18-May-2026 02:01:16.533 general: debug 1: zone_maintenance: managed-keys-zone: enter
18-May-2026 02:01:16.533 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
18-May-2026 02:01:16.533 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
18-May-2026 02:01:16.533 general: debug 1: managed-keys-zone: next key refresh: 18-May-2026 02:01:16.533
18-May-2026 02:01:16.533 general: debug 1: zone__settimer: zone version.bind/CH: enter
18-May-2026 02:01:16.533 general: debug 1: zone__settimer: zone authors.bind/CH: enter
18-May-2026 02:01:16.533 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 02:01:16.533 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 02:01:16.533 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 02:01:16.533 resolver: debug 1: fetch: ./DNSKEY
18-May-2026 02:01:16.533 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 02:01:16.533 resolver: debug 1: fetch: ./NS
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
18-May-2026 02:01:16.533 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
18-May-2026 02:01:16.537 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
18-May-2026 02:01:16.537 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
18-May-2026 02:01:16.537 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
18-May-2026 02:01:16.537 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
18-May-2026 02:01:16.537 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
18-May-2026 02:01:16.537 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
18-May-2026 02:01:16.585 database: debug 1: delete_node(): 0x7fd0700cb160 . (bucket 7)
18-May-2026 02:01:16.585 resolver: debug 1: fetch: ./DNSKEY
18-May-2026 02:01:16.585 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
18-May-2026 02:01:16.585 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
18-May-2026 02:01:16.589 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.
18-May-2026 02:01:16.589 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
18-May-2026 02:01:16.589 general: debug 1: managed-keys-zone: next key refresh: 19-May-2026 02:01:16.589
18-May-2026 02:01:16.589 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.
18-May-2026 02:01:16.589 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
18-May-2026 02:01:16.589 general: debug 1: managed-keys-zone: next key refresh: 19-May-2026 02:01:16.589
18-May-2026 02:01:16.589 general: debug 1: zone_journal: managed-keys-zone: enter
18-May-2026 02:01:16.597 general: debug 1: zone_needdump: managed-keys-zone: enter
18-May-2026 02:01:16.597 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 02:01:16.597 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 02:01:16.597 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 02:01:16.633 resolver: debug 1: resolver priming query complete: success
18-May-2026 02:01:17.789 general: info: received control channel command 'reconfig'
18-May-2026 02:01:17.789 general: debug 1: loop exclusive mode: starting
18-May-2026 02:01:17.789 general: debug 1: loop exclusive mode: started
18-May-2026 02:01:17.789 general: info: loading configuration from '/etc/contrail/dns/contrail-named.conf'
18-May-2026 02:01:17.789 general: info: the working directory is now '/etc/contrail/dns'
18-May-2026 02:01:17.789 general: info: using default UDP/IPv4 port range: [32768, 60999]
18-May-2026 02:01:17.789 general: info: using default UDP/IPv6 port range: [32768, 60999]
18-May-2026 02:01:17.789 general: info: Disabling periodic interface re-scans timer
18-May-2026 02:01:17.793 config: debug 1: none:215: dnssec-policy: load policy 'default'
18-May-2026 02:01:17.793 config: debug 1: none:238: dnssec-policy: load policy 'insecure'
18-May-2026 02:01:17.793 security: info: using built-in root key for view _default_view_
18-May-2026 02:01:17.793 general: info: set up managed keys zone for view _default_view_, file '/etc/contrail/dns/_default_view_.mkeys'
18-May-2026 02:01:17.793 general: debug 1: now using logging configuration from config file
18-May-2026 02:01:17.793 general: debug 1: loop exclusive mode: ending
18-May-2026 02:01:17.793 general: debug 1: loop exclusive mode: ended
18-May-2026 02:01:17.793 general: info: VDNS cleanup pass1: 2 departing views cleared
18-May-2026 02:01:17.793 general: info: VDNS cleanup pass2: 2 staying views re-checked
18-May-2026 02:01:17.793 general: info: VDNS detach view '_default' refcount=1
18-May-2026 02:01:17.809 general: debug 1: managed-keys-zone: final reference detached
18-May-2026 02:01:17.809 general: info: VDNS detach view '_bind' refcount=1
18-May-2026 02:01:17.809 database: debug 1: calling free_qpdb(.)
18-May-2026 02:01:17.809 database: debug 1: done free_qpdb(.)
18-May-2026 02:01:17.809 database: debug 1: calling free_qpdb(.)
18-May-2026 02:01:17.809 database: debug 1: called free_qpdb(.)
18-May-2026 02:01:17.817 general: debug 1: load_configuration: success
18-May-2026 02:01:17.817 general: info: reloading configuration succeeded
18-May-2026 02:01:17.817 general: debug 1: loop exclusive mode: starting
18-May-2026 02:01:17.833 general: debug 1: loop exclusive mode: started
18-May-2026 02:01:17.833 zoneload: debug 1: managed-keys-zone/_default_view_: starting load
18-May-2026 02:01:17.833 general: debug 1: zone_startload: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.833 zoneload: debug 1: managed-keys-zone/_default_view_: loading from master file /etc/contrail/dns/_default_view_.mkeys failed: file not found
18-May-2026 02:01:17.833 general: debug 1: managed-keys-zone/_default_view_: creating SOA
18-May-2026 02:01:17.833 zoneload: debug 1: managed-keys-zone/_default_view_: loaded; checking validity
18-May-2026 02:01:17.833 zoneload: info: managed-keys-zone/_default_view_: loaded serial 0
18-May-2026 02:01:17.833 general: debug 1: loop exclusive mode: ending
18-May-2026 02:01:17.833 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.833 general: info: any newly configured zones are now loaded
18-May-2026 02:01:17.833 general: debug 1: managed-keys-zone/_default_view_: synchronizing trusted keys
18-May-2026 02:01:17.833 general: debug 1: create_keydata: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.833 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.833 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 18-May-2026 02:01:17.833
18-May-2026 02:01:17.833 general: debug 1: zone_journal: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.833 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.833 general: debug 1: journal file /etc/contrail/dns/_default_view_.mkeys.jnl does not exist, creating it
18-May-2026 02:01:17.833 general: debug 1: loop exclusive mode: ended
18-May-2026 02:01:17.833 general: info: scheduled loading new zones
18-May-2026 02:01:17.837 general: debug 1: zone_needdump: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.837 general: debug 1: zone__settimer: zone version.bind/CH: enter
18-May-2026 02:01:17.837 general: debug 1: zone__settimer: zone authors.bind/CH: enter
18-May-2026 02:01:17.837 general: notice: FIPS mode is disabled
18-May-2026 02:01:17.837 general: notice: running
18-May-2026 02:01:17.837 general: debug 1: debug: t1-cloud-fixed version
18-May-2026 02:01:17.837 general: debug 1: zone_maintenance: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.837 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
18-May-2026 02:01:17.837 general: debug 1: zone__settimer: zone id.server/CH: enter
18-May-2026 02:01:17.837 general: debug 1: zone_refreshkeys: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.837 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.837 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 18-May-2026 02:01:17.837
18-May-2026 02:01:17.837 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.837 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.837 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.837 resolver: debug 1: fetch: ./DNSKEY
18-May-2026 02:01:17.837 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.841 resolver: debug 1: fetch: ./NS
18-May-2026 02:01:17.841 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
18-May-2026 02:01:17.841 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
18-May-2026 02:01:17.841 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
18-May-2026 02:01:17.841 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
18-May-2026 02:01:17.841 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
18-May-2026 02:01:17.841 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
18-May-2026 02:01:17.841 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
18-May-2026 02:01:17.841 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
18-May-2026 02:01:17.841 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
18-May-2026 02:01:17.841 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
18-May-2026 02:01:17.841 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
18-May-2026 02:01:17.841 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
18-May-2026 02:01:17.841 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
18-May-2026 02:01:17.853 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.
18-May-2026 02:01:17.853 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.853 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 19-May-2026 02:01:17.853
18-May-2026 02:01:17.853 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.
18-May-2026 02:01:17.853 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.853 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 19-May-2026 02:01:17.853
18-May-2026 02:01:17.853 general: debug 1: zone_journal: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.857 general: debug 1: zone_needdump: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.857 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.857 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.857 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:17.889 resolver: debug 1: resolver priming query complete: success
18-May-2026 02:01:41.882 general: debug 1: zone_maintenance: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:41.882 general: debug 1: zone_dump: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:41.882 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:41.886 general: debug 1: dump_done: managed-keys-zone/_default_view_: enter
18-May-2026 02:01:41.886 general: debug 1: zone_journal_compact: managed-keys-zone/_default_view_: target journal size 0
18-May-2026 02:04:13.424 network: info: listening on IPv6 interface vhost0, fe80::f816:3eff:fee0:c520%8#53
18-May-2026 02:04:13.428 network: info: no longer listening on 10.20.0.254#53
18-May-2026 02:04:13.436 network: info: listening on IPv4 interface vhost0, 10.20.0.254#53
18-May-2026 02:04:13.444 network: info: no longer listening on fe80::f816:3eff:fee0:c520%3#53
18-May-2026 02:04:15.636 network: info: listening on IPv6 interface pkt0, fe80::4c28:8fff:fe89:284f%9#53
18-May-2026 02:06:35.410 network: info: listening on IPv6 interface veth946f06f6-a, fe80::4e4:f5ff:fed8:7f33%12#53
18-May-2026 02:06:35.410 network: info: listening on IPv6 interface vethcb087f31-a, fe80::24c1:b8ff:fec0:b79d%13#53
18-May-2026 02:06:37.034 network: info: listening on IPv6 interface vethc5cb7e02-2, fe80::fc9a:b2ff:fe70:b5f2%14#53
18-May-2026 02:06:37.058 network: info: listening on IPv6 interface vethdfcc8c0c-1, fe80::9c6d:a9ff:fe03:1fac%15#53
18-May-2026 02:06:37.058 network: info: no longer listening on fe80::4e4:f5ff:fed8:7f33%12#53
18-May-2026 02:06:37.114 network: info: no longer listening on fe80::24c1:b8ff:fec0:b79d%13#53
18-May-2026 02:07:20.727 network: info: listening on IPv6 interface vethdcf7c463-e, fe80::88a9:9dff:fe24:1be1%16#53
18-May-2026 02:07:20.727 network: info: listening on IPv6 interface vethb659c973-4, fe80::e817:6bff:fe16:15ab%17#53