Re:uBlock 1.48.0 Adds Readiness Status, Code Viewer, and Oth...
by 1vuio0pswjnm7 on Tuesday March 21, 2023 @10:47PM
(#35256157)
While I have always used local authoritative DNS to avoid remote DNS queries, long before adblockers existed, other parts of the steup have changed over time. Currently, I use
(a) HTTP/1.1 pipelining and DoH servers for bulk DNS data
(b) localhost-bound authoritative DNS server for redirecting all domain names to forward proxy IP address
(c) localhost-bound forward proxy that stores domain-to-IP address mappings in memory
NB. Without modification, this setup is probably not going to work well for people who like to use graphical web browsers for everything. For recreational web use I am not using a graphical browser that auto-fetches resources. I am using a text-only browser. Thus, I only need DNS data for the domain names in the URLs I visit, not for ones found in web pages pointing to fonts, CSS, images, Javascript, and so forth. This makes the DNS data retrieval process very straightforward: one domain name for each URL. In the times I have tested recreational browsing using a graphical browser, it can be surprising how many web pages are quite readable without using resources from other domains, but for folks that want to view myriad web pages that are comprised of resources from a variety of hosts requiring numerous domain name lookups, bulk DNS data retrieval will require more work. In any event, there are many, many possible variations of a setup like this and the one I use is suited for me; I am not fond of the large graphical browsers and I rely on the proxy for a number of tasks. Other variations might suit other users' personal preferences.
(a) HTTP/1.1 pipelining and DoH servers for bulk DNS data
(b) localhost-bound authoritative DNS server for redirecting all domain names to forward proxy IP address
(c) localhost-bound forward proxy that stores domain-to-IP address mappings in memory
NB. Without modification, this setup is probably not going to work well for people who like to use graphical web browsers for everything. For recreational web use I am not using a graphical browser that auto-fetches resources. I am using a text-only browser. Thus, I only need DNS data for the domain names in the URLs I visit, not for ones found in web pages pointing to fonts, CSS, images, Javascript, and so forth. This makes the DNS data retrieval process very straightforward: one domain name for each URL. In the times I have tested recreational browsing using a graphical browser, it can be surprising how many web pages are quite readable without using resources from other domains, but for folks that want to view myriad web pages that are comprised of resources from a variety of hosts requiring numerous domain name lookups, bulk DNS data retrieval will require more work. In any event, there are many, many possible variations of a setup like this and the one I use is suited for me; I am not fond of the large graphical browsers and I rely on the proxy for a number of tasks. Other variations might suit other users' personal preferences.
Hope that helps.