-
Notifications
You must be signed in to change notification settings - Fork 58
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
Dns #219
Dns #219
Conversation
* aws_dns_service_provider_config - Controls what host/port/protocol combos the default aws_dns_resolver uses to | ||
* resolve queries. | ||
* | ||
* aws_host_resolution_service - A heavy-weight host name resolution service that contains CRT-specific and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not just call this aws_dns_caching_resolver or something?
or aws_dns_cache
* | ||
* Shoulds: | ||
* (1) Cache authority/zones-of-responsibility in a label-based tree (iterative only?) | ||
* (2) Assume query input is a host name and not an IP address. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would this break existing systems that rely on querying an ip address just returning that ip address?
enum aws_dns_resource_record_type type; | ||
|
||
/* time-to-live in seconds */ | ||
uint32_t ttl; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we store time fetched or something so we can evaluate the TTL?
First draft of a proposed public interface for DNS and host resolution that includes full resolver implementations and separation of concerns between resolvers and CRT-desired functionality.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.