Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Learn More

DNS setting issue with particular website

  • 4 odpovede
  • 0 má tento problém
  • 105 zobrazení
  • Posledná odpoveď od lifespan

more options

As described in this thread (https://support.mozilla.org/en-US/questions/1431159#answer-1618832), I had a problem accessing one particular domain after doing everything I could find to fix it. Setting DNS to Increased Protection fixed it. It's partly just curiosity but also concern that I'm asking if there is an issue that should be addressed.

The basic scenario: could not access one particular domain only in FF on one computer. No problems with FF on other devices and no problem with other browsers on the computer in question. Configuring DNS settings to Increased Protection is the only thing that allowed me to access that site (which happens to be the org I work for). So the setting is only necessary on this device and only for that domain.

What's the explanation or solution for ensuring I don't have other DNS issues, or something else, that will be a problem later?

As described in this thread (https://support.mozilla.org/en-US/questions/1431159#answer-1618832), I had a problem accessing one particular domain after doing everything I could find to fix it. Setting DNS to ''Increased Protection'' fixed it. It's partly just curiosity but also concern that I'm asking if there is an issue that should be addressed. The basic scenario: could not access one particular domain only in FF on one computer. No problems with FF on other devices and no problem with other browsers on the computer in question. Configuring DNS settings to Increased Protection is the only thing that allowed me to access that site (which happens to be the org I work for). So the setting is only necessary on this device and only for that domain. What's the explanation or solution for ensuring I don't have other DNS issues, or something else, that will be a problem later?

Vybrané riešenie

Removing specific DNS addresses in the OS that had been added to solve some previous problem (I do not recall what it was) fixed the problem. We'll see if the previous issue arises again. Thanks.

Čítať túto odpoveď v kontexte 👍 0

Všetky odpovede (4)

more options

This can possibly be caused by a problem with your DNS service. Does this fail as well if you use the 'Off' setting and if you use the DNS lookup tool from the about:debugging page in case of 'off'? You can open "about:" pages via the location/address bar.

Increased and Max Protection use Cloudflare as the provider. Maybe try a different DNS service in the OS.

more options

Thanks. Yes, it fails if the DNS setting is off. I don't know what you mean by "Does this fail as well if you use the 'Off' setting and if you use the DNS lookup tool from the about:debugging page in case of 'off'?" How do I use the lookup tool there?

I do not understand your suggestion about a different DNS service because with the increased protection setting, the current one works, and as best I can tell, there is no way to select one with default protection.

I've tried everything suggested in the link you provided.

more options

With the Default Protection setting, Firefox decides what to use for DNS lookup and if it fails with the 'Off' setting then this means that the DNS service that is set in the OS can't resolve this host. Like I wro9te above, Increased and Max Protection do not use the OS set DNS service and thus work where the OS DNS service fails. You need the check the DNS settings in the OS and possibly set another service.

Cloudflare:

IPv4: 1.1.1.1 | 1.0.0.1
IPv6: 2606:4700:4700::1111 | 2606:4700:4700::1001

Google:

IPv4: 8.8.8.8 - 8.8.4.4
IPv6: 2001:4860:4860::8888 - 2001:4860:4860::8844
more options

Vybrané riešenie

Removing specific DNS addresses in the OS that had been added to solve some previous problem (I do not recall what it was) fixed the problem. We'll see if the previous issue arises again. Thanks.