app domain does not appear to resolve to app server mixing up IPv4 and IPv6 #490

New Issue

2023-09-04T11:15:53Z

knoflook commented

2023-09-04 11:15:53 +00:00

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

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`

knoflook added the bug label 2023-09-04 11:15:53 +00:00

decentral1se added the abra label 2023-09-05 15:47:24 +00:00

decentral1se commented

2023-09-05 16:07:10 +00:00

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 for ostrom.collective.tools to make the comparison, right?

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 for `ostrom.collective.tools` to make the comparison, right?

3wordchant commented

2023-09-06 14:23:24 +00:00

➜ host ostrom.collective.tools
ostrom.collective.tools has address 88.198.81.228
ostrom.collective.tools has IPv6 address 2a01:4f8:222:f0a::2

So either would have worked, seems like the problem is that it did one kind of lookup on IPv4 and the other on IPv6.

``` ➜ host ostrom.collective.tools ostrom.collective.tools has address 88.198.81.228 ostrom.collective.tools has IPv6 address 2a01:4f8:222:f0a::2 ``` So either would have worked, seems like the problem is that it did one kind of lookup on IPv4 and the other on IPv6.

decentral1se referenced this issue from a commit

2023-10-04 01:25:26 +00:00

fix: ensure ipv4 is checked, not sometimes ipv6

decentral1se referenced this issue from toolshed/abra

2023-10-04 01:26:06 +00:00

fix: ensure ipv4 is checked, not sometimes ipv6 #364

decentral1se referenced this issue from a commit

2023-10-04 09:26:54 +00:00

fix: ensure ipv4 is checked, not sometimes ipv6

decentral1se commented

2023-10-04 09:29:06 +00:00

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.

Note, https://git.coopcloud.tech/coop-cloud/abra/pulls/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.

decentral1se referenced this issue from a commit

2023-10-04 09:29:12 +00:00

fix: ensure ipv4 is checked, not sometimes ipv6

decentral1se closed this issue

2023-10-04 09:29:18 +00:00

Sign in to join this conversation.

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/organising#490