12-Feb-2026 02:38:20.748 general: debug 1: now using logging configuration from config file
12-Feb-2026 02:38:20.748 general: debug 1: loop exclusive mode: ending
12-Feb-2026 02:38:20.748 general: debug 1: loop exclusive mode: ended
12-Feb-2026 02:38:20.748 general: notice: command channel listening on 127.0.0.1#8094
12-Feb-2026 02:38:20.748 general: debug 1: load_configuration: success
12-Feb-2026 02:38:20.748 general: debug 1: loop exclusive mode: starting
12-Feb-2026 02:38:20.748 general: debug 1: loop exclusive mode: started
12-Feb-2026 02:38:20.748 zoneload: debug 1: managed-keys-zone: starting load
12-Feb-2026 02:38:20.748 general: debug 1: zone_startload: managed-keys-zone: enter
12-Feb-2026 02:38:20.748 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
12-Feb-2026 02:38:20.748 general: debug 1: managed-keys-zone: creating SOA
12-Feb-2026 02:38:20.748 zoneload: debug 1: managed-keys-zone: loaded; checking validity
12-Feb-2026 02:38:20.748 zoneload: info: managed-keys-zone: loaded serial 0
12-Feb-2026 02:38:20.752 general: debug 1: loop exclusive mode: ending
12-Feb-2026 02:38:20.752 general: debug 1: loop exclusive mode: ended
12-Feb-2026 02:38:20.752 zoneload: debug 1: zone authors.bind/CH: starting load
12-Feb-2026 02:38:20.752 zoneload: debug 1: zone hostname.bind/CH: starting load
12-Feb-2026 02:38:20.752 zoneload: debug 1: zone version.bind/CH: starting load
12-Feb-2026 02:38:20.752 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 02:38:20.752 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
12-Feb-2026 02:38:20.752 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
12-Feb-2026 02:38:20.752 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
12-Feb-2026 02:38:20.752 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
12-Feb-2026 02:38:20.752 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
12-Feb-2026 02:38:20.752 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
12-Feb-2026 02:38:20.752 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
12-Feb-2026 02:38:20.752 general: debug 1: zone__settimer: zone authors.bind/CH: enter
12-Feb-2026 02:38:20.752 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
12-Feb-2026 02:38:20.752 general: debug 1: zone__settimer: zone authors.bind/CH: enter
12-Feb-2026 02:38:20.752 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
12-Feb-2026 02:38:20.752 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
12-Feb-2026 02:38:20.752 zoneload: debug 1: zone id.server/CH: starting load
12-Feb-2026 02:38:20.752 zoneload: debug 1: zone id.server/CH: loaded; checking validity
12-Feb-2026 02:38:20.752 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
12-Feb-2026 02:38:20.752 general: notice: all zones loaded
12-Feb-2026 02:38:20.752 general: debug 1: managed-keys-zone: synchronizing trusted keys
12-Feb-2026 02:38:20.752 general: debug 1: create_keydata: managed-keys-zone: enter
12-Feb-2026 02:38:20.752 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
12-Feb-2026 02:38:20.752 general: debug 1: managed-keys-zone: next key refresh: 12-Feb-2026 02:38:20.752
12-Feb-2026 02:38:20.752 general: debug 1: zone_journal: managed-keys-zone: enter
12-Feb-2026 02:38:20.752 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
12-Feb-2026 02:38:20.752 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 02:38:20.760 general: debug 1: zone_needdump: managed-keys-zone: enter
12-Feb-2026 02:38:20.760 general: debug 1: zone_maintenance: managed-keys-zone: enter
12-Feb-2026 02:38:20.760 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
12-Feb-2026 02:38:20.760 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
12-Feb-2026 02:38:20.760 general: debug 1: managed-keys-zone: next key refresh: 12-Feb-2026 02:38:20.760
12-Feb-2026 02:38:20.760 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 02:38:20.760 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 02:38:20.760 resolver: debug 1: fetch: ./DNSKEY
12-Feb-2026 02:38:20.760 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 02:38:20.760 resolver: debug 1: fetch: ./NS
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
12-Feb-2026 02:38:20.760 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
12-Feb-2026 02:38:20.760 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 02:38:20.764 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
12-Feb-2026 02:38:20.764 general: debug 1: zone__settimer: zone authors.bind/CH: enter
12-Feb-2026 02:38:20.764 general: notice: FIPS mode is disabled
12-Feb-2026 02:38:20.764 general: notice: running
12-Feb-2026 02:38:20.764 general: debug 1: zone__settimer: zone version.bind/CH: enter
12-Feb-2026 02:38:20.764 general: debug 1: zone__settimer: zone id.server/CH: enter
12-Feb-2026 02:38:20.764 general: debug 1: zone__settimer: zone version.bind/CH: enter
12-Feb-2026 02:38:20.764 general: debug 1: zone__settimer: zone id.server/CH: enter
12-Feb-2026 02:38:20.764 general: debug 1: zone_maintenance: zone version.bind/CH: enter
12-Feb-2026 02:38:20.764 general: debug 1: zone_maintenance: zone id.server/CH: enter
12-Feb-2026 02:38:20.764 general: debug 1: zone__settimer: zone version.bind/CH: enter
12-Feb-2026 02:38:20.764 general: debug 1: zone__settimer: zone id.server/CH: enter
12-Feb-2026 02:38:20.764 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.
12-Feb-2026 02:38:20.764 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
12-Feb-2026 02:38:20.764 general: debug 1: managed-keys-zone: next key refresh: 13-Feb-2026 02:38:20.764
12-Feb-2026 02:38:20.764 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.
12-Feb-2026 02:38:20.764 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
12-Feb-2026 02:38:20.764 general: debug 1: managed-keys-zone: next key refresh: 13-Feb-2026 02:38:20.764
12-Feb-2026 02:38:20.764 general: debug 1: zone_journal: managed-keys-zone: enter
12-Feb-2026 02:38:20.772 general: debug 1: zone_needdump: managed-keys-zone: enter
12-Feb-2026 02:38:20.776 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 02:38:20.776 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 02:38:20.776 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Feb-2026 02:38:20.776 lame-servers: info: SERVFAIL unexpected RCODE resolving './NS/IN': 192.36.148.17#53
12-Feb-2026 02:38:20.780 resolver: debug 1: resolver priming query complete: success
12-Feb-2026 02:38:22.028 general: info: received control channel command 'reconfig'
12-Feb-2026 02:38:22.028 general: debug 1: loop exclusive mode: starting
12-Feb-2026 02:38:22.036 general: debug 1: loop exclusive mode: started
12-Feb-2026 02:38:22.036 general: info: loading configuration from '/etc/contrail/dns/contrail-named.conf'
12-Feb-2026 02:38:22.036 general: info: the working directory is now '/etc/contrail/dns'
12-Feb-2026 02:38:22.036 general: info: using default UDP/IPv4 port range: [32768, 60999]
12-Feb-2026 02:38:22.036 general: info: using default UDP/IPv6 port range: [32768, 60999]
12-Feb-2026 02:38:22.036 general: info: Disabling periodic interface re-scans timer
12-Feb-2026 02:38:22.036 config: debug 1: none:215: dnssec-policy: load policy 'default'
12-Feb-2026 02:38:22.036 config: debug 1: none:238: dnssec-policy: load policy 'insecure'
12-Feb-2026 02:38:22.036 security: info: using built-in root key for view _default_view_
12-Feb-2026 02:38:22.036 general: info: set up managed keys zone for view _default_view_, file '/etc/contrail/dns/_default_view_.mkeys'
12-Feb-2026 02:38:22.036 general: debug 1: now using logging configuration from config file
12-Feb-2026 02:38:22.036 general: debug 1: loop exclusive mode: ending
12-Feb-2026 02:38:22.036 general: debug 1: loop exclusive mode: ended
12-Feb-2026 02:38:22.040 general: debug 1: managed-keys-zone: final reference detached
12-Feb-2026 02:38:22.040 database: debug 1: calling free_qpdb(.)
12-Feb-2026 02:38:22.040 database: debug 1: done free_qpdb(.)
12-Feb-2026 02:38:22.040 database: debug 1: calling free_qpdb(.)
12-Feb-2026 02:38:22.040 database: debug 1: called free_qpdb(.)
12-Feb-2026 02:38:22.040 general: debug 1: load_configuration: success
12-Feb-2026 02:38:22.040 general: info: reloading configuration succeeded
12-Feb-2026 02:38:22.040 general: debug 1: loop exclusive mode: starting
12-Feb-2026 02:38:22.040 general: debug 1: loop exclusive mode: started
12-Feb-2026 02:38:22.040 zoneload: debug 1: managed-keys-zone/_default_view_: starting load
12-Feb-2026 02:38:22.040 general: debug 1: zone_startload: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.040 zoneload: debug 1: managed-keys-zone/_default_view_: loading from master file /etc/contrail/dns/_default_view_.mkeys failed: file not found
12-Feb-2026 02:38:22.040 general: debug 1: managed-keys-zone/_default_view_: creating SOA
12-Feb-2026 02:38:22.040 zoneload: debug 1: managed-keys-zone/_default_view_: loaded; checking validity
12-Feb-2026 02:38:22.040 zoneload: info: managed-keys-zone/_default_view_: loaded serial 0
12-Feb-2026 02:38:22.040 general: debug 1: loop exclusive mode: ending
12-Feb-2026 02:38:22.040 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.040 general: debug 1: loop exclusive mode: ended
12-Feb-2026 02:38:22.040 general: info: scheduled loading new zones
12-Feb-2026 02:38:22.040 general: info: any newly configured zones are now loaded
12-Feb-2026 02:38:22.040 general: debug 1: managed-keys-zone/_default_view_: synchronizing trusted keys
12-Feb-2026 02:38:22.040 general: debug 1: create_keydata: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.040 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.040 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 12-Feb-2026 02:38:22.040
12-Feb-2026 02:38:22.040 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.040 general: debug 1: zone_journal: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.040 general: debug 1: journal file /etc/contrail/dns/_default_view_.mkeys.jnl does not exist, creating it
12-Feb-2026 02:38:22.048 general: debug 1: zone_needdump: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.048 general: debug 1: zone_maintenance: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.048 general: debug 1: zone_refreshkeys: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.048 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.048 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 12-Feb-2026 02:38:22.048
12-Feb-2026 02:38:22.048 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.048 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.048 resolver: debug 1: fetch: ./DNSKEY
12-Feb-2026 02:38:22.048 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.048 resolver: debug 1: fetch: ./NS
12-Feb-2026 02:38:22.048 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
12-Feb-2026 02:38:22.048 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
12-Feb-2026 02:38:22.048 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
12-Feb-2026 02:38:22.048 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
12-Feb-2026 02:38:22.048 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
12-Feb-2026 02:38:22.048 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
12-Feb-2026 02:38:22.048 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
12-Feb-2026 02:38:22.048 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
12-Feb-2026 02:38:22.048 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
12-Feb-2026 02:38:22.048 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
12-Feb-2026 02:38:22.048 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
12-Feb-2026 02:38:22.048 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
12-Feb-2026 02:38:22.048 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
12-Feb-2026 02:38:22.048 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
12-Feb-2026 02:38:22.048 general: debug 1: zone__settimer: zone authors.bind/CH: enter
12-Feb-2026 02:38:22.048 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.048 general: notice: FIPS mode is disabled
12-Feb-2026 02:38:22.048 general: notice: running
12-Feb-2026 02:38:22.048 general: debug 1: zone__settimer: zone version.bind/CH: enter
12-Feb-2026 02:38:22.048 general: debug 1: zone__settimer: zone id.server/CH: enter
12-Feb-2026 02:38:22.052 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.
12-Feb-2026 02:38:22.052 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.052 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 13-Feb-2026 02:38:22.052
12-Feb-2026 02:38:22.052 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.
12-Feb-2026 02:38:22.052 general: debug 1: set_refreshkeytimer: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.052 general: debug 1: managed-keys-zone/_default_view_: next key refresh: 13-Feb-2026 02:38:22.052
12-Feb-2026 02:38:22.052 general: debug 1: zone_journal: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.056 general: debug 1: zone_needdump: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.056 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.056 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.056 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:22.056 resolver: debug 1: resolver priming query complete: success
12-Feb-2026 02:38:47.064 general: debug 1: zone_maintenance: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:47.064 general: debug 1: zone_dump: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:47.064 general: debug 1: zone__settimer: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:47.072 general: debug 1: dump_done: managed-keys-zone/_default_view_: enter
12-Feb-2026 02:38:47.072 general: debug 1: zone_journal_compact: managed-keys-zone/_default_view_: target journal size 0
12-Feb-2026 02:41:39.687 network: info: listening on IPv6 interface vhost0, fe80::f816:3eff:fecc:f096%8#53
12-Feb-2026 02:41:39.687 network: info: no longer listening on 10.20.0.192#53
12-Feb-2026 02:41:39.695 network: info: listening on IPv4 interface vhost0, 10.20.0.192#53
12-Feb-2026 02:41:39.699 network: info: no longer listening on fe80::f816:3eff:fecc:f096%3#53
12-Feb-2026 02:41:42.655 network: info: listening on IPv6 interface pkt0, fe80::4c28:8fff:fe89:284f%9#53
12-Feb-2026 02:43:39.451 network: info: listening on IPv6 interface vethdc586111-e, fe80::7011:71ff:fea7:9f1a%12#53
12-Feb-2026 02:43:39.455 network: info: listening on IPv6 interface vethb0874d63-f, fe80::98e0:8bff:fef7:c01a%13#53
12-Feb-2026 02:43:59.867 network: info: listening on IPv6 interface veth0ecd5ad7-8, fe80::eca8:5aff:fe69:303a%14#53
12-Feb-2026 02:43:59.903 network: info: listening on IPv6 interface vethef1291b5-9, fe80::6cae:30ff:fe06:d004%15#53
12-Feb-2026 02:44:03.131 network: info: listening on IPv6 interface vethc81ca105-1, fe80::9c70:82ff:fe3f:8091%16#53
12-Feb-2026 02:44:03.135 network: info: listening on IPv6 interface veth77f4ef98-3, fe80::44a:76ff:fe2f:610a%17#53
12-Feb-2026 02:44:03.275 network: info: no longer listening on fe80::eca8:5aff:fe69:303a%14#53
12-Feb-2026 02:44:03.319 network: info: no longer listening on fe80::6cae:30ff:fe06:d004%15#53
12-Feb-2026 02:44:46.106 network: info: listening on IPv6 interface veth88380181-b, fe80::2c49:52ff:fe79:7c0f%18#53
12-Feb-2026 02:44:46.106 network: info: listening on IPv6 interface veth3d9e439a-7, fe80::40ad:c3ff:fee6:10e6%19#53