👻 spooky ipv6-only networking 👻 (@noIPv6)

yea good point 🤦🏻 i was testing the java client & java server i got ipv6-only server working (w/ nat64/dns64) - needed to add “-Djava.net.preferIPv6Addresses=true” to the command line (duh, i knew this but it’s been way too long)

Nitter
@tschaefer I remember deploying tweaked resolvers that remove any A record…
@cr @tschaefer I go one step further and add AAAA forcefully on CDN domains that don't have it.

@miyuru @cr

I use DNS64 and filter a records.

Using unofficial AAAA records of CDN doesn't work for me.(like the reddit problem or similar, I would need to maintain a list )

@tschaefer No need a list, I wrote a DNS proxy that does it automatically.

https://gitlab.com/miyurusankalpa/IPv6-dns-server

Miyuru / IPv6-dns-server · GitLab

Adds AAAA records to DNS where CDN support IPv6.

GitLab
@miyuru
you maintain a complete proxy 😉
I know also a way of hetzner users. (not cdn)
Some of them "forgot" the aaaa-record. But as long they are on a shared host, the ptr of the ipv4 leads to a working ipv6 address.

@miyuru

It is crazy.
It works also for the new Desinfec't 2023 by @ct_Magazin

hosted here cdncf.heise.de (cloudfront)

Why don't YOU add the AAAA-records, Dear @ct_Magazin ?

#ipv6now #ipv6

@miyuru
Maybe I should chain my resolvers. Adding your cdn AAAA-records, then DNS64 and then removing A-records.

#IPv6 #noipv4

@miyuru
I see, you included dns64 (configurable) and other features, so probably I don't need the chain.
@miyuru
Your test domain www.amazon.com has already IPv6, maybe you change the readme - or I misunderstood the test purpose.
@tschaefer yes, need to remove it, amazon did not have IPv6 when I added it.