19-Mar-2026 01:54:07.441 general: debug 1: now using logging configuration from config file
19-Mar-2026 01:54:07.441 general: debug 1: loop exclusive mode: ending
19-Mar-2026 01:54:07.443 general: debug 1: loop exclusive mode: ended
19-Mar-2026 01:54:07.443 general: notice: command channel listening on 127.0.0.1#8094
19-Mar-2026 01:54:07.443 general: debug 1: load_configuration: success
19-Mar-2026 01:54:07.443 general: debug 1: loop exclusive mode: starting
19-Mar-2026 01:54:07.443 general: debug 1: loop exclusive mode: started
19-Mar-2026 01:54:07.443 zoneload: debug 1: managed-keys-zone: starting load
19-Mar-2026 01:54:07.443 general: debug 1: zone_startload: managed-keys-zone: enter
19-Mar-2026 01:54:07.443 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
19-Mar-2026 01:54:07.443 general: debug 1: managed-keys-zone: creating SOA
19-Mar-2026 01:54:07.444 zoneload: debug 1: managed-keys-zone: loaded; checking validity
19-Mar-2026 01:54:07.444 zoneload: info: managed-keys-zone: loaded serial 0
19-Mar-2026 01:54:07.444 general: debug 1: loop exclusive mode: ending
19-Mar-2026 01:54:07.444 general: debug 1: loop exclusive mode: ended
19-Mar-2026 01:54:07.444 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Mar-2026 01:54:07.444 zoneload: debug 1: zone authors.bind/CH: starting load
19-Mar-2026 01:54:07.444 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
19-Mar-2026 01:54:07.444 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
19-Mar-2026 01:54:07.444 zoneload: debug 1: zone id.server/CH: starting load
19-Mar-2026 01:54:07.444 zoneload: debug 1: zone id.server/CH: loaded; checking validity
19-Mar-2026 01:54:07.444 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
19-Mar-2026 01:54:07.444 general: debug 1: zone__settimer: zone authors.bind/CH: enter
19-Mar-2026 01:54:07.444 general: debug 1: zone__settimer: zone id.server/CH: enter
19-Mar-2026 01:54:07.444 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
19-Mar-2026 01:54:07.444 general: debug 1: zone_maintenance: zone id.server/CH: enter
19-Mar-2026 01:54:07.444 general: debug 1: zone__settimer: zone authors.bind/CH: enter
19-Mar-2026 01:54:07.444 general: debug 1: zone__settimer: zone id.server/CH: enter
19-Mar-2026 01:54:07.447 zoneload: debug 1: zone hostname.bind/CH: starting load
19-Mar-2026 01:54:07.447 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
19-Mar-2026 01:54:07.447 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
19-Mar-2026 01:54:07.447 zoneload: debug 1: zone version.bind/CH: starting load
19-Mar-2026 01:54:07.447 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
19-Mar-2026 01:54:07.447 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
19-Mar-2026 01:54:07.447 general: notice: all zones loaded
19-Mar-2026 01:54:07.447 general: debug 1: managed-keys-zone: synchronizing trusted keys
19-Mar-2026 01:54:07.447 general: debug 1: create_keydata: managed-keys-zone: enter
19-Mar-2026 01:54:07.447 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
19-Mar-2026 01:54:07.447 general: debug 1: managed-keys-zone: next key refresh: 19-Mar-2026 01:54:07.447
19-Mar-2026 01:54:07.447 general: debug 1: zone_journal: managed-keys-zone: enter
19-Mar-2026 01:54:07.447 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
19-Mar-2026 01:54:07.447 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Mar-2026 01:54:07.457 general: debug 1: zone_needdump: managed-keys-zone: enter
19-Mar-2026 01:54:07.457 general: notice: FIPS mode is disabled
19-Mar-2026 01:54:07.457 general: notice: running
19-Mar-2026 01:54:07.457 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
19-Mar-2026 01:54:07.457 general: debug 1: zone__settimer: zone version.bind/CH: enter
19-Mar-2026 01:54:07.457 general: debug 1: zone__settimer: zone version.bind/CH: enter
19-Mar-2026 01:54:07.457 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
19-Mar-2026 01:54:07.457 general: debug 1: zone_maintenance: zone version.bind/CH: enter
19-Mar-2026 01:54:07.457 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
19-Mar-2026 01:54:07.457 general: debug 1: zone__settimer: zone version.bind/CH: enter
19-Mar-2026 01:54:07.457 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
19-Mar-2026 01:54:07.457 general: debug 1: zone_maintenance: managed-keys-zone: enter
19-Mar-2026 01:54:07.457 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
19-Mar-2026 01:54:07.457 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
19-Mar-2026 01:54:07.457 general: debug 1: managed-keys-zone: next key refresh: 19-Mar-2026 01:54:07.457
19-Mar-2026 01:54:07.457 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Mar-2026 01:54:07.457 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Mar-2026 01:54:07.457 general: debug 1: zone__settimer: zone authors.bind/CH: enter
19-Mar-2026 01:54:07.457 general: debug 1: zone__settimer: zone id.server/CH: enter
19-Mar-2026 01:54:07.457 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Mar-2026 01:54:07.457 resolver: debug 1: fetch: ./DNSKEY
19-Mar-2026 01:54:07.457 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Mar-2026 01:54:07.457 resolver: debug 1: fetch: ./NS
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
19-Mar-2026 01:54:07.458 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
19-Mar-2026 01:54:07.635 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-Mar-2026 01:54:07.635 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
19-Mar-2026 01:54:07.635 general: debug 1: managed-keys-zone: next key refresh: 20-Mar-2026 01:54:07.635
19-Mar-2026 01:54:07.635 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-Mar-2026 01:54:07.635 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
19-Mar-2026 01:54:07.635 general: debug 1: managed-keys-zone: next key refresh: 20-Mar-2026 01:54:07.635
19-Mar-2026 01:54:07.635 general: debug 1: zone_journal: managed-keys-zone: enter
19-Mar-2026 01:54:07.654 general: debug 1: zone_needdump: managed-keys-zone: enter
19-Mar-2026 01:54:07.654 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Mar-2026 01:54:07.654 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Mar-2026 01:54:07.654 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Mar-2026 01:54:07.690 resolver: debug 1: resolver priming query complete: success
19-Mar-2026 01:54:31.480 general: debug 1: zone_maintenance: managed-keys-zone: enter
19-Mar-2026 01:54:31.480 general: debug 1: zone_dump: managed-keys-zone: enter
19-Mar-2026 01:54:31.483 general: debug 1: zone__settimer: managed-keys-zone: enter
19-Mar-2026 01:54:31.501 general: debug 1: dump_done: managed-keys-zone: enter
19-Mar-2026 01:54:31.501 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
19-Mar-2026 01:54:58.793 network: info: listening on IPv6 interface tapeth0-0e1d11, fe80::bc65:20ff:fe6a:7f1%11#53
19-Mar-2026 01:54:58.804 network: info: listening on IPv6 interface tapeth0-0c8d04, fe80::a085:54ff:fe11:cb8c%13#53
19-Mar-2026 01:56:28.358 network: info: listening on IPv4 interface kube-ipvs0, 10.98.223.43#53
19-Mar-2026 01:56:36.141 network: info: listening on IPv6 interface tapeth0-f938ec, fe80::b89b:9eff:febf:6a1e%15#53
19-Mar-2026 01:56:36.162 network: info: listening on IPv6 interface tapeth0-4cc44c, fe80::dc3d:90ff:fed1:1086%17#53
19-Mar-2026 01:56:38.249 network: info: listening on IPv6 interface veth0ca562f5-e, fe80::44b4:80ff:fe50:54e%18#53
19-Mar-2026 01:56:44.713 network: info: listening on IPv6 interface tapeth0-cacb10, fe80::9cb8:e2ff:fe51:8a5f%20#53
19-Mar-2026 01:57:22.451 network: info: no longer listening on fe80::9cb8:e2ff:fe51:8a5f%20#53
19-Mar-2026 01:57:29.325 network: info: no longer listening on fe80::44b4:80ff:fe50:54e%18#53
19-Mar-2026 01:57:29.967 network: info: no longer listening on fe80::b89b:9eff:febf:6a1e%15#53
19-Mar-2026 01:57:35.113 network: info: no longer listening on fe80::dc3d:90ff:fed1:1086%17#53
19-Mar-2026 01:57:54.601 network: info: listening on IPv6 interface tapeth0-64af1b, fe80::1420:d8ff:fe93:f986%22#53
19-Mar-2026 01:57:54.602 network: info: listening on IPv6 interface tapeth0-59a6b6, fe80::dc6a:70ff:fecc:21e%24#53
19-Mar-2026 01:57:54.602 network: info: listening on IPv6 interface tapeth0-840e6e, fe80::84c4:daff:fe3d:1f7f%26#53
19-Mar-2026 01:57:59.979 network: info: listening on IPv6 interface tapeth0-79a55f, fe80::8051:4aff:feac:5f4f%28#53
19-Mar-2026 01:57:59.991 network: info: listening on IPv6 interface tapeth0-d90b0d, fe80::c39:21ff:fe78:791e%30#53
19-Mar-2026 01:57:59.995 network: info: listening on IPv6 interface tapeth0-e00d9b, fe80::5c6a:ecff:fe04:c453%32#53
19-Mar-2026 01:58:04.970 network: info: listening on IPv6 interface tapeth0-d7063b, fe80::855:52ff:fe92:dbae%34#53
19-Mar-2026 01:58:04.971 network: info: listening on IPv6 interface tapeth0-e26d27, fe80::c847:bbff:fe49:a49f%36#53
19-Mar-2026 01:58:14.189 network: info: listening on IPv4 interface kube-ipvs0, 10.111.77.44#53
19-Mar-2026 02:01:23.578 network: info: no longer listening on fe80::c39:21ff:fe78:791e%30#53
19-Mar-2026 02:01:23.590 network: info: no longer listening on fe80::84c4:daff:fe3d:1f7f%26#53
19-Mar-2026 02:01:23.619 network: info: no longer listening on fe80::1420:d8ff:fe93:f986%22#53
19-Mar-2026 02:01:23.648 network: info: no longer listening on fe80::dc6a:70ff:fecc:21e%24#53
19-Mar-2026 02:01:54.061 network: info: no longer listening on fe80::8051:4aff:feac:5f4f%28#53
19-Mar-2026 02:01:54.061 network: info: no longer listening on fe80::5c6a:ecff:fe04:c453%32#53
19-Mar-2026 02:01:54.070 network: info: no longer listening on fe80::c847:bbff:fe49:a49f%36#53
19-Mar-2026 02:01:54.098 network: info: no longer listening on fe80::855:52ff:fe92:dbae%34#53
19-Mar-2026 02:02:09.771 network: info: no longer listening on 10.111.77.44#53