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
[RFC] API design for IPv6 and more types of records #43
Comments
I think you're raising a very relevant issue here 👍 Currently, the How can we configure the Other than the default I'm curious what others think about this, what other projects offer similar APIs? 👍 |
I'd also be interested in how to determine IPv6 support / route-ability for amphp/socket#35. For the second issue I'd recommend to have separate I'd probably remove either |
We now have support for the most relevant resource record types (RRs) such as The current It is my understanding that we should add a new method which supports passing an explicit record type (such as For the reference: Node.js uses dedicated method names (such as Once the Once this is supported in our Socket component, we may want to add some configuration options to disable either protocol type (there's no reliable way to detect IPv6 support) and also deprecate the then unused |
Currently this package only supports A and CNAME records in it's implementation and after a quick chat with @clue earlier today we decided we need to come up with a good way support IPv6 and more record types. Here is a quick hack up to get the discussion started:
The text was updated successfully, but these errors were encountered: