02-Feb-2026 01:35:40.539 general: debug 1: now using logging configuration from config file
02-Feb-2026 01:35:40.539 general: debug 1: loop exclusive mode: ending
02-Feb-2026 01:35:40.540 general: debug 1: loop exclusive mode: ended
02-Feb-2026 01:35:40.540 general: notice: command channel listening on 127.0.0.1#8094
02-Feb-2026 01:35:40.540 general: debug 1: load_configuration: success
02-Feb-2026 01:35:40.540 general: debug 1: loop exclusive mode: starting
02-Feb-2026 01:35:40.858 general: debug 1: loop exclusive mode: started
02-Feb-2026 01:35:40.858 zoneload: debug 1: managed-keys-zone: starting load
02-Feb-2026 01:35:40.858 general: debug 1: zone_startload: managed-keys-zone: enter
02-Feb-2026 01:35:40.858 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
02-Feb-2026 01:35:40.858 general: debug 1: managed-keys-zone: creating SOA
02-Feb-2026 01:35:40.858 zoneload: debug 1: managed-keys-zone: loaded; checking validity
02-Feb-2026 01:35:40.858 zoneload: info: managed-keys-zone: loaded serial 0
02-Feb-2026 01:35:40.858 general: debug 1: loop exclusive mode: ending
02-Feb-2026 01:35:40.867 zoneload: debug 1: zone hostname.bind/CH: starting load
02-Feb-2026 01:35:40.867 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
02-Feb-2026 01:35:40.867 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
02-Feb-2026 01:35:40.867 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
02-Feb-2026 01:35:40.867 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
02-Feb-2026 01:35:40.867 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
02-Feb-2026 01:35:40.867 zoneload: debug 1: zone id.server/CH: starting load
02-Feb-2026 01:35:40.867 zoneload: debug 1: zone id.server/CH: loaded; checking validity
02-Feb-2026 01:35:40.867 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
02-Feb-2026 01:35:40.867 general: debug 1: zone__settimer: zone id.server/CH: enter
02-Feb-2026 01:35:40.867 general: debug 1: zone_maintenance: zone id.server/CH: enter
02-Feb-2026 01:35:40.867 general: debug 1: zone__settimer: zone id.server/CH: enter
02-Feb-2026 01:35:40.867 general: debug 1: loop exclusive mode: ended
02-Feb-2026 01:35:40.867 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Feb-2026 01:35:40.867 zoneload: debug 1: zone authors.bind/CH: starting load
02-Feb-2026 01:35:40.867 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
02-Feb-2026 01:35:40.867 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
02-Feb-2026 01:35:40.867 zoneload: debug 1: zone version.bind/CH: starting load
02-Feb-2026 01:35:40.867 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
02-Feb-2026 01:35:40.867 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
02-Feb-2026 01:35:40.867 general: notice: all zones loaded
02-Feb-2026 01:35:40.867 general: debug 1: managed-keys-zone: synchronizing trusted keys
02-Feb-2026 01:35:40.867 general: debug 1: create_keydata: managed-keys-zone: enter
02-Feb-2026 01:35:40.867 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
02-Feb-2026 01:35:40.867 general: debug 1: managed-keys-zone: next key refresh: 02-Feb-2026 01:35:40.867
02-Feb-2026 01:35:40.867 general: debug 1: zone_journal: managed-keys-zone: enter
02-Feb-2026 01:35:40.867 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
02-Feb-2026 01:35:40.891 general: debug 1: zone_needdump: managed-keys-zone: enter
02-Feb-2026 01:35:40.891 general: notice: FIPS mode is disabled
02-Feb-2026 01:35:40.891 general: notice: running
02-Feb-2026 01:35:40.891 general: debug 1: zone__settimer: zone authors.bind/CH: enter
02-Feb-2026 01:35:40.891 general: debug 1: zone__settimer: zone version.bind/CH: enter
02-Feb-2026 01:35:40.891 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Feb-2026 01:35:40.891 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Feb-2026 01:35:40.891 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Feb-2026 01:35:40.891 general: debug 1: zone__settimer: zone version.bind/CH: enter
02-Feb-2026 01:35:40.891 general: debug 1: zone__settimer: zone authors.bind/CH: enter
02-Feb-2026 01:35:40.891 general: debug 1: zone_maintenance: managed-keys-zone: enter
02-Feb-2026 01:35:40.891 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
02-Feb-2026 01:35:40.891 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
02-Feb-2026 01:35:40.891 general: debug 1: managed-keys-zone: next key refresh: 02-Feb-2026 01:35:40.891
02-Feb-2026 01:35:40.891 general: debug 1: zone_maintenance: zone version.bind/CH: enter
02-Feb-2026 01:35:40.891 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
02-Feb-2026 01:35:40.891 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Feb-2026 01:35:40.891 resolver: debug 1: fetch: ./DNSKEY
02-Feb-2026 01:35:40.891 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Feb-2026 01:35:40.891 general: debug 1: zone__settimer: zone version.bind/CH: enter
02-Feb-2026 01:35:40.891 general: debug 1: zone__settimer: zone authors.bind/CH: enter
02-Feb-2026 01:35:40.891 resolver: debug 1: fetch: ./NS
02-Feb-2026 01:35:40.891 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
02-Feb-2026 01:35:40.892 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
02-Feb-2026 01:35:40.893 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
02-Feb-2026 01:35:40.895 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
02-Feb-2026 01:35:40.895 general: debug 1: zone__settimer: zone id.server/CH: enter
02-Feb-2026 01:35:41.002 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.
02-Feb-2026 01:35:41.003 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
02-Feb-2026 01:35:41.003 general: debug 1: managed-keys-zone: next key refresh: 03-Feb-2026 01:35:41.003
02-Feb-2026 01:35:41.003 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.
02-Feb-2026 01:35:41.003 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
02-Feb-2026 01:35:41.003 general: debug 1: managed-keys-zone: next key refresh: 03-Feb-2026 01:35:41.003
02-Feb-2026 01:35:41.003 general: debug 1: zone_journal: managed-keys-zone: enter
02-Feb-2026 01:35:41.082 general: debug 1: zone_needdump: managed-keys-zone: enter
02-Feb-2026 01:35:41.082 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Feb-2026 01:35:41.082 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Feb-2026 01:35:41.082 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Feb-2026 01:35:41.475 resolver: debug 1: resolver priming query complete: success
02-Feb-2026 01:36:06.913 general: debug 1: zone_maintenance: managed-keys-zone: enter
02-Feb-2026 01:36:06.913 general: debug 1: zone_dump: managed-keys-zone: enter
02-Feb-2026 01:36:06.917 general: debug 1: zone__settimer: managed-keys-zone: enter
02-Feb-2026 01:36:06.957 general: debug 1: dump_done: managed-keys-zone: enter
02-Feb-2026 01:36:06.957 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
02-Feb-2026 01:36:27.078 network: info: listening on IPv6 interface tapeth0-605d4c, fe80::b83f:fdff:fe7b:9f5b%11#53
02-Feb-2026 01:36:37.381 network: info: listening on IPv6 interface tapeth0-772322, fe80::f409:1cff:fe5b:5f1f%13#53
02-Feb-2026 01:38:29.355 network: info: listening on IPv4 interface kube-ipvs0, 10.109.202.196#53
02-Feb-2026 01:38:36.998 network: info: listening on IPv6 interface tapeth0-88b873, fe80::bcfc:5eff:fe7b:771e%15#53
02-Feb-2026 01:38:37.003 network: info: listening on IPv6 interface tapeth0-1dff7d, fe80::68f6:73ff:fe9a:a4d3%17#53
02-Feb-2026 01:38:42.694 network: info: listening on IPv6 interface vetha17c7cce-2, fe80::e057:52ff:feef:982c%18#53
02-Feb-2026 01:38:47.879 network: info: listening on IPv6 interface tapeth0-29bc5c, fe80::e022:e7ff:fedc:aac6%20#53
02-Feb-2026 01:39:25.234 network: info: no longer listening on fe80::e022:e7ff:fedc:aac6%20#53
02-Feb-2026 01:39:32.149 network: info: no longer listening on fe80::e057:52ff:feef:982c%18#53
02-Feb-2026 01:39:37.952 network: info: no longer listening on fe80::68f6:73ff:fe9a:a4d3%17#53
02-Feb-2026 01:39:43.025 network: info: no longer listening on fe80::bcfc:5eff:fe7b:771e%15#53
02-Feb-2026 01:40:04.359 network: info: listening on IPv6 interface tapeth0-60033c, fe80::1495:bff:feb0:454e%22#53
02-Feb-2026 01:40:04.361 network: info: listening on IPv6 interface tapeth0-5a6e24, fe80::7cfe:56ff:fe22:73f7%24#53
02-Feb-2026 01:40:08.582 network: info: listening on IPv6 interface tapeth0-610660, fe80::4e5:4ff:feed:70cb%26#53
02-Feb-2026 01:40:08.585 network: info: listening on IPv6 interface tapeth0-383082, fe80::ac09:6fff:fe1d:df61%28#53
02-Feb-2026 01:40:08.585 network: info: listening on IPv6 interface tapeth0-45cc08, fe80::7832:e2ff:fee7:1c98%30#53
02-Feb-2026 01:40:08.585 network: info: listening on IPv6 interface tapeth0-361887, fe80::98bc:76ff:fe6a:6d30%32#53
02-Feb-2026 01:40:13.637 network: info: listening on IPv6 interface tapeth0-38e012, fe80::d857:bbff:fec7:1d1%34#53
02-Feb-2026 01:40:13.638 network: info: listening on IPv6 interface tapeth0-26959c, fe80::e077:b7ff:fe19:98a1%36#53
02-Feb-2026 01:40:23.573 network: info: listening on IPv4 interface kube-ipvs0, 10.100.17.255#53
02-Feb-2026 01:43:34.006 network: info: no longer listening on fe80::ac09:6fff:fe1d:df61%28#53
02-Feb-2026 01:43:34.025 network: info: no longer listening on fe80::1495:bff:feb0:454e%22#53
02-Feb-2026 01:43:34.044 network: info: no longer listening on fe80::7cfe:56ff:fe22:73f7%24#53
02-Feb-2026 01:43:34.064 network: info: no longer listening on fe80::4e5:4ff:feed:70cb%26#53
02-Feb-2026 01:44:04.090 network: info: no longer listening on fe80::98bc:76ff:fe6a:6d30%32#53
02-Feb-2026 01:44:04.116 network: info: no longer listening on fe80::e077:b7ff:fe19:98a1%36#53
02-Feb-2026 01:44:04.135 network: info: no longer listening on fe80::d857:bbff:fec7:1d1%34#53
02-Feb-2026 01:44:04.146 network: info: no longer listening on fe80::7832:e2ff:fee7:1c98%30#53
02-Feb-2026 01:44:19.933 network: info: no longer listening on 10.100.17.255#53