Φόρουμ κοινότητας «Firefox»

I am using 140 ESR version on linux with Cloudflare's DNS over HTTPS and with DOH active for some reason resolving a domain like d3oklwo3y1bx83.cloudfront.net will resolve to local host IP 127.0.0.1.

I am using firefox about:networking#dnslookuptool to test resolution of the domain d3oklwo3y1bx83.cloudfront.net Both with DOH on and off the resolution remains local host. I tried another browser on the same workstation and I was able to receive a resolution of 13.225.193.203 13.225.193.133 13.225.193.64 13.225.193.58 Why is firefox ESR not able to resolve that domain? What are causes ?

Is is firefox dnslookuptool results.

On a dual-stack network, with Windows tcpip6 ‘disabledcomponents’ parameter set to prefer IPv6, Firefox ignores this setting whenever an endpoint resolves both an IPv4 and a NAT64 address.

While monitoring traffic captured while connecting to sites in Firefox, if the initial DNS request for the site comes back with an IPv6 address only, the connection attempts from client’s IPv6 address to destination IPv6. If DNS answers come back with IPv4 and IPv6, the connection attempts IPv6 to IPv6. If DNS answers come back with IPv4 and a NAT64 address, Firefox doesn’t even attempt to connect to the NAT64 address, it immediately defaults to IPv4. I’ve tried disabling the IPv4 fallback setting which doesn’t change the behavior.

We’re running version 140.8.0esr. Is this behavior intended for Firefox? Is there a way to configure Firefox so it doesn’t ignore NAT64 addresses in dual-stack environments? The only way I found to force this was to completely disable the IPv4 stack on the client system’s NIC.

As of recent I increasingly have issues with accessing websites, those websites previously (yesterday) worked fine on Firefox. Version is 148.0 on Mac 26.3 (Apple M3 Silicon).

Now it has completely stopped working. Only websites using direct IP-address still work, all others fail with "Hmm. We’re having trouble finding that site.". Safari still opens the websites flawlessly.

Nothing has changed on the OS level or application level as no updates have been installed (no need, as everything is up to date). Antivirus is BitDefender with extension for Firefox enabled for already an extended time (year or so).

I tried disabling several dns.resolver settings as mentioned in https://support.mozilla.org/en-US/kb/firefox-cant-load-websites-other-browsers-can. No improvement whatsoever.

I quit firefox, removed the cache manually and restarted while starting a new test profile, so completely blank. Issue is still there.

DNS Servers on OS-level are correct.

Version 148 was installed last night evening and as such could be the reason for the failure since it is basically the only thing that changed.