BTW, this statement not right
"because ping is by default resolving the PTR for the FQDN you are supplying"
To ping a FQDN, say www.domain.tld
you have to query for the A record, or AAAA - can not ping it if you don't have the IP.
In your example you gave a FQDN to ping, so why would it report IP vs the name you pinged.. If you want just the IP for that FQDN your pinging then use the -n option as already stated.
Incomplete maybe, the ping will resolve the A and/or AAAA record for the name supplied as an argument, but it will then resolve the PTR for the IP address it gets and output that in the ping results.
PING cconn.info(ipv6.hautevitesse.net) 56 data bytes
64 bytes from ipv6.hautevitesse.net: icmp_seq=0 ttl=62 time=4.01 ms
64 bytes from ipv6.hautevitesse.net: icmp_seq=1 ttl=62 time=3.27 ms
64 bytes from ipv6.hautevitesse.net: icmp_seq=2 ttl=62 time=3.72 ms
--- cconn.info ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 3.275/3.672/4.015/0.304 ms, pipe 2
cconn.info is the FQDN I supply, the IP resolves to 2605:2a00:ffff:fffe::10 but the PTR to 2605:2a00:ffff:fffe::10 is ipv6.hautevitesse.net. So ipv6.hautevitesse.net is what is shown in the ping results....