-
Notifications
You must be signed in to change notification settings - Fork 2
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
Nameserver receives query that it can resolve immediately from resolver #9
Comments
|
TCP specifications: https://tools.ietf.org/html/rfc5966 |
TO DO:
|
Hey, we don't have to do both TCP and UDP. |
For writing the code for this issue? Perhaps not. We could just support UDP for now. |
The RFC we've linked to here states that TCP is used for zone transfers and messages that exceed 512 bytes. It also states that supporting TCP is part of fully implementing the core DNS protocol. |
I would vote for doing both. None of the team have lots of experience with low level networking, and learning the difference between TCP and UDP and how that works is a good thing. |
When a nameserver receives a query that it has the information for in its cache, it can find that in the cache
The text was updated successfully, but these errors were encountered: