app domain does not appear to resolve to app server mixing up IPv4 and IPv6 #490
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#490
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Got this glorious error today. Both addresses are right, maybe there should be a way to run abra ipv4/ipv6 only?
FATA[0003] app domain collabora.ostrom.collective.tools (2a01:4f8:222:f0a::2) does not appear to resolve to app server ostrom.collective.tools (88.198.81.228)?
The workaround was to add the IPv4 address to
/etc/hosts
.:88.198.81.228 collabora.ostrom.collective.tools
Sadness 😬 I guess
abra
should just grok whether it's reading a ipv4/ipv6 record and match accordingly? In this case,abra
should have tried to look up the ipv6 record forostrom.collective.tools
to make the comparison, right?So either would have worked, seems like the problem is that it did one kind of lookup on IPv4 and the other on IPv6.
Note, coop-cloud/abra#364 fixes that we do only stick to ipv4 when possible. I couldn't quite reproduce the issue but I think this could help fix it. This is ofc sadness for the ipv6 hackers amongst us. I welcome a change set which adapts this function to support ipv6 in the case of ipv4 matching failing. I think it's just repeating the logic and then passing
"ip6"
into the resolver.