NfNitLoop ("Cody Casterline ๐ณ๏ธโ๐") wrote:
In fact, that is what Firefox's DNS lookup algorithm seems to do. My network dump caught it doing lookups for dns.google (to bootstrap its DNS-over-HTTP) and it used a separate source port for requesting A, AAAA, HTTPS, etc.
This feels like a big footgun to anyone who's stuck behind consumer NAT. I wonder -- did they consider using separate ports instead of adding the unnecessary serialization? Or did that not fix the test case that prompted the initial workaround? ๐ค






