Description of problem:

How reproducible:

Always

Is this issue a regression from an earlier version:

No

Steps to Reproduce:

1. Sync RHEL repositories, publish CV, Create AK on Satellite with IPv4

2. Navigate to Hosts -> Register Hosts, select AK and generate command

3. Run the registered command on IPv6 host

# set -o pipefail && curl -sS --insecure 'https://satellite-ipv4.redhat.com/register?activation_keys=test_ak_el9&location_id=2&operatingsystem_id=1&organization_id=1&update_packages=false' -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjo0LCJpYXQiOjE3MjU0NDY0NDksImp0aSI6ImQ2OWZmNjA0Yjg0ZTlmNDU5NWZkYTM2ZGI1NmE0ZGFhNWIzZTQ1M2NiM2EwMWNhNjg4ODZlZWViMmYzNDJiZmUiLCJleHAiOjE3MjU0NjA4NDksInNjb3BlIjoicmVnaXN0cmF0aW9uI2dsb2JhbCByZWdpc3RyYXRpb24jaG9zdCJ9.fy0bJRIjgsMOQRDh5nLBA8yBmX9oeKghA8YRtIuIV3g' | bash
curl: (6) Could not resolve host: satellite-ipv4.redhat.com 

# ping <satellite-ipv4>
ping: connect: Network is unreachable 

Actual behavior:
IPv6 host can't reach to the Satellite with FQDN or IP causing  "curl: (6) Could not resolve host: satellite-ipv4.redhat.com" 

Expected behavior:
IPv6 host can be reached to IPv4 satellite directly or with a proxy, and host is registered successfully

Business Impact / Additional info:

Workaround:

1. Use `-x http://infra-ipv64-proxy.redhat.com:3128` in the generated curl command and in the global registration template
2. subscription-manager config --server.proxy_hostname={proxy_hostname} --server.proxy_port={proxy_port}