Proposed Changes

When starting an application (with all exceptions on) rabbitmq always gives a couple of exceptions because it first tries to connect to IPv6 (and fails) but then succeeds to connect to IPv4. RabbitMQ is using exceptions as normal control flow. This is annoying. It makes the user wonder what he did wrong, and has to wressle through the startup of his program clicking away all the exceptions. Usually one will disable the recurring exceptions at the risk of missing it when it's relevant.

As asked in https://groups.google.com/g/rabbitmq-users/c/sHeiZMBwfWU
Also see https://stackoverflow.com/a/86395708/1560347 .

Types of Changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

• Bug fix (non-breaking change which fixes issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause an observable behavior change in existing systems)
• Documentation improvements (corrections, new content, etc)
• Cosmetic change (whitespace, formatting, etc)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask on the
mailing list. We're here to help! This is simply a reminder of what we are
going to look for before merging your code.

• I have read the CONTRIBUTING.md document
• I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
• All tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in related repositories

Further Comments

This pull request probably need some work. This is more of a proof of concept, please let me know what you think.

It's probably a big no-no to change the api, however it's impossible to pass an endpoint without doing the DNS resolution internally.