-
-
Notifications
You must be signed in to change notification settings - Fork 431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
13.2 issue with CNAME queries #1116
Comments
Thanks for the feedback. I have identified the issue that is causing the failure cache record to get added and will get that fixed in the next update. However, it usually does not matter and the domain should resolve without issues. But, it seems like you have Advanced Forwarding app installed which uses the EDNS Client Subnet feature in Cache to store data for various network groups defined in the app. Which is why its showing So are you using the Advanced Forwarding app or are you using a root conditional forwarder zone? |
Definitely not using the advanced forwarding app. In fact, I've never even installed it previously. The 2 apps I use are: DNS rebinding protection and the Query logging app. I'm using a root conditional forwarding zone. For me, the domains in question don't actually resolve without issue other than on the first query. Subsequent queries return a SERVFAIL, so on my end at least, it breaks quite a few things, including the Technitium app store. |
Thanks for the details. Do you have EDNS Client Subnet option enabled in Settings? That too can cause this issue with resolution with the current state of the cache. |
I don't have it enabled, no. The best I can do is to repeat the set of tests again, although I'm sure that I had neither the app installed nor the edns client subnet option enabled. It might take me a day or two to come back on this, since I backed out the version to a prior one, so I'd need to upgrade again to rerun the tests |
Right, so I had 30 minutes to spare so upgraded again and did some more tests. Confirmed that no forwarding app is installed, that I am using a root conditional forwarding zone and that DNSSEC is switched off everywhere, both on the main settings page and on the definition for each of the FWD records in the conditional forwarding zone. The eDnsClientSubnet is only returned when querying the controld server and not 1.1.1.1 and appears in the actual response from p0.freedns.controld.com, so it doesn't seem to be technitium adding it Cache records resulting from both queries:
Using the DNS Client to inspect the responses from both servers over tls yields the following
|
Thanks for the details. Yes, the controld server is returning EDNS Client Subnet when not asked and its getting cached. Will update the cache code to detect this case. |
Just upgraded one of my servers to 13.2 and immediately had some funky things happening. There appears to be an issue with resolving CNAME records when using multiple concurrent forwarders.
In particular, with two conditional forwarders defined in the root zone, 1.1.1.1 and p0.freedns.controld.com, both using tls or a combination of tls and quic, a DnsSpecialCacheRecordData with a SERVFAIL gets added to the valid record, resulting in the initial query working and subsequent queries failing as the SERVFAIL is served from cache.
Disabling one of the forwarders makes the problem go away. I tested this out on multiple CNAMEs and the result is the same.
This does not occur on versions prior to 13.2
Both forwarders using tls
One forwarder using tls and the other quic
Each of the two forwarders disabled in turn
The text was updated successfully, but these errors were encountered: