-
Notifications
You must be signed in to change notification settings - Fork 302
Open
Description
I have an odd issue. Everything works great and the logs are clean for days, except when trying to resolve the SRV-record "_https._tcp.repo.librewolf.net". Same problem for both DoT, DoQ and DoH3. Any idea what's wrong or is it a bug?!
Jun 17 06:35:36 admin: 2025/06/17 06:35:36.573880 ERROR exchange failed prefix=dnsproxy upstream=tls://xxxxxx.dns.nextdns.io:853 question=";_https._tcp.repo.librewolf.net.\tIN\t SRV" duration=6.006420068s err="reading response from tls://DK-ANX-DoT-xxxxxx.dns.nextdns.io:853: read tcp xx.xx.xx.xx:56274->188.172.192.71:853: i/o timeout"
Jun 17 06:47:04 admin: 2025/06/17 06:47:04.606209 ERROR exchange failed prefix=dnsproxy upstream=quic://SE-ANX-DoQ-xxxxxx.dns.nextdns.io:853 question=";_https._tcp.repo.librewolf.net.\tIN\t SRV" duration=6.032274547s err="reading response from quic://SE-ANX-DoQ-xxxxxx.dns.nextdns.io:853: deadline exceeded"
Jun 17 06:47:31 admin: 2025/06/17 06:47:31.658463 ERROR exchange failed prefix=dnsproxy upstream=https://doh3.dns.nextdns.io:443/xxxxxx/DK-ZEP-DoH question=";_https._tcp.repo.librewolf.net.\tIN\t SRV" duration=9.006318843s err="requesting https://doh3.dns.nextdns.io:443/xxxxxx/DK-ZEP-DoH: Get_0rtt \"https://doh3.dns.nextdns.io:443/xxxxxx/DK-ZEP-DoH?dns=<xxxxx>": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Metadata
Metadata
Assignees
Labels
No labels