4 ms·

Your isp dns converts the AAAA record to AA record with the ipv4 of it's own (only router) configured dualstack machine, that machine does cgnat46 and visits th

Your isp dns converts the AAAA record to AA record with the ipv4 of it's own (only router) configured dualstack machine, that machine does cgnat46 and visits the ipv6 only server. If software has hardcoded ipv6 addresses, this is much harder to solve, but I don't think this is really an issue, because hardcoded ipv6 addresses appear very seldom.

Dylan16807 2y ago
Assuming you mean nat46, your description is a bit off. The NAT box doesn't have a single ipv4, it needs a big pile of ipv4 addresses to dynamically allocate whenever a new AAAA record comes through. But that means it has to intercept all DNS requests and doesn't work with anything it didn't intercept, which seems far from ideal.
- aboardRat4 2y ago
  >it needs a big pile of ipv4 addresses to dynamically allocate whenever a new AAAA record comes through. But those don't have to be globally routable. >it needs a big pile of ipv4 addresses to dynamically allocate whenever a new AAAA record comes through. This wasn't really a problem until doh/dot became a thing. But even nowadays doh and dot are provided by whom? By google and cloudflare who are tls-mitm'ing half of the internet anyway. Moreover most ISPs intercept dns to display those "please enter your phone number to verify your identity" screens anyway. >far from ideal. No more imperfect than NAT. Idealism is what is killing ipv6.
  - Dylan16807 2y ago
    If I'm going to run single stack locally I'm going to use IPv6 and a stateless converter for IPv4.
    - aboardRat4 2y ago
      Which means that servers have zero incentive to convert to ipv6. All this cgnat46 setup is not in the name of end users, because they will always adapt somehow, as reels have a huge force of attraction. It is to make sure that service providers can deploy ipv6-only _servers_ and not bother that 60 percent of their target audience will be unavailable. The issue with the ipv6 internet is not the end users, they are paying, so the ISPs will always adapt to their needs, or the users themselves will buy new equipment in the worst case, it's the service providers who stop being profitable by going ipv6-only.
      - Dylan16807 2y ago
        Your idea also gives servers no incentive to convert, and if they do convert they become less reliable for anyone on IPv4.
Ekaros 2y ago
That process seems extremely error prone on anything but most basic protocols... And given how many people here for example don't run their ISPs DNS... Just seems massively complex and very resource intensive process.
- aboardRat4 2y ago
  >That process seems extremely error prone on anything but most basic protocols... Worse is better. Moreover, we really mostly need to make it work on http, that's enough to say "you can watch YouTube", but also deficient enough to stimulate ipv6 transition. >given how many people here for example don't run their ISPs DNS.. Those people usually know how to deal with ipv6. >Just seems massively complex and very resource intensive process. No more complex than hanging in limbo for 30 years .
throw0101c 2y ago
> Your isp dns converts the AAAA record to AA record with the ipv4 of it's own (only router) configured dualstack machine, that machine does cgnat46 and visits the ipv6 only server. You mean like: * https://en.wikipedia.org/wiki/IPv6_transition_mechanism#464XLAT https://en.wikipedia.org/wiki/IPv6_transition_mechanism#464X... * https://en.wikipedia.org/wiki/4over6 https://en.wikipedia.org/wiki/4over6
- aboardRat4 2y ago
  Not, it's the other way round. If an isp already has full ipv6 deployment, accommodating for ipv4 is easy. The biggest issue is, surprisingly, not ISPs, but service providers.

Dylan16807 2y ago

Assuming you mean nat46, your description is a bit off. The NAT box doesn't have a single ipv4, it needs a big pile of ipv4 addresses to dynamically allocate whenever a new AAAA record comes through. But that means it has to intercept all DNS requests and doesn't work with anything it didn't intercept, which seems far from ideal.

aboardRat4 2y ago
>it needs a big pile of ipv4 addresses to dynamically allocate whenever a new AAAA record comes through. But those don't have to be globally routable. >it needs a big pile of ipv4 addresses to dynamically allocate whenever a new AAAA record comes through. This wasn't really a problem until doh/dot became a thing. But even nowadays doh and dot are provided by whom? By google and cloudflare who are tls-mitm'ing half of the internet anyway. Moreover most ISPs intercept dns to display those "please enter your phone number to verify your identity" screens anyway. >far from ideal. No more imperfect than NAT. Idealism is what is killing ipv6.
- Dylan16807 2y ago
  If I'm going to run single stack locally I'm going to use IPv6 and a stateless converter for IPv4.
  - aboardRat4 2y ago
    Which means that servers have zero incentive to convert to ipv6. All this cgnat46 setup is not in the name of end users, because they will always adapt somehow, as reels have a huge force of attraction. It is to make sure that service providers can deploy ipv6-only _servers_ and not bother that 60 percent of their target audience will be unavailable. The issue with the ipv6 internet is not the end users, they are paying, so the ISPs will always adapt to their needs, or the users themselves will buy new equipment in the worst case, it's the service providers who stop being profitable by going ipv6-only.
    - Dylan16807 2y ago
      Your idea also gives servers no incentive to convert, and if they do convert they become less reliable for anyone on IPv4.

Ekaros 2y ago

That process seems extremely error prone on anything but most basic protocols... And given how many people here for example don't run their ISPs DNS... Just seems massively complex and very resource intensive process.

aboardRat4 2y ago
>That process seems extremely error prone on anything but most basic protocols... Worse is better. Moreover, we really mostly need to make it work on http, that's enough to say "you can watch YouTube", but also deficient enough to stimulate ipv6 transition. >given how many people here for example don't run their ISPs DNS.. Those people usually know how to deal with ipv6. >Just seems massively complex and very resource intensive process. No more complex than hanging in limbo for 30 years .

throw0101c 2y ago

> Your isp dns converts the AAAA record to AA record with the ipv4 of it's own (only router) configured dualstack machine, that machine does cgnat46 and visits the ipv6 only server. You mean like: * https://en.wikipedia.org/wiki/IPv6_transition_mechanism#464XLAT https://en.wikipedia.org/wiki/IPv6_transition_mechanism#464X... * https://en.wikipedia.org/wiki/4over6 https://en.wikipedia.org/wiki/4over6

aboardRat4 2y ago
Not, it's the other way round. If an isp already has full ipv6 deployment, accommodating for ipv4 is easy. The biggest issue is, surprisingly, not ISPs, but service providers.