18-May-2026 01:37:43.116 general: debug 1: now using logging configuration from config file
18-May-2026 01:37:43.116 general: debug 1: loop exclusive mode: ending
18-May-2026 01:37:43.116 general: debug 1: loop exclusive mode: ended
18-May-2026 01:37:43.116 general: notice: command channel listening on 127.0.0.1#8094
18-May-2026 01:37:43.116 general: info: VDNS cleanup pass1: 0 departing views cleared
18-May-2026 01:37:43.116 general: info: VDNS cleanup pass2: 2 staying views re-checked
18-May-2026 01:37:43.116 general: debug 1: load_configuration: success
18-May-2026 01:37:43.116 general: debug 1: loop exclusive mode: starting
18-May-2026 01:37:43.132 general: debug 1: loop exclusive mode: started
18-May-2026 01:37:43.132 zoneload: debug 1: managed-keys-zone: starting load
18-May-2026 01:37:43.132 general: debug 1: zone_startload: managed-keys-zone: enter
18-May-2026 01:37:43.132 zoneload: debug 1: managed-keys-zone: loading from master file /etc/contrail/dns/managed-keys.bind failed: file not found
18-May-2026 01:37:43.132 general: debug 1: managed-keys-zone: creating SOA
18-May-2026 01:37:43.133 zoneload: debug 1: managed-keys-zone: loaded; checking validity
18-May-2026 01:37:43.133 zoneload: info: managed-keys-zone: loaded serial 0
18-May-2026 01:37:43.133 general: debug 1: loop exclusive mode: ending
18-May-2026 01:37:43.133 zoneload: debug 1: zone authors.bind/CH: starting load
18-May-2026 01:37:43.133 zoneload: debug 1: zone authors.bind/CH: loaded; checking validity
18-May-2026 01:37:43.133 general: debug 1: dns_zone_verifydb: zone authors.bind/CH: enter
18-May-2026 01:37:43.133 general: debug 1: zone__settimer: zone authors.bind/CH: enter
18-May-2026 01:37:43.133 general: debug 1: zone_maintenance: zone authors.bind/CH: enter
18-May-2026 01:37:43.133 general: debug 1: zone__settimer: zone authors.bind/CH: enter
18-May-2026 01:37:43.133 zoneload: debug 1: zone version.bind/CH: starting load
18-May-2026 01:37:43.133 zoneload: debug 1: zone version.bind/CH: loaded; checking validity
18-May-2026 01:37:43.133 general: debug 1: dns_zone_verifydb: zone version.bind/CH: enter
18-May-2026 01:37:43.133 general: debug 1: zone__settimer: zone version.bind/CH: enter
18-May-2026 01:37:43.133 general: debug 1: zone_maintenance: zone version.bind/CH: enter
18-May-2026 01:37:43.133 general: debug 1: zone__settimer: zone version.bind/CH: enter
18-May-2026 01:37:43.133 general: debug 1: loop exclusive mode: ended
18-May-2026 01:37:43.133 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 01:37:43.133 zoneload: debug 1: zone hostname.bind/CH: starting load
18-May-2026 01:37:43.133 zoneload: debug 1: zone hostname.bind/CH: loaded; checking validity
18-May-2026 01:37:43.133 general: debug 1: dns_zone_verifydb: zone hostname.bind/CH: enter
18-May-2026 01:37:43.133 zoneload: debug 1: zone id.server/CH: starting load
18-May-2026 01:37:43.133 zoneload: debug 1: zone id.server/CH: loaded; checking validity
18-May-2026 01:37:43.133 general: debug 1: dns_zone_verifydb: zone id.server/CH: enter
18-May-2026 01:37:43.133 general: notice: all zones loaded
18-May-2026 01:37:43.133 general: debug 1: managed-keys-zone: synchronizing trusted keys
18-May-2026 01:37:43.133 general: debug 1: create_keydata: managed-keys-zone: enter
18-May-2026 01:37:43.133 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
18-May-2026 01:37:43.133 general: debug 1: managed-keys-zone: next key refresh: 18-May-2026 01:37:43.133
18-May-2026 01:37:43.133 general: debug 1: zone_journal: managed-keys-zone: enter
18-May-2026 01:37:43.133 general: debug 1: journal file /etc/contrail/dns/managed-keys.bind.jnl does not exist, creating it
18-May-2026 01:37:43.255 general: debug 1: zone_needdump: managed-keys-zone: enter
18-May-2026 01:37:43.255 general: debug 1: zone__settimer: zone version.bind/CH: enter
18-May-2026 01:37:43.257 general: debug 1: zone__settimer: zone authors.bind/CH: enter
18-May-2026 01:37:43.257 general: notice: FIPS mode is disabled
18-May-2026 01:37:43.257 general: notice: running
18-May-2026 01:37:43.257 general: debug 1: debug: t1-cloud-fixed version
18-May-2026 01:37:43.257 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
18-May-2026 01:37:43.257 general: debug 1: zone__settimer: zone id.server/CH: enter
18-May-2026 01:37:43.257 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 01:37:43.257 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 01:37:43.257 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 01:37:43.257 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
18-May-2026 01:37:43.257 general: debug 1: zone__settimer: zone id.server/CH: enter
18-May-2026 01:37:43.257 general: debug 1: zone_maintenance: managed-keys-zone: enter
18-May-2026 01:37:43.257 general: debug 1: zone_refreshkeys: managed-keys-zone: enter
18-May-2026 01:37:43.257 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
18-May-2026 01:37:43.257 general: debug 1: managed-keys-zone: next key refresh: 18-May-2026 01:37:43.257
18-May-2026 01:37:43.257 general: debug 1: zone_maintenance: zone hostname.bind/CH: enter
18-May-2026 01:37:43.257 general: debug 1: zone_maintenance: zone id.server/CH: enter
18-May-2026 01:37:43.257 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 01:37:43.257 resolver: debug 1: fetch: ./DNSKEY
18-May-2026 01:37:43.257 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 01:37:43.257 general: debug 1: zone__settimer: zone hostname.bind/CH: enter
18-May-2026 01:37:43.257 general: debug 1: zone__settimer: zone id.server/CH: enter
18-May-2026 01:37:43.257 resolver: debug 1: fetch: ./NS
18-May-2026 01:37:43.257 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2801:1b8:10::b#53
18-May-2026 01:37:43.258 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:9f::42#53
18-May-2026 01:37:43.258 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:9f::42#53
18-May-2026 01:37:43.258 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:a8::e#53
18-May-2026 01:37:43.258 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:a8::e#53
18-May-2026 01:37:43.258 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:1::53#53
18-May-2026 01:37:43.258 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:1::53#53
18-May-2026 01:37:43.258 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fe::53#53
18-May-2026 01:37:43.258 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fe::53#53
18-May-2026 01:37:43.258 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
18-May-2026 01:37:43.258 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:12::d0d#53
18-May-2026 01:37:43.258 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
18-May-2026 01:37:43.258 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:ba3e::2:30#53
18-May-2026 01:37:43.259 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2f::f#53
18-May-2026 01:37:43.259 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2f::f#53
18-May-2026 01:37:43.259 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:dc3::35#53
18-May-2026 01:37:43.259 lame-servers: info: network unreachable resolving './NS/IN': 2001:dc3::35#53
18-May-2026 01:37:43.259 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2::c#53
18-May-2026 01:37:43.259 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2::c#53
18-May-2026 01:37:43.259 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53
18-May-2026 01:37:43.259 lame-servers: info: network unreachable resolving './NS/IN': 2001:500:2d::d#53
18-May-2026 01:37:43.259 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:7fd::1#53
18-May-2026 01:37:43.259 lame-servers: info: network unreachable resolving './NS/IN': 2001:7fd::1#53
18-May-2026 01:37:43.259 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:c27::2:30#53
18-May-2026 01:37:43.259 lame-servers: info: network unreachable resolving './NS/IN': 2001:503:c27::2:30#53
18-May-2026 01:37:43.261 lame-servers: info: network unreachable resolving './NS/IN': 2801:1b8:10::b#53
18-May-2026 01:37:43.263 database: debug 1: delete_node(): 0x15be4d0 . (bucket 2)
18-May-2026 01:37:43.263 resolver: debug 1: fetch: ./DNSKEY
18-May-2026 01:37:43.263 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:503:ba3e::2:30#53
18-May-2026 01:37:43.263 lame-servers: info: network unreachable resolving './DNSKEY/IN': 2001:500:12::d0d#53
18-May-2026 01:37:43.275 database: debug 1: delete_node(): 0x178fe40 . (bucket 0)
18-May-2026 01:37:43.279 resolver: debug 1: resolver priming query complete: success
18-May-2026 01:37:43.307 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.
18-May-2026 01:37:43.307 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
18-May-2026 01:37:43.307 general: debug 1: managed-keys-zone: next key refresh: 19-May-2026 01:37:43.307
18-May-2026 01:37:43.307 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.
18-May-2026 01:37:43.308 general: debug 1: set_refreshkeytimer: managed-keys-zone: enter
18-May-2026 01:37:43.308 general: debug 1: managed-keys-zone: next key refresh: 19-May-2026 01:37:43.307
18-May-2026 01:37:43.308 general: debug 1: zone_journal: managed-keys-zone: enter
18-May-2026 01:37:43.321 general: debug 1: zone_needdump: managed-keys-zone: enter
18-May-2026 01:37:43.329 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 01:37:43.329 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 01:37:43.329 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 01:38:09.288 general: debug 1: zone_maintenance: managed-keys-zone: enter
18-May-2026 01:38:09.288 general: debug 1: zone_dump: managed-keys-zone: enter
18-May-2026 01:38:09.292 general: debug 1: zone__settimer: managed-keys-zone: enter
18-May-2026 01:38:09.300 general: debug 1: dump_done: managed-keys-zone: enter
18-May-2026 01:38:09.300 general: debug 1: zone_journal_compact: managed-keys-zone: target journal size 0
18-May-2026 01:38:27.215 network: info: listening on IPv6 interface tapeth0-05011c, fe80::5c77:18ff:fe1c:b9c4%11#53
18-May-2026 01:38:27.252 network: info: listening on IPv6 interface tapeth0-e5dc9c, fe80::c4ef:79ff:fe3a:2fec%13#53
18-May-2026 01:39:53.655 network: info: listening on IPv4 interface kube-ipvs0, 10.98.3.69#53
18-May-2026 01:40:00.719 network: info: listening on IPv6 interface tapeth0-9fb708, fe80::64c3:49ff:fe3d:1655%15#53
18-May-2026 01:40:00.730 network: info: listening on IPv6 interface tapeth0-7a2eb5, fe80::5c88:7fff:fe0a:e642%17#53
18-May-2026 01:40:04.302 network: info: listening on IPv6 interface vethafcee832-4, fe80::30e5:50ff:fe6a:bdb1%18#53
18-May-2026 01:40:09.998 network: info: listening on IPv6 interface tapeth0-b791ee, fe80::b4a4:eeff:fea9:a43f%20#53
18-May-2026 01:40:52.852 network: info: no longer listening on fe80::b4a4:eeff:fea9:a43f%20#53
18-May-2026 01:40:59.437 network: info: no longer listening on fe80::30e5:50ff:fe6a:bdb1%18#53
18-May-2026 01:41:00.422 network: info: no longer listening on fe80::5c88:7fff:fe0a:e642%17#53
18-May-2026 01:41:05.331 network: info: no longer listening on fe80::64c3:49ff:fe3d:1655%15#53
18-May-2026 01:41:25.519 network: info: listening on IPv6 interface tapeth0-bda6ed, fe80::d86e:47ff:feb7:d54c%22#53
18-May-2026 01:41:25.523 network: info: listening on IPv6 interface tapeth0-294c33, fe80::b4aa:66ff:fe62:5b1c%24#53
18-May-2026 01:41:25.523 network: info: listening on IPv6 interface tapeth0-e291e9, fe80::c808:44ff:fedf:9bab%26#53
18-May-2026 01:41:30.639 network: info: listening on IPv6 interface tapeth0-695757, fe80::c0f3:f0ff:feb9:64d9%28#53
18-May-2026 01:41:30.650 network: info: listening on IPv6 interface tapeth0-a978e2, fe80::5879:31ff:fe83:55ea%30#53
18-May-2026 01:41:30.651 network: info: listening on IPv6 interface tapeth0-6ee027, fe80::1433:8eff:fec6:379b%32#53
18-May-2026 01:41:35.566 network: info: listening on IPv6 interface tapeth0-fa7657, fe80::2cdd:47ff:fe23:a42d%34#53
18-May-2026 01:41:35.567 network: info: listening on IPv6 interface tapeth0-03d3bd, fe80::2825:f6ff:fec9:622e%36#53
18-May-2026 01:41:44.960 network: info: listening on IPv4 interface kube-ipvs0, 10.105.12.121#53
18-May-2026 01:44:55.014 network: info: no longer listening on fe80::b4aa:66ff:fe62:5b1c%24#53
18-May-2026 01:44:55.075 network: info: no longer listening on fe80::d86e:47ff:feb7:d54c%22#53
18-May-2026 01:44:55.081 network: info: no longer listening on fe80::c808:44ff:fedf:9bab%26#53
18-May-2026 01:44:55.081 network: info: no longer listening on fe80::5879:31ff:fe83:55ea%30#53
18-May-2026 01:45:25.432 network: info: no longer listening on fe80::c0f3:f0ff:feb9:64d9%28#53
18-May-2026 01:45:25.448 network: info: no longer listening on fe80::2825:f6ff:fec9:622e%36#53
18-May-2026 01:45:25.481 network: info: no longer listening on fe80::2cdd:47ff:fe23:a42d%34#53
18-May-2026 01:45:25.502 network: info: no longer listening on fe80::1433:8eff:fec6:379b%32#53
18-May-2026 01:45:41.120 network: info: no longer listening on 10.105.12.121#53