Oxidized/Ruby prefers IPv4 address over IPv6 address resolved from DNS

[ewysong]

I'm running Oxidized on Ubuntu 22.04 with dual stack IPv4/IPv6, and trying to back up the configuration of some devices that are not reachable from this server via IPv4, only IPv6. There are A and AAAA records for the device.

The problem I'm running into is that Oxidized (Ruby?) is using A record instead of the AAAA record to chose the IP address to try and connect to for the backup. I can see this in packet captures and from the Oxidized web it lists the IPv4 address as well. AAAA records should be preferred and tried first from my understanding. If I remove the A record from DNS, Oxidized works just fine as it uses the AAAA record and successfully connects.

I'd like to leave the A records in DNS and not have to add /etc/hosts entries on the server for every device.

oxidized-web v.0.14.0
oxidized v.0.30.1
ruby 3.3.4-p94

Thanks for any assistance!

[robertcheramy]

A better way would be to have oxidized try all available IP address until it gets a connection.

[github-actions]

This issue is stale because it has been open 90 days with no activity.

[dunc623b]

Same issue here.