Here's a wild guess, considering you didn't provide much information (including the Host OS distribution):
Your system has probably this default sysctl setting:
# sysctl net.ipv6.conf.all.accept_ra
net.ipv6.conf.all.accept_ra = 1
Here's the description:
accept_ra - INTEGER
Accept Router Advertisements; autoconfigure using them.
It also determines ...
No UFW cannot do that, you must terminate and re-transmit (like with an nginx proxy or stunnel), you cannot use port mapping as you must rewrite the packet with IPv4/IPv6.
Example - Use Cloudflare - https://community.cloudflare.com/t/proxy-ipv4-visitors-to-ipv6-only-backend/115186
Okay, apparently the answer is no, not all people have IPv6, some people still have only IPv4 and cannot access a service that is IPv6 only.
One can only hope that will change soon, but I assume it may still take years until all people have IPv6.
The address on the interface is 2a01:4f9:c010:5335::1/64, not 2a01:4f9:c010:5335::/64. You incorrectly configured the DNS for the network, but not the host.
Per your comment, changing DNS to the host fixed the problem.
After more digging I found out my setup could be refined a bit, though I am not entirely convinced that I have covered all my bases.
Anyway ip -6 rule show could be tweaked a bit.
32000: from 2001:470:7875::/48 lookup openvpn
Was generated by the following command:
ip -6 rule add priority 32000 from 2001:470:7875::/48 table openvpn
You can tell these are in use when ss output shows sockets with mapped addresses.
IPv4 connections can be handled with the v6 API by using the
v4-mapped-on-v6 address type; thus a program needs to support only
this API type to support both protocols. This is handled
transparently by the address handling functions in the C library.
People require an IPV6 address or something like a proxy to allow them to see an IPv6 site. IPv4 and IPV6 are different stacks, so it will be the case that users of IPv4 only stacks will not be able to reach your IPv6 only site.
With respect of an alternative to an http/https proxy server at another host, its possible a VPN provider can provide you with an ...
Let's draft a more comprehensive explanation if the problem should affect also other people. The OP is connecting to the web through a SOCKS5 proxy established with:
ssh -D <local_port>
Unfortunately there is a Firefox bug, which doesn't allow IPv6-only hosts to connect to an IPv4 address using the proxy. They must enable DNS proxying too.
In the ...
As a same Internet connection test, this is flawed.
Comparing v4 addresses assumes the user agent to be behind the NAT you are expecting. This reduces flexibility when their public address space is restructured.
Carrier grade NAT means a v4 address can be shared by who knows how many customers.
Multihoming is relatively easy. The same IP can have paths ...
The only way to do this is:
Send the form to v4.example.com, which only has A record for the web server you are submitting the form to.
In the web server, setup a virtual host with v4.example.com domain name, or add v4.example.com as an additional domain to the existing virtual host.
Then there can be cross-domain issues you need to take care of.
Configure the interface to use stable addressing. EUI-64, rfc7217 stable opaque, or static addressing. Bring the interface up and get its global scope address.
Anything in fe80::/10 is link local. Not routable, only use those on the same LAN.
By the way, on Linux, use the ip command. Not ifconfig, which has been unmaintained for many years. However, some ...
If you get a 500 Internal Server Error you need to check your server's error log for details of the error. The 500 status is simply a catch-all response returned to the client because of some specific server error.
There are a number issues here that result in errors...
Require not ip 2a01:598:
Require not ip 2a01:598:::
In both these cases, the ...