Protocol oddity

[Bill]

I've no idea if this is new or has always been this way, but if I do a basic (IPv4) ping to idnet.com it works perfectly, but with an IPv6 one (ping6) I get "nodename nor servname provided, or not known", suggesting no IPv6 record on the DNS server?

But browsing to idnet.com shows the connection as being being over IPv6...

Main DNS is Cloudflare (1.1.1.1) with Google (8.8.8.8) as backup.

Doesn't happen on other sites I've tried and it's not causing any issue that I can see, it just seems odd.

[nowster]

I had a dig (sic.) and:

idnet.com has no IPv6 address

but HTTP connections to it redirect to

www.idnet.com which does.

The redirect is mildly misconfigured:

Code Select Expand

* Host idnet.com:80 was resolved.
* IPv6: (none)
* IPv4: 212.69.36.50
*   Trying 212.69.36.50:80...
* Established connection to idnet.com (212.69.36.50 port 80) from 192.168.x.x port 38136
* using HTTP/1.x
> GET / HTTP/1.1
> Host: idnet.com
> User-Agent: curl/8.21.0-rc2
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 301 Moved Permanently
< Server: nginx/1.14.1
< Date: Thu, 18 Jun 2026 10:04:32 GMT
< Content-Type: text/html
< Content-Length: 185
< Connection: keep-alive
< Location: https://www.idnet.com//
<



[Bill]

I should have thought of that, I've come across it (not identical, but similar) on other sites... although I wouldn't know how to check the way you did, I had to ask on those too

Thanks 👍