17-Nov-2025 01:32:25.177 general: debug 1: now using logging configuration from config file
17-Nov-2025 01:32:25.177 general: debug 1: loop exclusive mode: ending
17-Nov-2025 01:32:25.177 general: debug 1: loop exclusive mode: ended
17-Nov-2025 01:32:25.177 general: notice: command channel listening on 127.0.0.1#8094
17-Nov-2025 01:32:25.178 general: debug 1: load_configuration: success
17-Nov-2025 01:32:25.178 general: debug 1: loop exclusive mode: starting
17-Nov-2025 01:32:25.180 general: debug 1: loop exclusive mode: started
17-Nov-2025 01:32:25.180 zoneload: debug 1: managed-keys-zone: starting load
17-Nov-2025 01:32:25.180 general: debug 1: zone_startload: managed-keys-zone: enter
17-Nov-2025 01:32:25.180 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
17-Nov-2025 01:32:25.180 general: debug 1: managed-keys-zone: creating SOA
17-Nov-2025 01:32:25.180 zoneload: debug 1: managed-keys-zone: loaded; checking validity
17-Nov-2025 01:32:25.180 zoneload: info: managed-keys-zone: loaded serial 0
17-Nov-2025 01:32:25.180 general: debug 1: loop exclusive mode: ending
17-Nov-2025 01:32:25.180 zoneload: debug 1: zone authors.bind/CH: starting load
17-Nov-2025 01:32:25.180 zoneload: debug 1: zone version.bind/CH: starting load
17-Nov-2025 01:32:25.180 general: debug 1: loop exclusive mode: ended
17-Nov-2025 01:32:25.180 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
17-Nov-2025 01:32:25.180 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
17-Nov-2025 01:32:25.180 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
17-Nov-2025 01:32:25.180 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
17-Nov-2025 01:32:25.180 zoneload: debug 1: zone hostname.bind/CH: starting load
17-Nov-2025 01:32:25.180 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
17-Nov-2025 01:32:25.180 zoneload: debug 1: zone id.server/CH: starting load
17-Nov-2025 01:32:25.180 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
17-Nov-2025 01:32:25.180 zoneload: debug 1: zone id.server/CH: loaded; checking validity
17-Nov-2025 01:32:25.180 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
17-Nov-2025 01:32:25.180 general: debug 1: zone__settimer: zone authors.bind/CH: enter
17-Nov-2025 01:32:25.180 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
17-Nov-2025 01:32:25.180 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
17-Nov-2025 01:32:25.180 general: notice: all zones loaded
17-Nov-2025 01:32:25.180 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
17-Nov-2025 01:32:25.180 general: debug 1: zone__settimer: managed-keys-zone: enter
17-Nov-2025 01:32:25.180 general: debug 1: managed-keys-zone: synchronizing trusted keys
17-Nov-2025 01:32:25.180 general: debug 1: zone__settimer: zone authors.bind/CH: enter
17-Nov-2025 01:32:25.180 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
17-Nov-2025 01:32:25.180 general: debug 1: create_keydata: managed-keys-zone: enter
17-Nov-2025 01:32:25.180 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
17-Nov-2025 01:32:25.180 general: debug 1: managed-keys-zone: next key refresh: 17-Nov-2025 01:32:25.180
17-Nov-2025 01:32:25.180 general: debug 1: zone_journal: managed-keys-zone: enter
17-Nov-2025 01:32:25.181 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
17-Nov-2025 01:32:25.192 general: debug 1: zone_needdump: managed-keys-zone: enter
17-Nov-2025 01:32:25.192 general: notice: FIPS mode is disabled
17-Nov-2025 01:32:25.192 general: notice: running
17-Nov-2025 01:32:25.192 general: debug 1: zone__settimer: zone version.bind/CH: enter
17-Nov-2025 01:32:25.192 general: debug 1: zone__settimer: zone id.server/CH: enter
17-Nov-2025 01:32:25.192 general: debug 1: zone__settimer: zone version.bind/CH: enter
17-Nov-2025 01:32:25.192 general: debug 1: zone__settimer: zone id.server/CH: enter
17-Nov-2025 01:32:25.192 general: debug 1: zone_maintenance: zone version.bind/CH: enter
17-Nov-2025 01:32:25.192 general: debug 1: zone_maintenance: zone id.server/CH: enter
17-Nov-2025 01:32:25.192 general: debug 1: zone__settimer: zone version.bind/CH: enter
17-Nov-2025 01:32:25.192 general: debug 1: zone__settimer: zone id.server/CH: enter
17-Nov-2025 01:32:25.192 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
17-Nov-2025 01:32:25.192 general: debug 1: zone__settimer: zone authors.bind/CH: enter
17-Nov-2025 01:32:25.192 general: debug 1: zone_maintenance: managed-keys-zone: enter
17-Nov-2025 01:32:25.192 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
17-Nov-2025 01:32:25.192 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
17-Nov-2025 01:32:25.192 general: debug 1: managed-keys-zone: next key refresh: 17-Nov-2025 01:32:25.192
17-Nov-2025 01:32:25.192 general: debug 1: zone__settimer: managed-keys-zone: enter
17-Nov-2025 01:32:25.192 general: debug 1: zone__settimer: managed-keys-zone: enter
17-Nov-2025 01:32:25.192 general: debug 1: zone__settimer: managed-keys-zone: enter
17-Nov-2025 01:32:25.192 general: debug 1: zone__settimer: managed-keys-zone: enter
17-Nov-2025 01:32:25.192 resolver: debug 1: fetch: ./DNSKEY
17-Nov-2025 01:32:25.192 general: debug 1: zone__settimer: managed-keys-zone: enter
17-Nov-2025 01:32:25.192 resolver: debug 1: fetch: ./NS
17-Nov-2025 01:32:25.193 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
17-Nov-2025 01:32:25.193 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
17-Nov-2025 01:32:25.193 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
17-Nov-2025 01:32:25.193 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
17-Nov-2025 01:32:25.193 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
17-Nov-2025 01:32:25.193 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
17-Nov-2025 01:32:25.193 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
17-Nov-2025 01:32:25.193 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
17-Nov-2025 01:32:25.193 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
17-Nov-2025 01:32:25.193 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
17-Nov-2025 01:32:25.193 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
17-Nov-2025 01:32:25.193 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
17-Nov-2025 01:32:25.193 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
17-Nov-2025 01:32:25.193 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
17-Nov-2025 01:32:25.193 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
17-Nov-2025 01:32:25.193 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
17-Nov-2025 01:32:25.194 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
17-Nov-2025 01:32:25.194 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
17-Nov-2025 01:32:25.194 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
17-Nov-2025 01:32:25.194 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
17-Nov-2025 01:32:25.194 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
17-Nov-2025 01:32:25.194 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
17-Nov-2025 01:32:25.194 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
17-Nov-2025 01:32:25.194 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
17-Nov-2025 01:32:25.194 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
17-Nov-2025 01:32:25.205 lame-servers: info: SERVFAIL unexpected RCODE resolving './NS/IN': 192.36.148.17#53
17-Nov-2025 01:32:25.206 lame-servers: info: SERVFAIL unexpected RCODE resolving './DNSKEY/IN': 192.36.148.17#53
17-Nov-2025 01:32:25.207 database: debug 1: delete_node(): 0xd5bb80 . (bucket 1)
17-Nov-2025 01:32:25.207 resolver: debug 1: fetch: ./DNSKEY
17-Nov-2025 01:32:25.208 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
17-Nov-2025 01:32:25.208 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
17-Nov-2025 01:32:25.208 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
17-Nov-2025 01:32:25.208 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
17-Nov-2025 01:32:25.208 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.
17-Nov-2025 01:32:25.208 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
17-Nov-2025 01:32:25.208 general: debug 1: managed-keys-zone: next key refresh: 18-Nov-2025 01:32:25.208
17-Nov-2025 01:32:25.209 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.
17-Nov-2025 01:32:25.209 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
17-Nov-2025 01:32:25.209 general: debug 1: managed-keys-zone: next key refresh: 18-Nov-2025 01:32:25.208
17-Nov-2025 01:32:25.209 general: debug 1: zone_journal: managed-keys-zone: enter
17-Nov-2025 01:32:25.249 general: debug 1: zone_needdump: managed-keys-zone: enter
17-Nov-2025 01:32:25.249 general: debug 1: zone__settimer: managed-keys-zone: enter
17-Nov-2025 01:32:25.249 general: debug 1: zone__settimer: managed-keys-zone: enter
17-Nov-2025 01:32:25.249 general: debug 1: zone__settimer: managed-keys-zone: enter
17-Nov-2025 01:32:25.261 resolver: debug 1: resolver priming query complete: success
17-Nov-2025 01:32:49.216 general: debug 1: zone_maintenance: managed-keys-zone: enter
17-Nov-2025 01:32:49.216 general: debug 1: zone_dump: managed-keys-zone: enter
17-Nov-2025 01:32:49.219 general: debug 1: zone__settimer: managed-keys-zone: enter
17-Nov-2025 01:32:49.222 general: debug 1: dump_done: managed-keys-zone: enter
17-Nov-2025 01:32:49.222 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
17-Nov-2025 01:32:58.636 network: info: listening on IPv6 interface tapeth0-b44f9f, fe80::a4c3:3dff:fe24:4827%11#53
17-Nov-2025 01:32:58.669 network: info: listening on IPv6 interface tapeth0-d40112, fe80::f489:b8ff:fe88:2258%13#53
17-Nov-2025 01:34:59.022 network: info: listening on IPv4 interface kube-ipvs0, 10.97.76.197#53
17-Nov-2025 01:35:06.699 network: info: listening on IPv6 interface tapeth0-24df36, fe80::1ccf:85ff:fe66:d34a%15#53
17-Nov-2025 01:35:06.702 network: info: listening on IPv6 interface tapeth0-95151c, fe80::48ae:7dff:fe25:5d03%17#53
17-Nov-2025 01:35:11.438 network: info: listening on IPv6 interface veth2b49719d-b, fe80::6cd4:5eff:fe0b:a2d9%18#53
17-Nov-2025 01:35:17.386 network: info: listening on IPv6 interface tapeth0-354c5a, fe80::2021:fdff:fe1c:ef9%20#53
17-Nov-2025 01:35:55.079 network: info: no longer listening on fe80::2021:fdff:fe1c:ef9%20#53
17-Nov-2025 01:36:01.267 network: info: no longer listening on fe80::6cd4:5eff:fe0b:a2d9%18#53
17-Nov-2025 01:36:02.346 network: info: no longer listening on fe80::1ccf:85ff:fe66:d34a%15#53
17-Nov-2025 01:36:07.379 network: info: no longer listening on fe80::48ae:7dff:fe25:5d03%17#53
17-Nov-2025 01:36:27.082 network: info: listening on IPv6 interface tapeth0-91bab5, fe80::e4f8:dbff:fe74:15ef%22#53
17-Nov-2025 01:36:27.085 network: info: listening on IPv6 interface tapeth0-dff222, fe80::e84a:aaff:fe55:2945%24#53
17-Nov-2025 01:36:27.085 network: info: listening on IPv6 interface tapeth0-509e62, fe80::80c3:75ff:fe77:eba0%26#53
17-Nov-2025 01:36:32.843 network: info: listening on IPv6 interface tapeth0-5620cc, fe80::c0f5:24ff:fe8b:9c22%28#53
17-Nov-2025 01:36:32.852 network: info: listening on IPv6 interface tapeth0-af9744, fe80::40de:e2ff:fe95:c60e%30#53
17-Nov-2025 01:36:32.854 network: info: listening on IPv6 interface tapeth0-8f91f3, fe80::482e:aaff:fe1b:7f5d%32#53
17-Nov-2025 01:36:32.854 network: info: listening on IPv6 interface tapeth0-b866ee, fe80::90ff:eaff:fe75:5269%34#53
17-Nov-2025 01:36:37.707 network: info: listening on IPv6 interface tapeth0-7610a3, fe80::50b7:ddff:feb2:1213%36#53
17-Nov-2025 01:36:46.667 network: info: listening on IPv4 interface kube-ipvs0, 10.110.130.59#53
17-Nov-2025 01:39:55.481 network: info: no longer listening on fe80::e4f8:dbff:fe74:15ef%22#53
17-Nov-2025 01:39:55.510 network: info: no longer listening on fe80::80c3:75ff:fe77:eba0%26#53
17-Nov-2025 01:39:55.527 network: info: no longer listening on fe80::e84a:aaff:fe55:2945%24#53
17-Nov-2025 01:39:55.532 network: info: no longer listening on fe80::482e:aaff:fe1b:7f5d%32#53
17-Nov-2025 01:40:26.022 network: info: no longer listening on fe80::40de:e2ff:fe95:c60e%30#53
17-Nov-2025 01:40:26.053 network: info: no longer listening on fe80::90ff:eaff:fe75:5269%34#53
17-Nov-2025 01:40:26.065 network: info: no longer listening on fe80::50b7:ddff:feb2:1213%36#53
17-Nov-2025 01:40:26.079 network: info: no longer listening on fe80::c0f5:24ff:fe8b:9c22%28#53
17-Nov-2025 01:40:41.473 network: info: no longer listening on 10.110.130.59#53