-
Notifications
You must be signed in to change notification settings - Fork 75
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
CNAME answers to A request #161
Comments
This seems to work
|
Nice! Is there a publicly available record we can use to test? If so, mind making a PR? |
Well I guess we'd have to update this https://github.com/saghul/pycares/blob/master/tests/tests.py#L186 but I'm not exactly sure how we are supposed to build the response for each case? |
Right. Up until this point I've used publicly available records instead of synthetic ones. |
I'm not sure how we should go about generating the synthetic one, perhaps creating a fake server ? |
Not sure, I suppose it might be tricky to test on Windows, that's why I relied on existing DNS records, though this is not ideal. |
For my use case, I'd like to get the actual record I request. Would this change "help" by returning the A record of the CNAME automatically? |
I think that it is possible for a server to answer an A request with a CNAME response, but it seems that pycares, although in both cases using the c-ares
ares_parse_a_reply
method, forces the result of an A query to be a list of IPspycares/src/pycares/__init__.py
Line 168 in 4e6e36f
The text was updated successfully, but these errors were encountered: