Log messages should be changed/adjusted for "Timeout - no response from upstream DNS server"

Feature Requests
1

"Inspired" by Timeout - no response from (which?) upstream DNS server - #5 by rdwebdesign I request that this unspecific and very undetailed message should be changed/adjusted so that is clear if a single one DNS upstream server (and which one) or all of them are not responding.

Example of this message:

2025-02-20 12:42:33.694 CET [67/T103] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-02-20 12:42:35.710 CET [67/T103] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-02-20 12:42:37.726 CET [67/T103] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-02-20 12:42:39.742 CET [67/T103] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-02-20 12:42:41.758 CET [67/T103] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-02-20 12:42:43.774 CET [67/T103] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-02-21 06:36:38.756 CET [79/T122] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-02-21 06:36:40.772 CET [79/T122] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-02-21 06:36:42.789 CET [79/T122] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-02-21 06:36:44.996 CET [79/T122] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
3

Is the solution to this just phrasing it as a plural?
"Timeout - no response from upstream DNS server(s)"

When FTL.log notes these errors such as:

2025-04-19 22:30:51.080 ERROR Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
2025-04-19 22:30:51.080 INFO Tried to resolve PTR "254.1.168.192.in-addr.arpa" on 127.0.0.1#53 (UDP)

The servers that the request is sent to are listed in pihole.log:

2025-04-19 22:30:51.845 query[PTR] 254.1.168.192.in-addr.arpa from 192.168.1.130
2025-04-19 22:30:51.850 forwarded 252.1.168.192.in-addr.arpa to 192.168.1.254
2025-04-19 22:30:51.850 forwarded 254.1.168.192.in-addr.arpa to 192.168.1.253

It only displays the error message if none of the servers respond.

It there are no errors, then nothing is noted in FTL.log, and pihole.log lists the requests that were sent and notes which did respond, eg:

2025-04-19 22:36:07.040 query[PTR] 9.1.168.192.in-addr.arpa from 127.0.0.1
2025-04-19 22:36:07.040 forwarded 9.1.168.192.in-addr.arpa to 192.168.1.254
2025-04-19 22:36:07.040 forwarded 9.1.168.192.in-addr.arpa to 192.168.1.253
2025-04-19 22:36:07.040 forwarded 9.1.168.192.in-addr.arpa to 192.168.1.252
2025-04-19 22:36:07.040 forwarded 9.1.168.192.in-addr.arpa to 192.168.1.251
2025-04-19 22:36:07.040 forwarded 9.1.168.192.in-addr.arpa to 192.168.1.1
2025-04-19 22:36:07.044 reply 192.168.1.9 is testbox.internal