29-Jan-2026 01:37:12.063 general: debug 1: now using logging configuration from config file
29-Jan-2026 01:37:12.063 general: debug 1: loop exclusive mode: ending
29-Jan-2026 01:37:12.063 general: debug 1: loop exclusive mode: ended
29-Jan-2026 01:37:12.063 general: notice: command channel listening on 127.0.0.1#8094
29-Jan-2026 01:37:12.063 general: debug 1: load_configuration: success
29-Jan-2026 01:37:12.063 general: debug 1: loop exclusive mode: starting
29-Jan-2026 01:37:12.102 general: debug 1: loop exclusive mode: started
29-Jan-2026 01:37:12.102 zoneload: debug 1: managed-keys-zone: starting load
29-Jan-2026 01:37:12.102 general: debug 1: zone_startload: managed-keys-zone: enter
29-Jan-2026 01:37:12.102 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
29-Jan-2026 01:37:12.102 general: debug 1: managed-keys-zone: creating SOA
29-Jan-2026 01:37:12.102 zoneload: debug 1: managed-keys-zone: loaded; checking validity
29-Jan-2026 01:37:12.102 zoneload: info: managed-keys-zone: loaded serial 0
29-Jan-2026 01:37:12.102 general: debug 1: loop exclusive mode: ending
29-Jan-2026 01:37:12.103 zoneload: debug 1: zone id.server/CH: starting load
29-Jan-2026 01:37:12.103 zoneload: debug 1: zone id.server/CH: loaded; checking validity
29-Jan-2026 01:37:12.103 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
29-Jan-2026 01:37:12.103 general: debug 1: zone__settimer: zone id.server/CH: enter
29-Jan-2026 01:37:12.103 general: debug 1: zone_maintenance: zone id.server/CH: enter
29-Jan-2026 01:37:12.103 general: debug 1: zone__settimer: zone id.server/CH: enter
29-Jan-2026 01:37:12.103 zoneload: debug 1: zone version.bind/CH: starting load
29-Jan-2026 01:37:12.103 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
29-Jan-2026 01:37:12.103 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
29-Jan-2026 01:37:12.103 general: debug 1: zone__settimer: zone version.bind/CH: enter
29-Jan-2026 01:37:12.103 general: debug 1: zone_maintenance: zone version.bind/CH: enter
29-Jan-2026 01:37:12.103 general: debug 1: zone__settimer: zone version.bind/CH: enter
29-Jan-2026 01:37:12.103 zoneload: debug 1: zone authors.bind/CH: starting load
29-Jan-2026 01:37:12.103 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
29-Jan-2026 01:37:12.103 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
29-Jan-2026 01:37:12.103 zoneload: debug 1: zone hostname.bind/CH: starting load
29-Jan-2026 01:37:12.103 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
29-Jan-2026 01:37:12.103 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
29-Jan-2026 01:37:12.103 general: notice: all zones loaded
29-Jan-2026 01:37:12.103 general: debug 1: managed-keys-zone: synchronizing trusted keys
29-Jan-2026 01:37:12.103 general: debug 1: create_keydata: managed-keys-zone: enter
29-Jan-2026 01:37:12.103 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
29-Jan-2026 01:37:12.103 general: debug 1: managed-keys-zone: next key refresh: 29-Jan-2026 01:37:12.103
29-Jan-2026 01:37:12.103 general: debug 1: zone_journal: managed-keys-zone: enter
29-Jan-2026 01:37:12.103 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
29-Jan-2026 01:37:12.103 general: debug 1: loop exclusive mode: ended
29-Jan-2026 01:37:12.103 general: debug 1: zone__settimer: managed-keys-zone: enter
29-Jan-2026 01:37:12.123 general: debug 1: zone_needdump: managed-keys-zone: enter
29-Jan-2026 01:37:12.140 general: debug 1: zone__settimer: zone version.bind/CH: enter
29-Jan-2026 01:37:12.140 general: notice: FIPS mode is disabled
29-Jan-2026 01:37:12.140 general: notice: running
29-Jan-2026 01:37:12.140 general: debug 1: zone__settimer: zone authors.bind/CH: enter
29-Jan-2026 01:37:12.140 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
29-Jan-2026 01:37:12.140 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
29-Jan-2026 01:37:12.140 general: debug 1: zone__settimer: zone authors.bind/CH: enter
29-Jan-2026 01:37:12.140 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
29-Jan-2026 01:37:12.140 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
29-Jan-2026 01:37:12.140 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
29-Jan-2026 01:37:12.140 general: debug 1: zone__settimer: zone authors.bind/CH: enter
29-Jan-2026 01:37:12.140 general: debug 1: zone__settimer: zone id.server/CH: enter
29-Jan-2026 01:37:12.140 general: debug 1: zone__settimer: managed-keys-zone: enter
29-Jan-2026 01:37:12.140 general: debug 1: zone_maintenance: managed-keys-zone: enter
29-Jan-2026 01:37:12.140 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
29-Jan-2026 01:37:12.140 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
29-Jan-2026 01:37:12.140 general: debug 1: managed-keys-zone: next key refresh: 29-Jan-2026 01:37:12.140
29-Jan-2026 01:37:12.140 general: debug 1: zone__settimer: managed-keys-zone: enter
29-Jan-2026 01:37:12.140 general: debug 1: zone__settimer: managed-keys-zone: enter
29-Jan-2026 01:37:12.140 general: debug 1: zone__settimer: managed-keys-zone: enter
29-Jan-2026 01:37:12.140 resolver: debug 1: fetch: ./DNSKEY
29-Jan-2026 01:37:12.140 general: debug 1: zone__settimer: managed-keys-zone: enter
29-Jan-2026 01:37:12.140 resolver: debug 1: fetch: ./NS
29-Jan-2026 01:37:12.140 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
29-Jan-2026 01:37:12.141 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
29-Jan-2026 01:37:12.142 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
29-Jan-2026 01:37:12.145 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.
29-Jan-2026 01:37:12.145 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
29-Jan-2026 01:37:12.145 general: debug 1: managed-keys-zone: next key refresh: 30-Jan-2026 01:37:12.145
29-Jan-2026 01:37:12.145 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.
29-Jan-2026 01:37:12.145 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
29-Jan-2026 01:37:12.145 general: debug 1: managed-keys-zone: next key refresh: 30-Jan-2026 01:37:12.145
29-Jan-2026 01:37:12.145 general: debug 1: zone_journal: managed-keys-zone: enter
29-Jan-2026 01:37:12.197 general: debug 1: zone_needdump: managed-keys-zone: enter
29-Jan-2026 01:37:12.197 general: debug 1: zone__settimer: managed-keys-zone: enter
29-Jan-2026 01:37:12.197 general: debug 1: zone__settimer: managed-keys-zone: enter
29-Jan-2026 01:37:12.197 general: debug 1: zone__settimer: managed-keys-zone: enter
29-Jan-2026 01:37:12.200 resolver: debug 1: resolver priming query complete: success
29-Jan-2026 01:37:36.222 general: debug 1: zone_maintenance: managed-keys-zone: enter
29-Jan-2026 01:37:36.222 general: debug 1: zone_dump: managed-keys-zone: enter
29-Jan-2026 01:37:36.224 general: debug 1: zone__settimer: managed-keys-zone: enter
29-Jan-2026 01:37:36.228 general: debug 1: dump_done: managed-keys-zone: enter
29-Jan-2026 01:37:36.228 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
29-Jan-2026 01:38:04.824 network: info: listening on IPv6 interface tapeth0-153cdb, fe80::54b6:95ff:fe4b:d97f%11#53
29-Jan-2026 01:38:04.825 network: info: listening on IPv6 interface tapeth0-476f53, fe80::c073:17ff:fe1e:15d%13#53
29-Jan-2026 01:39:44.719 network: info: listening on IPv4 interface kube-ipvs0, 10.110.125.235#53
29-Jan-2026 01:39:52.733 network: info: listening on IPv6 interface tapeth0-3ac0d1, fe80::74a0:14ff:fef4:1d99%15#53
29-Jan-2026 01:39:52.739 network: info: listening on IPv6 interface tapeth0-75190b, fe80::58db:17ff:fe50:45b%17#53
29-Jan-2026 01:39:56.764 network: info: listening on IPv6 interface vethc2bd2a1a-1, fe80::b032:c3ff:fe68:13bb%18#53
29-Jan-2026 01:40:01.880 network: info: listening on IPv6 interface tapeth0-1b0d2f, fe80::1448:8cff:fe74:6adc%20#53
29-Jan-2026 01:40:35.599 network: info: no longer listening on fe80::1448:8cff:fe74:6adc%20#53
29-Jan-2026 01:40:41.961 network: info: no longer listening on fe80::b032:c3ff:fe68:13bb%18#53
29-Jan-2026 01:40:42.770 network: info: no longer listening on fe80::58db:17ff:fe50:45b%17#53
29-Jan-2026 01:40:47.672 network: info: no longer listening on fe80::74a0:14ff:fef4:1d99%15#53
29-Jan-2026 01:41:07.610 network: info: listening on IPv6 interface tapeth0-23e189, fe80::10d4:83ff:fed4:2e42%22#53
29-Jan-2026 01:41:07.611 network: info: listening on IPv6 interface tapeth0-3591c9, fe80::24e2:85ff:fec5:c7bb%24#53
29-Jan-2026 01:41:07.612 network: info: listening on IPv6 interface tapeth0-ea89df, fe80::3406:3eff:fee5:889a%26#53
29-Jan-2026 01:41:12.728 network: info: listening on IPv6 interface tapeth0-77fb58, fe80::9830:11ff:fe14:f046%28#53
29-Jan-2026 01:41:12.730 network: info: listening on IPv6 interface tapeth0-0219e6, fe80::44c0:88ff:fe64:5e90%30#53
29-Jan-2026 01:41:12.730 network: info: listening on IPv6 interface tapeth0-ba154e, fe80::70cf:edff:fe18:6415%32#53
29-Jan-2026 01:41:17.592 network: info: listening on IPv6 interface tapeth0-c0d9ca, fe80::2849:10ff:fe82:55ec%34#53
29-Jan-2026 01:41:17.592 network: info: listening on IPv6 interface tapeth0-391ad7, fe80::17:caff:fe4c:18b%36#53
29-Jan-2026 01:41:26.901 network: info: listening on IPv4 interface kube-ipvs0, 10.108.18.251#53
29-Jan-2026 01:44:35.762 network: info: no longer listening on fe80::10d4:83ff:fed4:2e42%22#53
29-Jan-2026 01:44:35.774 network: info: no longer listening on fe80::24e2:85ff:fec5:c7bb%24#53
29-Jan-2026 01:44:35.774 network: info: no longer listening on fe80::3406:3eff:fee5:889a%26#53
29-Jan-2026 01:44:35.800 network: info: no longer listening on fe80::9830:11ff:fe14:f046%28#53
29-Jan-2026 01:45:05.738 network: info: no longer listening on fe80::44c0:88ff:fe64:5e90%30#53
29-Jan-2026 01:45:05.765 network: info: no longer listening on fe80::17:caff:fe4c:18b%36#53
29-Jan-2026 01:45:05.786 network: info: no longer listening on fe80::70cf:edff:fe18:6415%32#53
29-Jan-2026 01:45:05.865 network: info: no longer listening on fe80::2849:10ff:fe82:55ec%34#53
29-Jan-2026 01:45:21.494 network: info: no longer listening on 10.108.18.251#53