4 ms·

This goes the other direction too. I just this second fixed a problem with incredibly slow SSH connections because a host lookup which returned an IPv4 address

by XorNot 7mo ago

This goes the other direction too. I just this second fixed a problem with incredibly slow SSH connections because a host lookup which returned an IPv4 address instantly was waiting 10+ seconds for an IPv6 response which would never come. Now I'm sure I can fix DNSmasq to do something sensible here, but the defaults didn't even break - they worked in the most annoying way possible where had I just disabled IPv6 that would've fixed the entire problem right away. Dual stack has some incredibly stupid defaults.

iso1631 7mo ago
> Dual stack has some incredibly stupid defaults. Dual stack is the problem, and it's not going away in the next 20 years. Single stack ipv4, fine, if your applications support it then great. Single stack ipv6, fine, if your applications support it then great. Dual stack is just horrendous, you can never be sure what stack you're on when you work at a higher level.
Dagger2 7mo ago
If your DNS server isn't replying to requests, your DNS server is broken. That has nothing to do with v6.
- jampekka 7mo ago
  If the problem gets fixed by simply disabling v6, it has much to do with v6.
  - Dagger2 7mo ago
    It might get hidden by disabling v6, but not fixed. And if your DNS server fails to reply to an AAAA lookup over v4, that's 100% not a v6 problem.