Archivio di tutti i clip:
(Notebook di Evernote).
Security Researchers Express Concerns Over Mozilla’s New DNS Resolution For Firefox
With their next patch
Mozilla will introduce two new features to their
Firefox browser they call “DNS over HTTPs” (DoH) and Trusted Recursive Resolver (TRR). Mozilla says this is an additional feature which enables security.
Researchers think otherwise. From a report:
So let’s get to the new Firefox feature called “Trusted Recursive Resolver” (TRR). When Mozilla turns this on by default, the DNS changes you configured in your network won’t have any effect anymore. At least for browsing with Firefox, because Mozilla has partnered up with Cloudflare, and will resolve the domain names from the application itself via a DNS server from Cloudflare based in the United States. Cloudflare will then be able to read everyone’s DNS requests. From our point of view, us being security geeks, advertising this feature with slogans like “increases security” is rather misleading because in many cases the opposite is the case. While it is true that with TRR you may not expose the websites you call to a random DNS server in an untrustworthy network you don’t know, it is not true that this increases security in general. It is true when you are somewhere in a network you don’t know, i. e. a public WiFi network, you could automatically use the DNS server configured by the network. This could cause a security issue, because that unknown DNS server might have been compromised. In the worst case it could lead you to a phishing site pretending to be the website of your bank: as soon as you enter your personal banking information, it will be sent straight to the attackers. But on the other hand Mozilla withholds that using their Trusted Recursive Resolver would cause a security issue in the first place for users who are indeed in a trustworthy network where they know their resolvers, or use the ISP’s default one. Because sharing data or information with any third party, which is Cloudflare in this case, is a security issue itself.
I run my own local recursorsive nameservers even on my portable devices. totally not interested in using anyone’s resolvers but my own. I hope they publish instructions on how to bypass the behavior.
Re: (Score:2, Informative)
Anonymous Coward writes: on Sunday August 05, 2018 @11:33PM (
Will this enable or disable the behavior?
blog.nightly.mozilla.o… [mozilla.org] wiki.mozilla.org/Trust… [mozilla.org]
0: Off by default1: Firefox chooses faster2: TRR default w/DNS fallback3: TRR only mode5: Disabled
I imagine the setting we’re all looking for is: user_pref(“network.trr.mode”, 5);
Re: (Score:2, Interesting)
UK spook team would say ‘This is bad’How will we block British Users from using our censored lists or logging persons of interest who reference very bad extreme religious sites?China: Eeek – our firewall will need fixing again. We just block and force it to fallback – no probs.
Me: I use a VPN and it will get over this, only I dont trust my AV software from pokingits beak in – such as dangerous sites.
The winners will lbe PirateBay and banned chat apps in oppressed countries – and cloudflare, Microsoft, Bing
It depends on how it’s implemented, and what the selected DNS provider do. But it seems like putting all eggs in one basket and someyhing that may slow down the internet experience as well.
It’s actually very easy for the UK “spook team” as you call it, or British government in general: you just modify the law if necessary to include DNS proxy services, and then prosecute Cloudflare. The latter then has the choice between continuing to operate in the UK, accepting it has to filter DNS results, or taking its ball home.
The latter is not an option for CF, so they’d cave.
In some ways this might be the worst solution Mozilla could come up with as far as ensuring DNS integrity goes. They’re cen
So when I’m using an internal nameserver that resolves local servers with their local IP address, this thing will force resolve the external address from an external DNS and break local access, won’t it? (split brained DNS)
Anonymous Coward writes: on Sunday August 05, 2018 @09:10PM (
Sorry I’ll have to pass how Firefox these days. They are making to many decisions that really should be mine not there’s. This should be a opt in if it happens at all. A lot of us use chosen DNS servers thank you very much Mozilla but no thanks.
> They are making to many decisions that really should be mine not there’s. A lot of us use chosen DNS servers
Like you, I would turn it off. I also recognize that 99.9% of users don’t know what DNS is. So that goes to the question of “they [Firefox] are making too many decisions that should be mine, not theirs”. I would say the *defaults* should be selected based on what is best for the 99% of users who can’t and won’t make a choice. Settings should be available for the 0.1% who will use them.
That said, I’m not convinced that this particular choice is best for the 99% who don’t know what we’re talking about. That’s an entirely separate question.
It doesn’t have to be black and white. Take an approach similar to Microsoft’s where they show a screen on first use with all the defaults set but the ability to select your own, clueless users get to click next and keep what Mozilla thinks is best while knowledgeable users can make whatever choice that they see fit as they are being informed.
That just trains users to blindly click “use recommended settings” all the time. Within about a week of Microsoft rolling that screen out you started seeing malware requesting permissions from the user with “use recommended settings” or “accept (recommended)”. Worst of all, having gone with the recommendation the next pop-up from Windows asking them to confirm if they are really really sure also becomes a blind click-through.
Besides which, I don’t see any value in such a screen when the settings menu is two clicks away and power users are going in there anyway.
This would be a neat feature for the.1% as well, if you could explicitly define what service back-end provides the TRR. Then it is just a redundant failsafe DNS alternative that you can still control.
The issue is not that there is an alternative resolver that can work even when DNS is down; the issue is that it makes a decision for you that you don’t like– specifically, the choice of who is providing the resolution services. If they give you that control too, then this “issue” disappears completely.
> What about the remaining 0.9% of people?
Those are the ones still using Internet Explorer. Probably also using AOL’s DNS servers, to find Geocities.
I suppose you prefer to do yoru forwarding requests to your ISP DNS who sells your browsing information instead hu?
FYI cloudflare’s business model is to help business customers secure their connections. You can read it here [184.108.40.206] which is a plus for grandma. But if you’re technical like most of us then I am sure you can disable it.
Law enforcement has to monitor the bad guys. He could be part of that effort.
Sorry I’ll have to pass how Firefox these days. They are making to many decisions that really should be mine not there’s.
It’s a shame you’re reaching such a radical decision with no clear indication of how you’ll achieve this desired end. The other popular browsers (Edge, Safari, Chrome, or Opera) are proprietary (nonfree software, user-subjugating software). So without more information it seems like you’re likely going to choose a browser that will, ironically, give you considerably less control over your browser and you’ll end up making a choice to have fewer “decisions that really should be mine not [theirs]”. You’re overreacting in response to something that is literally a preference change away (as far as we know now). Encrypted DNS lookups could be a very good thing, but pushing users into using a particular DNS server is bad and choosing an organization with a track record for going back on their promises (as Cloudflare is famous for doing [torrentfreak.com]) makes this decision worse.
But regardless of the change or how easy it is to switch the behavior back to using only your preferred DNS server and never informing an unwanted third-party about your browsing, the saving grace of Firefox remains the same: Firefox is licensed such that one can make a free derivative browser (as others have done). We’re all allowed to inspect the code, make changes, run the now-trusted version, and help others by distributing a derivative browser. You can’t legally do any of that with other popular browsers.
We make free software better by improving it and using the improved versions, not abandoning free software when it becomes inconvenient or undesirable. The privacy you obviously, and rightly, want to keep depends on software freedom.
Chromium is free software. Or do proprietary Google Chrome and free Chromium differ specifically in a way relevant to this article? That is, do they differ in how they send DNS requests?
At least Firefox says openly what they’re doing. Edge and Chrome close-software do not, but who knows what happens under the hood.
90% people who don’t even know what DNS is, and who wouldn’t be able to select this security feature in the first place (since they don’t understand it) do welcome the feature, unknowingly.
Problem is Firefox is eager to give Cloudfare *all* the DNS traffic, and Chrome is also talking about doing the same, but to 220.127.116.11 (Google’s).
So… now what?
I can’t imagine this will fly with European users. No way the storage of dns requests by a private company on US soil is going to be GDPR compliant.
Have you ever actually tried to help Mozilla / Firefox? Have you ever filed a bug report or commented on one?
Every time I have, Mozilla’s goons either:
1 – Report it as a dupe of a related issue that was closed (closed as fixed, closed as won’t fix / feature request, or closed as being a dupe of yet some other one).
2 – Close it as fixed without fixing it. Often, the issues marked as fixed are not actually fixed, or were fixed but have reappeared (what you’re trying to report before getting marked as a dupe, see above).
3 – Close it as won’t fix / feature request and lock the comments (see above). These are often issues where people are complaining that FF’s latest change or injection of some bullshit no one wants has broken basic functionality and the mods on their bug tracker just stick their fingers in their ears and scream “LALALALALALALALA I CAN’T HEAR YOU” before locking the comments and marking everything as dupes that ultimately trace back to some completely unrelated issue.
4 – Report it as a dupe of a completely unrelated issue and chastise you for not using the broken and unwieldy search to find issues unrelated to what you’re trying to report.
… need this feature a lot.
And since the Firefox developer team has a big subset of that demographic, is quite clear why this was included.
All the rest of us, who carefully configured our DNS resolvers (or set up our own DNS servers), get screwed by default. Please tell me how to turn this off in Firefox for Mac/Android…
All the hipster developers using wifi in starbucks and other hipster coffee shops should be thanking Mozilla right now. All the rest of us, not so much.
PS: How does this work when one needs to go to a captive web portal in order to authenticate on the Wifi?
I dropped them years ago for their willingness to fuck with standard network behavior. If I put an address in, I want my browser to ask my OS to resolve it. Period. I don’t want to search for the thing if it’s not found. I don’t want someone’s re-implemented name service protocol. I certainly don’t want some half-assed application written by some half-assed application developer to try to re-invent how networking works, along with all the ways we already figured out that networking could be attacked for the last four decades.
Not that shocking behavior. WHen you use a VPN (you do right?) the
default config (of course you changed that) is to have DNS res done by the VPN server, not your computer.
Then use the search bar not the URL bar.
Again, bad idea, this only helps the browser and will add a common well known attack vector, it will not help any installed applications or services making internet calls.
Keep it separate, if you want to avoid resolving DNS over your network connection get a service/application that will curate your hosts file or act as a local personal DNS server/service itself. This way more than just your browser gets the benefits.
keep it separate
If you’re grandma or a hipster yes this is a good thing and it offers better performance too. Cloudflare is a company that offers protection from DDOS attacks, CDN, as well as networking security. Cloudflare’s DNS guarantees privacy as well [18.104.22.168].
If you are the slashdotter nerd then you will go into about:config and turn it off so what is the big deal.
Reghardless of whether Cloudflare is God or the devil, it is NOT what I want. Not what I have configured, and if I get it, then it causes me a lot of support calls from users who don’t get what they paid for, It is like having Systemd bypass your settings for DNS resolve – a source of very difficult to diagnose harassment for support workers, with no warning
This should not be done without a popup saying “Do you want me to fuck with your settings without asking?” then the person who codes it will understan
This is of course complete bullshit.
As if anyone with something better to do than snoop on the wire at Starbucks won’t see destination IP, SNI or servers public key identity and have access to the exact same data DNS provides.
What they really need is 802.1x.
Where do you get your DNS information for your resolvers? From your ISP? From Google? Why do you trust those people more than Cloudflare? Why do you think this ONLY works with Cloudflare?
The DNS over HTTPs allows you to connect to any server capable of DNS relay through HTTPs. That means you can setup your mobile browser to use YOUR OWN DNS RESOLVERS in your house and it cannot be intercepted (because it’s being encrypted) nor will those reading the traffic KNOW you are getting DNS over the HTTPS (because i
As I stated on my original post, I use Firefox ESR 60 on a mac. And Firefox on my android (KeyOne).
At home I use 22.214.171.124, 126.96.36.199 and 188.8.131.52 since I have better things to do than to set up my Synology to be my DNS server.
But when I travel, I use public wifi whenever I can get it, be that my hotel, the training centers were I teach, or, god forbid, a hipster coffee shop. And many of those need a captive portal to autenticate to the Wifi, and that depends on using the Network’s DNS servers. So, I configured an “Automatic” setting on the network locales of my mac to handle those cases.
So, as a user of Firefox, I am not happy with this. I am capable enough to configure my DNS settings (or, if push comes to shove, set up a DNS from scratch, not even touching my nas).
So thank you for the inconvenience mozilla. I hope you guys enjoy the backslash when hipsters start to realize that they can not connect to the net in their favourite hipster watering spot because they can not get to the captive portals…
At least, the guys who use Mozilla in corporate networks will get this assinine setting turned off in group policies… as for the rest of us, a quick google and a trip to about::settings shal suffice
You might consider switching to DNS Watch [dns.watch]. Instead of providing Google or Cloudflare all your DNS query data (they have fingers in plenty enough other places in my opinion), DNS Watch favors privacy, security, and anonymity.
Preffered DNS server: 184.108.40.206Alternate DNS server: 220.127.116.11
Why trust them? A lot of dead links on their website, GitHub, Facebook, their “network”, even their other website ideal-hosting.com isn’t resolving.
All I can find is that they are some IT/Media company from Munich, Germany.
Mozilla employee here, though not involved with this project.
The hipsters will be fine, as the most likely setting falls back to the system DNS when TRR fails. For a little more detail see: wiki.mozilla.org/Trust… [mozilla.org]
The hipsters will be fine, as the most likely setting falls back to the system DNS when TRR fails.
… which negates any purported security benefit from this “feature”. All a malicious access point wanting to send you to phishing sites would need to do would be to block TRR.
Mozilla employee here, though not involved with this project.
Will Mozilla be disclosing its financial relationship with cloudflare and provide a full accounting of funds it receives as a result of this insanity?
I hope you guys enjoy the backslash when hipsters start to realize that they can not connect to the net in their favourite hipster watering spot because they can not get to the captive portals…
I take it you don’t realise that Firefox detects captive portals and brings up a bar across the top asking you to sign in, and that since Firefox is in control of when and how it makes requests this functionality is not affected?
May I recommend another slashdot story, the one suggesting we need more people studying liberal arts because the concept of “critical thinking” seems to be lost.
This is what is currently on the 18.104.22.168 site (which I’m assuming that’s what Firefox is using since it’s owned by Cloudflare)
Privacy First: Guaranteed.We will never sell your data or use it to target ads. Period.
We will never log your IP address (the way other companies identify you). And we’re not just saying that. We’ve retained KPMG to audit our systems annually to ensure that we’re doing what we say.
Frankly, we don’t want to know what you do on the Internet—it’s none of our business—and we’ve taken the technical steps to ensure we can’t
Of course, like any other DNS Resolver, you have to trust what they’re saying is true, but vs. your ISP DNS (which most firefox users are using by default) or Google Public DNS, Cloudflare would be a privacy improvement. Not sure if it’s better than Quad9 security wise though.
The biggest issue I have is that the settings aren’t exposed by the settings menu and has to be configured using about:config. I would like to see better controls for it and possibly a list of supported DNS providers to choose like how I can choose Search engines.
But by law, your ISP is required to maintain a log of all Internet meta-data going back three years as part of the strategy against cybercrime. In turn these companies outsource this work to centralised providers.
Thre truth is in the middle, as usual.
once again, this is a bad idea!
browsers are not the only things using DNS, additionally, it is just one more attack vector on an already sizable surface area.
And if FF enforces this feature… they will only risk losing market share in the browser space every time their “vision” is used to attack systems.
I don’t understand why Mozilla thinks the browser has any business directing DNS to whoever they think it should go to. So, once this update happens, as a Firefox user, all my DNS-related browsing info goes to Cloudflare? At the moment, I’m just using my ISP’s default DNS. They already know where I’m browsing. Now, both my ISP and Cloudflare know where I’m browsing. How is this better? At the moment, we can disable it, of course, but no one but Slashdot denizens might do this.
It is not “better” for me, but this behaviour should have an interesting, unintended effect for Australian users of Firefox. Australian ISPs are, for the most part, subject to a series of court orders requiring them to serve fake IP addresses when asked for The Pirate Bay, Rarbg etc. That fake address leads a browser to a information/warning page. It is trivially circumvented for tech savvy users by not using the ISP DNS. It strikes me that this change will, at least in the short term, make Firefox au
For about 5 seconds, until Cloudfare configure their resolver to appear to be local to where the request originated (if they haven’t already done so).
This is just like the behaviour of Google’s 22.214.171.124 resolver.
Might take more than 5 seconds but it will happen given the small number of targets. The existing court orders would need to be extended to to cover non-parties to the original law suits, or new suits raised with handy precedent, and the Copyright Act might need to change to cover entities other than “carriage service providers” (which may not cover Cloudflare at the moment). Nothing that money cannot buy.
They’ll have to do that anyway, as CDNs sometimes use DNS to direct users to a content server local to the user.
Because they can tap the requests on the DNS resolvers and resell it. Verisign did something commercially similar by putting a wildcard at *.com instead of returning an “invalid address” response.
Coding for the sake of coding. The same reason Gnome is a mess along with systemd. One could also argue design by committee.
I don’t understand why Mozilla thinks the browser has any business directing DNS to whoever they think it should go to
I don’t understand how anyone (including Firefox’s design team) can think this is different from any other malware doing the same thing. Surely it is a criminal act?
Security issues aside this would result in some very strange behaviour on a misconfigured network:
– Different content being served to different applications.- An apparent network outage for one application is transparent to the other.
Because if it does, I think I can overall live with it.
only as long as the thing you looking for is not censored by cloudflare – and even then, only the most basic censorship.
… or Mozilla.
See my own comment further down the page.
What we really need anyway is Distributed DNS so it can’t be bogarted.
Yes, I know that’s not an easy thing to ask for. But sooner or later, it will be figured out.
In the meantime, Cloudflare’s guaranteed secure and private DNS servers are the best we have, other than OpenDNS.
Granted, it’s all based on a privacy guarantee in their Terms of Service, but it’s worded correctly and I trust that a lot more than I trust Google.
When cloudflare uses system to resolve names guess what… that process itself uses insecure protocol to query root resolvers up to whoever owns the zone so claiming that cloudflare is secure is rather comical. It’s actually no more secure than running your own server using default root list without a forwarder.
Why is it even relevant whether name resolution is secure? The underlying network isn’t secure. Anyone in the network path can fuck you. Heck there is a long history of those normally o
They should be allowed to do so, at the OS level.
The summary didn’t mention if this “feature” was possible to disable.
I DO NOT want every freaking app to use a different DNS to resolve my queries.
>”The summary didn’t mention if this “feature” was possible to disable.”
about:confignetwork.trr.mode = 5 to completely disable it
0 Off. To use operating system resolver.1 Race native against TRR. Do both in parallel and go with the one that returns a result first. Most likely the native one will win.2 First. Use TRR first, and only if the secure resolution fails use the operating system resolver.3 Only. Only use TRR. Never use the native (after the initial setup).4 Shadow. Runs the TRR resolves in parallel with the native for timing and measurements but uses only the native resolver results.5 Off by choice This is the same as 0 but marks it as done by choice and not done by default.
Hmmm. I haven’t looked at this… but it sounds like it’ll break any host names I’ve set up locally (for development) and not published to global DNS…
Please tell me that this will break internal DNS for non-existent top level domains. I’ve recently encountered several business partners who insisted on inventing their own internal top level domains, and simply accepting that there is no HTTPS signatory for those top level domains.
Good Job, Mozilla, in making an unexcusable privacy-raping tool..
Fuck off,Signed,The majority of reality, faggots.
And I’m gay, so I can call you faggots all day long without repercussion, dick-suckers.
Moderator alert: this account (Khyber) has been compromised!
This whole so-called “security issue” ignores the fact that Cloudflare already offers its own DNS resolvers, at 126.96.36.199 and 188.8.131.52.
AND — this is the big point — they guarantee that they keep no records and do not even log the traffic going through those servers.
Frankly, I trust that a whole lot more than any promise from Google.
And yes… as long as cloudflare continues the same policy, and live up to it, it is a heck of a lot more secure than going through some random DNS resolver you don’t eve
Eh I’ll just post this link here and you can draw your own conclusions.
Cloudflare will collect only the following information from Firefox users:âTimestampâIP Version (IPv4 vs IPv6)âResolver IP address + Port the Query Originated FromâProtocol (TCP, UDP, TLS or HTTPS)âQuery NameâQuery TypeâQuery ClassâQuery Rd bit setâQuery Do bit setâQuery Size Query EDNSâEDNS VersionâEDNS PayloadâEDNS NsidâResponse Type (normal, timeout, blocked)âResponse CodeâResponse SizeâResponse CountâResponse
They all answer to US authorities. I thought CLoudflare was European but I could be wrong. Your American service provider is no exception.
Whoops meant to post this here.
You can draw your own conclusions.
First off your ISP guarantees they sell your browser history to advertisers and some EVEN INSERT ads into your browsing experience. Cloudflare who is behind 184.108.40.206 guarantees your privacy as well as gives you the lowest latency if you read the agreement at www.1111.com. [220.127.116.11]
Cloudflare is used for companies that have been hacked for security as well as CDN services. Experia consulted with them after the scandal.
I already set my DNS servers to cloudflare (18.104.22.168) when they launched their service. Now I can use it over https so no one along the network path can snoop my dns queries. If there is a faster or more private dns service, I’d like to know about it so I can switch to it.
I’m also using cloudflare but only because the I.P. address for their primary DNS is the same as Pocky Day [wikipedia.org].
Cloudflare is an adversary and is doing its utmost to break the world wide web [notabug.org]. You can have no reasonable expectation of privacy from them, either [device5.co.uk]. Cloudflare is a MiTM attack on the web and should be treated as such. They have a track record of spreading disinformation and even messing with bug tickets of privacy projects like tor to try to make themselves look better without fixing anything.
Your ISP should not *have* your browser history. You should be using tor [eff.org]. If your ISP can see your browsing
zero visibility to internal DNS resolution for corporate networks
Ham handed is the kindest thing I can say about this.
Obviously you don’t work for a living. I’ve worked IT for over 30 years, for companies, very large and very small. Often IT does suck, especially when ideas are done thoughtlessly, just as this knee jerk initiative from Mozilla is.
IT doesn’t control my firefox. I install it myself. IT provides me DHCP specified DNS resolver that understands our internal network. They provide the certificate I can install.
This path ultimately leads to firefox resolution acting *differently* than chrome and neither resolving like the rest of the system.
The browser projects need to not internalize name resolution and instead work toward whatever they need out of the OS resolver.
And if this is disabled by default why is everybody so pissed off ?
This is from “we know better than you” Mozilla. I bet it’s enabled by default.
it is off by default.
wiki.mozilla.org/Trust… [mozilla.org] “TRR is preffed OFF by default and you need to set a URI for an available DOH server to be able to use it.”” Set `network.trr.mode` to 2 to make DNS Over HTTPS the browser’s first choice but use regular DNS as a fallback (0 is “off by default”, 1 lets Firefox pick whichever is faster, 3 for TRR only mode, 5 to explicitly turn it off).”
I am sorry, AGAIN, what is the problem ? People are simply throwing mud and getting angry because they want to.
DNS is one of the few remaining services yet to be totally centralized. Assertions centralized systems (Mozilla) are more trustworthy and privacy preserving than federated ones is doublespeak.
Mozilla is basically asserting without evidence everyone’s DNS servers are untrustworthy and therefore for users own good only theirs can be trusted.
It is not even clear what even practical theoretical benefit to the end user would be given anyone in data path can see destination address, SNI, PKI Identity and TLS ses
In security world, changing DNS servers being used without notifying the owner of the machine is known as “hijacking DNS”.
How on earth is Mozilla getting away with hijacking DNS?
Because sharing data or information with any third party, which is Cloudflare in this case, is a security issue itself.
Exposing data to a particular party is an issue iff the security model treats that data as confidential and not intended for that party. In the current model of things, DNS queries are sent in the clear and so there is no confidentiality with respect to any party that happens to be eavesdropping.
So then thinking for a bit, we could have some transport layer security for DNS, this would prov
Block cross-site scripting by default. (uMatrix)
Block tracking cookies. (Privacy Badger)
Block advertising. (uBlock Origin)
Feature thrash does not solve security problems. If you can’t get updates that are separate from new features, you can’t trust them to reduce the attack surface.
Stop updating?? Risky! Block JS?? a lot of sites won’t work. Privacy Badger and uBlock Origin are indeed nice recommendations.
This gives a blank page which is not truly a blank page. The blank page shows some icons for frequently visited pages. That’s why I also use an add-on to get a real blank tab.
Ah! Hark the days of Netscape Navigator 2.0, and the little Lizard Throbber on the corner!(can you install the old lizard throbber back? Firefox 61/Linux here.)
You do realize getting around DNS filtering is trivial, right?
Yep so the answer is to use your ISP who tells you in the agreement they will sell your information and history to advertisers instead
A lot of websites now are going HTTPS with Google banning HTTP already in canary releases in Chrome. This will make it harder with transport layer security. FOr example your ISP will know you went to Amazon but not much else.
However, true pornhub will still be a record if they track each ISP unless you do a proxy with a securre connection.
Their own site explicitly says otherwise.
Cloudflare will collect only the following information from Firefox users:âTimestampâIP Version (IPv4 vs IPv6)âResolver IP address + Port the Query Originated FromâProtocol (TCP, UDP, TLS or HTTPS)âQuery NameâQuery TypeâQuery ClassâQuery Rd bit setâQuery Do bit setâQuery Size Query EDNSâEDNS VersionâEDNS PayloadâEDNS NsidâResponse Type (normal, timeout, blocked)âResponse CodeâResponse Siz
I use Cloudflare’s 22.214.171.124 DNS server because it saves me up to 8 digits on each look request!
Dude, DO NOT write their name as “Mozi//a”, that’s SJW and/or hipster crap. Mozi//a reads as “Mozi slash slash A”. They’re called Mozilla, in all letters.
It gives us extra overhead. Maybe Mozilla thinks the Web is not slow enough with all the current crap, maybe they want to make it even slower.
I trust you will let me know about upcoming changes that require a user response.
Oh, sure thing guy. This is, after all, the official way to send us queries and since you’ve clearly gave us a way to contact you, you’ll be hearing an official reply soon.
Get more comments of loaded
“When the only tool you have is a hammer, you tend to treat everything as if it were a nail.” — Abraham Maslow