Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Rohkem teavet

Teema arhiveeriti. Please ask a new question if you need help.

using DoH, how can i do a traceroute from the browser?

myPalabok
myPalabok
more options

FF 67.0.4

i have enabled DoH, i'm inside company network withour own DNS servers (it resolves to root hints for Internet sites).

how can i tell, when i browse, that FF is now using DoH servers instead of our DNS servers?

FF 67.0.4 i have enabled DoH, i'm inside company network withour own DNS servers (it resolves to root hints for Internet sites). how can i tell, when i browse, that FF is now using DoH servers instead of our DNS servers?

All Replies (3)

philipp
philipp
  • Moderator
more options

hello, when you enter "about:networking#dns" into the address bar of firefox, the TRR pane should say true for all hostnames resolved through doh...

Hasan
Hasan
more options

Hi,

I have enabled the DoH feature in my browser with default Cloudflare provider. I am using our company DNS server so far. we don't have any DoH policy for Firefox. But still i found that it is not working. I have tried "about:networking#dns" and found all the values set to false in TRR.

Can someone tell me, why it is not enabled?

Regards Hasan

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Hi Hasan, there are several reasons Firefox might not use DoH in an enterprise environment, such as an explicit policy set by IT or finding a "dns canary" configured when checking regular DNS.

But Firefox might also check for implicit indications. The latest blog post says in the upcoming U.S. rollout, "...our plan is to: ... Respect enterprise configuration and disable DoH unless explicitly enabled by enterprise configuration." I haven't researched exactly what that entails -- a single group policy setting the home page could trigger it? -- or whether it might already be affecting Firefox 69.