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

explicitly resolve A/AAAA when pulling external IP from icanhazip #2132

Merged
merged 1 commit into from
Sep 19, 2024

Conversation

evgeni
Copy link
Member

@evgeni evgeni commented Sep 19, 2024

ipv4.icanhazip.com has an AAAA record, and ipv6 has an A record, which
leads to both facts returning v6 addresses.

while this is a missconfiguration on the side of icanhazip.com, we can
prevent it from happening by forcing things at the resolver level.

ipv4.icanhazip.com has an AAAA record, and ipv6 has an A record, which
leads to both facts returning v6 addresses.

while this is a missconfiguration on the side of icanhazip.com, we can
prevent it from happening by forcing things at the resolver level.
Copy link
Member

@ekohl ekohl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ipv4.icanhazip.com has an AAAA record

That sounds like it's against the entire point of the service

@evgeni
Copy link
Member Author

evgeni commented Sep 19, 2024

ipv4.icanhazip.com has an AAAA record

That sounds like it's against the entire point of the service

Yepp. It's a miss-config on the Cloudflare side. I've poked @major (he used to run this service) as I don't know who to poke at CF (who runs the service now).

@evgeni evgeni merged commit 9b9ec51 into master Sep 19, 2024
2 checks passed
@evgeni evgeni deleted the force-v4 branch September 19, 2024 08:47
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.

2 participants