Skip navigation

Ignore AAAA records if IPv6 unicast routing isn't functional

score 5
You have not voted. New

This is a global request for all of AOS, but there isn't a place for such feature requests. It does affect the 1500 series switches (as well as lots of other things).

 

We have many devices in IPv4-only environments, either with IPv6 routing disabled or not available, where the device has no IPv6 global unicast address.

 

When using a hostname on the CLI to connect to a dual-stack remote device, the unit will retrieve the IPv6 AAAA hostname and the connection will fail.

 

This feature request is for AOS to avoid resolving AAAA records if IPv6 unicast routing is not functional, and to use IPv4 A records only.

 

Example from a Netvanta 1531 running AOS 12.3.2:

 

sw0.gta#sh ipv6 route

Codes: C - connected, S - static, O - OSPF, B - BGP

       E1 - OSPF external type 1, E2 - OSPF external type 2

       I - OSPF inter area, N - Named Prefix, D - DHCPv6 PD

 

Gateway of last resort is not set

 

sw0.gta#ping google.com

Type CTRL+C to abort.                                 

Legend: '!' = Success, '?' = Unknown host, '$' = Invalid host address

        '*' = Request timed out, '-' = Destination host unreachable

        'x' = TTL expired in transit, 'e' = Unknown error

        'B' = Packet too big

Sending 5, 100-byte ICMP Echos to 2607:F8B0:4007:801::200E, timeout is 2 seconds:

*****

Success rate is 0 percent (0/5)

sw0.gta#

Comments

Vote history