Skip to content
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

fix: Allow address family to be resolved from DNS #1607

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

richiejp
Copy link

It may not be possible to know before hand what address a host will
resolve to.

Possibly this fixes #1576

It may not be possible to know before hand what address a host will
resolve to.
@richiejp
Copy link
Author

@luin Ping

@luin
Copy link
Collaborator

luin commented Jan 30, 2023

Sorry for the delay! Should it be considered as a breaking change?

@richiejp
Copy link
Author

Yes. If someone has broken DNS then they will find out when this is changed.

@maxpain
Copy link

maxpain commented Mar 11, 2024

Any updates on this?

@Defman
Copy link

Defman commented Sep 21, 2024

I have sort of the inverse problem. In our dualstack setup we have aws vpc dns64, this works great with our nat... however our elasticache is placed in a legacy VPC without ipv6. However this should in its own not be a problem. But since the dns server returns both ipv4 and ipv6 addresses for the elasticache cluster dns... ioredis seems to get stuck in ClusterAllFailedError: Failed to refresh slots cache. I have tried setting ?family=4 however this does not seem to force ioredis to resolve the hostname to only ipv4. Any suggestions for workarounds, place a dns server in front of the default dns server and have it strip out the ipv6 addresses...

Note: ioredis does not seem to have this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unhandled error event: Error: getaddrinfo ENOTFOUND - AWS ElasticCache
4 participants