On Wed, 5 Jan 2022 19:42:33 +0100
wrote:
> On Wed, Jan 05, 2022 at 12:41:23PM -0500, Celejar wrote:
>
> [...]
>
> > The configuration I'm talking about is as follows: the browser makes
> > ordinary, unencrypted DNS requests to the Pi-hole, over a trusted
> > network
>
> If the browser decides
On Wed, Jan 05, 2022 at 12:41:23PM -0500, Celejar wrote:
[...]
> The configuration I'm talking about is as follows: the browser makes
> ordinary, unencrypted DNS requests to the Pi-hole, over a trusted
> network
If the browser decides to make the DNS requests over HTTPS (DoH [1],
that's what we
On Wed, 5 Jan 2022 18:20:23 +0100
wrote:
> On Wed, Jan 05, 2022 at 08:43:23AM -0500, Celejar wrote:
> > On Wed, 5 Jan 2022 06:10:48 +0100
> > wrote:
> >
> > > On Tue, Jan 04, 2022 at 04:05:11PM -0500, Celejar wrote:
> > >
> > > [...]
> > >
> > > > One way "to combine DoH with resolving 14,000
On Wed, Jan 05, 2022 at 08:43:23AM -0500, Celejar wrote:
> On Wed, 5 Jan 2022 06:10:48 +0100
> wrote:
>
> > On Tue, Jan 04, 2022 at 04:05:11PM -0500, Celejar wrote:
> >
> > [...]
> >
> > > One way "to combine DoH with resolving 14,000 addresses to 127.0.0.1"
> > > is by using Pi-hole. Some peop
On Wed, 5 Jan 2022 06:10:48 +0100
wrote:
> On Tue, Jan 04, 2022 at 04:05:11PM -0500, Celejar wrote:
>
> [...]
>
> > One way "to combine DoH with resolving 14,000 addresses to 127.0.0.1"
> > is by using Pi-hole. Some people have *millions* of domains blacklisted
> > in Pi-hole:
>
> Pi-hole won'
to...@tuxteam.de wrote:
> On Tue, Jan 04, 2022 at 04:09:42PM -0500, Dan Ritter wrote:
>
> [...]
>
> > Here's what I do:
> >
> > My local DNS resolver offers DNS, DNS over TLS, and DNS over
> > HTTPS.
> >
> > I supply a use-application-dns.net zone that returns NXDOMAIN.
> > That tells browsers
On Tue, Jan 04, 2022 at 04:09:42PM -0500, Dan Ritter wrote:
[...]
> Here's what I do:
>
> My local DNS resolver offers DNS, DNS over TLS, and DNS over
> HTTPS.
>
> I supply a use-application-dns.net zone that returns NXDOMAIN.
> That tells browsers to not use DoH.
Oh, is it possible to tell th
On Tue, Jan 04, 2022 at 04:05:11PM -0500, Celejar wrote:
[...]
> One way "to combine DoH with resolving 14,000 addresses to 127.0.0.1"
> is by using Pi-hole. Some people have *millions* of domains blacklisted
> in Pi-hole:
Pi-hole won't help unles it also does HTTPS proxying (that means it
would
David Wright wrote:
> On Tue 04 Jan 2022 at 19:37:34 (+0100), to...@tuxteam.de wrote:
> > On Tue, Jan 04, 2022 at 01:19:37PM -0500, Michael Stone wrote:
> >
> > [...]
> >
> > > And this is why putting stuff into /etc/hosts is basically never the right
> > > answer. :)
> >
> > Eye, beholder and
On Tue, 4 Jan 2022 20:58:27 +0100
wrote:
> On Tue, Jan 04, 2022 at 01:33:18PM -0600, David Wright wrote:
> > On Tue 04 Jan 2022 at 19:37:34 (+0100), to...@tuxteam.de wrote:
> > > On Tue, Jan 04, 2022 at 01:19:37PM -0500, Michael Stone wrote:
> > >
> > > [...]
> > >
> > > > And this is why putti
On Tue, Jan 04, 2022 at 10:34:48AM -0800, James H. H. Lampert wrote:
On 1/4/22 10:19 AM, Michael Stone wrote:
And this is why putting stuff into /etc/hosts is basically never the
right answer. :)
Au contraire!
Among other things, the host table is the best possible place to block
access to c
On Tue, Jan 04, 2022 at 01:33:18PM -0600, David Wright wrote:
> On Tue 04 Jan 2022 at 19:37:34 (+0100), to...@tuxteam.de wrote:
> > On Tue, Jan 04, 2022 at 01:19:37PM -0500, Michael Stone wrote:
> >
> > [...]
> >
> > > And this is why putting stuff into /etc/hosts is basically never the right
> >
On 1/4/22 11:33 AM, David Wright wrote:
In fact, I was quite shocked when I just tried
DNS over HTTPS for a couple of minutes. The 10-day weather
profile that I screenshoot every day was plastered in popups.
Anyone know how to combine DoH with resolving 14,000 addresses
to 127.0.0.1? Also, does
On Tue 04 Jan 2022 at 19:37:34 (+0100), to...@tuxteam.de wrote:
> On Tue, Jan 04, 2022 at 01:19:37PM -0500, Michael Stone wrote:
>
> [...]
>
> > And this is why putting stuff into /etc/hosts is basically never the right
> > answer. :)
>
> Eye, beholder and things. I've got a couple of them like
On Tue, Jan 04, 2022 at 10:34:48AM -0800, James H. H. Lampert wrote:
> On 1/4/22 10:19 AM, Michael Stone wrote:
> > And this is why putting stuff into /etc/hosts is basically never the
> > right answer. :)
>
> Au contraire!
>
> Among other things, the host table is the best possible place to bloc
On Tue, Jan 04, 2022 at 01:19:37PM -0500, Michael Stone wrote:
[...]
> And this is why putting stuff into /etc/hosts is basically never the right
> answer. :)
Eye, beholder and things. I've got a couple of them like so:
# Pest:
127.0.0.1 www.google-analytics.com
127.0.0.1 ajax.google.com
On 1/4/22 10:19 AM, Michael Stone wrote:
And this is why putting stuff into /etc/hosts is basically never the
right answer. :)
Au contraire!
Among other things, the host table is the best possible place to block
access to certain unwanted domains. For example, if you add these entries:
> 0.
On Tue, Jan 04, 2022 at 01:09:06AM +0100, local10 wrote:
Jan 3, 2022, 23:08 by d...@randomstring.org:
Alright. Put this into your /etc/hosts temporarily:
[...]
OK, I understand now what the problem was. Quite a while ago I added a line
into the /etc/hosts to fix a temp DNS issue and completel
On Tue, Jan 04, 2022 at 12:50:39PM +0100, local10 wrote:
> Jan 4, 2022, 05:58 by to...@tuxteam.de:
>
> > Seems to work for me (currently). Are you still getting the error?
> >
>
>
> Not anymore, it has been solved:
> https://lists.debian.org/debian-user/2022/01/msg00096.html
>
> Thanks to eve
Jan 4, 2022, 05:58 by to...@tuxteam.de:
> Seems to work for me (currently). Are you still getting the error?
>
Not anymore, it has been solved:
https://lists.debian.org/debian-user/2022/01/msg00096.html
Thanks to everyone who responded.
Jan 3, 2022, 23:53 by loca...@tutanota.com:
> Jan 3, 2022, 23:08 by d...@randomstring.org:
>
>> Alright. Put this into your /etc/hosts temporarily:
>>
>> 152.195.33.23 www.usps.com tools.usps.com www.usps.gov
>>
>> That's unlikely to be an optimal IP from their CDN, but it is
>> currently working
21 matches
Mail list logo