12-Jan-2026 01:33:24.004 general: debug 1: now using logging configuration from config file
12-Jan-2026 01:33:24.004 general: debug 1: loop exclusive mode: ending
12-Jan-2026 01:33:24.004 general: debug 1: loop exclusive mode: ended
12-Jan-2026 01:33:24.004 general: notice: command channel listening on 127.0.0.1#8094
12-Jan-2026 01:33:24.005 general: debug 1: load_configuration: success
12-Jan-2026 01:33:24.005 general: debug 1: loop exclusive mode: starting
12-Jan-2026 01:33:24.020 general: debug 1: loop exclusive mode: started
12-Jan-2026 01:33:24.020 zoneload: debug 1: managed-keys-zone: starting load
12-Jan-2026 01:33:24.020 general: debug 1: zone_startload: managed-keys-zone: enter
12-Jan-2026 01:33:24.020 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
12-Jan-2026 01:33:24.020 general: debug 1: managed-keys-zone: creating SOA
12-Jan-2026 01:33:24.020 zoneload: debug 1: managed-keys-zone: loaded; checking validity
12-Jan-2026 01:33:24.020 zoneload: info: managed-keys-zone: loaded serial 0
12-Jan-2026 01:33:24.020 general: debug 1: loop exclusive mode: ending
12-Jan-2026 01:33:24.020 zoneload: debug 1: zone authors.bind/CH: starting load
12-Jan-2026 01:33:24.020 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
12-Jan-2026 01:33:24.020 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
12-Jan-2026 01:33:24.020 general: debug 1: zone__settimer: zone authors.bind/CH: enter
12-Jan-2026 01:33:24.020 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
12-Jan-2026 01:33:24.020 general: debug 1: zone__settimer: zone authors.bind/CH: enter
12-Jan-2026 01:33:24.020 zoneload: debug 1: zone version.bind/CH: starting load
12-Jan-2026 01:33:24.021 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
12-Jan-2026 01:33:24.021 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
12-Jan-2026 01:33:24.021 zoneload: debug 1: zone id.server/CH: starting load
12-Jan-2026 01:33:24.021 zoneload: debug 1: zone id.server/CH: loaded; checking validity
12-Jan-2026 01:33:24.021 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
12-Jan-2026 01:33:24.021 general: debug 1: zone__settimer: zone version.bind/CH: enter
12-Jan-2026 01:33:24.021 general: debug 1: zone__settimer: zone id.server/CH: enter
12-Jan-2026 01:33:24.021 general: debug 1: zone_maintenance: zone version.bind/CH: enter
12-Jan-2026 01:33:24.021 general: debug 1: zone_maintenance: zone id.server/CH: enter
12-Jan-2026 01:33:24.021 general: debug 1: zone__settimer: zone version.bind/CH: enter
12-Jan-2026 01:33:24.021 general: debug 1: zone__settimer: zone id.server/CH: enter
12-Jan-2026 01:33:24.021 general: debug 1: loop exclusive mode: ended
12-Jan-2026 01:33:24.021 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Jan-2026 01:33:24.021 zoneload: debug 1: zone hostname.bind/CH: starting load
12-Jan-2026 01:33:24.021 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
12-Jan-2026 01:33:24.021 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
12-Jan-2026 01:33:24.021 general: notice: all zones loaded
12-Jan-2026 01:33:24.021 general: debug 1: managed-keys-zone: synchronizing trusted keys
12-Jan-2026 01:33:24.021 general: debug 1: create_keydata: managed-keys-zone: enter
12-Jan-2026 01:33:24.021 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
12-Jan-2026 01:33:24.021 general: debug 1: managed-keys-zone: next key refresh: 12-Jan-2026 01:33:24.021
12-Jan-2026 01:33:24.021 general: debug 1: zone_journal: managed-keys-zone: enter
12-Jan-2026 01:33:24.021 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
12-Jan-2026 01:33:24.035 general: debug 1: zone_needdump: managed-keys-zone: enter
12-Jan-2026 01:33:24.060 general: notice: FIPS mode is disabled
12-Jan-2026 01:33:24.060 general: notice: running
12-Jan-2026 01:33:24.060 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
12-Jan-2026 01:33:24.060 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Jan-2026 01:33:24.060 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Jan-2026 01:33:24.060 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Jan-2026 01:33:24.060 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
12-Jan-2026 01:33:24.060 general: debug 1: zone_maintenance: managed-keys-zone: enter
12-Jan-2026 01:33:24.060 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
12-Jan-2026 01:33:24.061 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
12-Jan-2026 01:33:24.061 general: debug 1: managed-keys-zone: next key refresh: 12-Jan-2026 01:33:24.061
12-Jan-2026 01:33:24.061 general: debug 1: zone__settimer: zone version.bind/CH: enter
12-Jan-2026 01:33:24.061 general: debug 1: zone__settimer: zone id.server/CH: enter
12-Jan-2026 01:33:24.061 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
12-Jan-2026 01:33:24.061 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Jan-2026 01:33:24.061 resolver: debug 1: fetch: ./DNSKEY
12-Jan-2026 01:33:24.061 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Jan-2026 01:33:24.061 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
12-Jan-2026 01:33:24.061 resolver: debug 1: fetch: ./NS
12-Jan-2026 01:33:24.061 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
12-Jan-2026 01:33:24.061 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
12-Jan-2026 01:33:24.061 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
12-Jan-2026 01:33:24.061 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
12-Jan-2026 01:33:24.061 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
12-Jan-2026 01:33:24.061 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
12-Jan-2026 01:33:24.061 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
12-Jan-2026 01:33:24.062 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
12-Jan-2026 01:33:24.073 general: debug 1: zone__settimer: zone authors.bind/CH: enter
12-Jan-2026 01:33:24.121 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-Jan-2026 01:33:24.121 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
12-Jan-2026 01:33:24.121 general: debug 1: managed-keys-zone: next key refresh: 13-Jan-2026 01:33:24.121
12-Jan-2026 01:33:24.121 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-Jan-2026 01:33:24.121 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
12-Jan-2026 01:33:24.121 general: debug 1: managed-keys-zone: next key refresh: 13-Jan-2026 01:33:24.121
12-Jan-2026 01:33:24.121 general: debug 1: zone_journal: managed-keys-zone: enter
12-Jan-2026 01:33:24.145 general: debug 1: zone_needdump: managed-keys-zone: enter
12-Jan-2026 01:33:24.145 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Jan-2026 01:33:24.145 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Jan-2026 01:33:24.145 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Jan-2026 01:33:24.154 resolver: debug 1: resolver priming query complete: success
12-Jan-2026 01:33:49.172 general: debug 1: zone_maintenance: managed-keys-zone: enter
12-Jan-2026 01:33:49.172 general: debug 1: zone_dump: managed-keys-zone: enter
12-Jan-2026 01:33:49.175 general: debug 1: zone__settimer: managed-keys-zone: enter
12-Jan-2026 01:33:49.178 general: debug 1: dump_done: managed-keys-zone: enter
12-Jan-2026 01:33:49.178 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
12-Jan-2026 01:33:54.550 network: info: listening on IPv6 interface tapeth0-d9e3bb, fe80::7406:c5ff:fe7d:edd1%11#53
12-Jan-2026 01:34:04.086 network: info: listening on IPv6 interface tapeth0-f53738, fe80::bc9a:38ff:fe83:ad57%13#53
12-Jan-2026 01:35:44.820 network: info: listening on IPv4 interface kube-ipvs0, 10.109.215.170#53
12-Jan-2026 01:35:53.333 network: info: listening on IPv6 interface tapeth0-fe22ba, fe80::c0a3:56ff:fe88:7806%15#53
12-Jan-2026 01:35:53.356 network: info: listening on IPv6 interface tapeth0-da8327, fe80::90bd:23ff:fe3a:549%17#53
12-Jan-2026 01:35:58.135 network: info: listening on IPv6 interface veth15a1c458-d, fe80::a491:5dff:fee4:c7ec%18#53
12-Jan-2026 01:36:02.428 network: info: listening on IPv6 interface tapeth0-fbbd9a, fe80::5c99:72ff:fee5:a8d3%20#53
12-Jan-2026 01:36:40.942 network: info: no longer listening on fe80::5c99:72ff:fee5:a8d3%20#53
12-Jan-2026 01:36:47.567 network: info: no longer listening on fe80::a491:5dff:fee4:c7ec%18#53
12-Jan-2026 01:36:48.563 network: info: no longer listening on fe80::c0a3:56ff:fe88:7806%15#53
12-Jan-2026 01:36:53.474 network: info: no longer listening on fe80::90bd:23ff:fe3a:549%17#53
12-Jan-2026 01:37:13.270 network: info: listening on IPv6 interface tapeth0-7a69f2, fe80::f076:7cff:fe88:7f1e%22#53
12-Jan-2026 01:37:13.273 network: info: listening on IPv6 interface tapeth0-bdb713, fe80::6090:d5ff:fe0f:c05b%24#53
12-Jan-2026 01:37:18.198 network: info: listening on IPv6 interface tapeth0-15ca52, fe80::b803:1fff:fe3c:5e5a%26#53
12-Jan-2026 01:37:18.201 network: info: listening on IPv6 interface tapeth0-2ef230, fe80::d447:55ff:fe72:a128%28#53
12-Jan-2026 01:37:18.202 network: info: listening on IPv6 interface tapeth0-92f2fd, fe80::8427:57ff:fe16:5ebc%30#53
12-Jan-2026 01:37:18.208 network: info: listening on IPv6 interface tapeth0-b9b2bb, fe80::f81f:30ff:fe0c:1297%32#53
12-Jan-2026 01:37:23.446 network: info: listening on IPv6 interface tapeth0-18bc1d, fe80::a007:71ff:fe68:e14a%34#53
12-Jan-2026 01:37:23.447 network: info: listening on IPv6 interface tapeth0-d2a976, fe80::ce3:d9ff:feaf:6768%36#53
12-Jan-2026 01:37:32.776 network: info: listening on IPv4 interface kube-ipvs0, 10.101.172.69#53
12-Jan-2026 01:40:42.688 network: info: no longer listening on fe80::6090:d5ff:fe0f:c05b%24#53
12-Jan-2026 01:40:43.068 network: info: no longer listening on fe80::f076:7cff:fe88:7f1e%22#53
12-Jan-2026 01:40:43.081 network: info: no longer listening on fe80::b803:1fff:fe3c:5e5a%26#53
12-Jan-2026 01:40:43.097 network: info: no longer listening on fe80::f81f:30ff:fe0c:1297%32#53
12-Jan-2026 01:41:13.042 network: info: no longer listening on fe80::8427:57ff:fe16:5ebc%30#53
12-Jan-2026 01:41:13.240 network: info: no longer listening on fe80::ce3:d9ff:feaf:6768%36#53
12-Jan-2026 01:41:13.254 network: info: no longer listening on fe80::a007:71ff:fe68:e14a%34#53
12-Jan-2026 01:41:13.298 network: info: no longer listening on fe80::d447:55ff:fe72:a128%28#53
12-Jan-2026 01:41:28.959 network: info: no longer listening on 10.101.172.69#53