-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: implement DNS over QUIC #18
base: main
Are you sure you want to change the base?
Conversation
Hi @bassosimone! I made changes as per RFC 9250. Could you test once? One more change is pending. The edns-tcp-keepalive option (section 5.5.2). This option should not be set. If we receive this option as an argument in NewQuery function we need to handle it. |
Nice, it seems the code is now working as intended with |
More specifically, I think there are two criteria we should meet for merging an MVP of DNS over QUIC:
I will allocate some time to study the RFC and review the code over the weekend! Thank you for working on DoQ, @roopeshsn! 🙏 ✨ |
I tried to resolve the following domain,
I got the following error,
I'll look into this. |
Thanks to you! |
From response.go file, I came to know that if a domain is not valid, then we'll get an error with a suffix "no such host". This is expected, correct? But in this case, roopeshsn.com is valid. So dns0.eu is not able to resolve this domain correct? |
Let me try and run the same command you were running with other protocols. So, I tried using DNS-over-TLS first:
It's curious I get an Then I tried using DNS-over-UDP:
This result seems to suggest
(See how the answer is
So,
However, Anyway, back onto the DoQ topic, I think the DoQ code is working as intended, since it shows
However, I am still a bit confused by the following:
I would have expected |
Implemented DNS over QUIC.
Part of rbmk-project/issues#3