Le 07/03/2021 à 18:20, tito via Dng a écrit :
> On Sun, 7 Mar 2021 18:03:30 +0100
> Antony Stone wrote:
>
>> On Sunday 07 March 2021 at 17:59:22, Steve Litt wrote:
>>
>>> See this web page:
>>>
>>> https://en.wikipedia.org/wiki/Anti-pattern
>>>
>>> I'd say at least half of the listed
On Mon, 8 Mar 2021 20:00:46 +1100
wirelessduck--- via Dng wrote:
> What’s the consensus on Quad9? Are they any better from a privacy
> standpoint?
I personally do not trust any of the DNS-providers with such easy-
to-remember IP addresses. Also, if you want unfiltered results from
Quad9, you
Στις 8/3/21 12:29 π.μ., ο/η Rick Moen έγραψε:
Leaving aside my being disappointed about people willingly outsourcing
their recursive DNS to the second-nosiest company on the planet[1]
+1.1.1.1 ... don't forget cloudflare bullies..
but i do forward local queries to opennic (w/ dnscrypt) and
> On 8 Mar 2021, at 19:08, Dimitris via Dng wrote:
>
> Στις 8/3/21 12:29 π.μ., ο/η Rick Moen έγραψε:
>> Leaving aside my being disappointed about people willingly outsourcing
>> their recursive DNS to the second-nosiest company on the planet[1]
>
> +1.1.1.1 ... don't forget cloudflare
On Mon, 2021-03-08 at 10:08 +0200, Dimitris via Dng wrote:
> Στις 8/3/21 12:29 π.μ., ο/η Rick Moen έγραψε:
> > Leaving aside my being disappointed about people willingly
> > outsourcing
> > their recursive DNS to the second-nosiest company on the planet[1]
>
> +1.1.1.1 ... don't forget cloudflare
On Mon, 2021-03-08 at 06:40 -0700, Gabe Stanton via Dng wrote:
> On Mon, 2021-03-08 at 10:08 +0200, Dimitris via Dng wrote:
> > Στις 8/3/21 12:29 π.μ., ο/η Rick Moen έγραψε:
> > > Leaving aside my being disappointed about people willingly
> > > outsourcing
> > > their recursive DNS to the
Rick Moen said:
>The above is a vexing problem for travelers w/laptops who prefer to
>specify their own choice of nameserver and still use hotel/motel WiFi
>(and wired ethernet, actually). Best case, you have to disable your
>nameserver IP override long enough to navigate the captive portal, and
>On Mon, 2021-03-08 at 06:40 -0700, Gabe Stanton via Dng wrote:
>Oh, and one more thing since you mentioned icann, one thing to note is
>that opennic also has their own tld system, independent of icann. As a
>community of operators, they can do that. Of course no one can access
>their tld's
Redirecting this thread back to the list. See below q and a between
Steve and me.
On Mon, 2021-03-08 at 09:16 -0500, Steve Litt wrote:
> > On Mon, 2021-03-08 at 06:40 -0700, Gabe Stanton via Dng wrote:
> > Oh, and one more thing since you mentioned icann, one thing to note
> > is
> > that
Hi all,
When I added four opennic root servers to my unbound's root.hints, I
couldn't resolve grep.geek on my unbound server at 192.168.0.102, even
though I could resolve it from the opennic root servers.
Then I commented out all the icann root servers, restarted, and now I
can resolve grep.geek
On Mon, 2021-03-08 at 10:34 -0500, Steve Litt wrote:
> Hi all,
>
> When I added four opennic root servers to my unbound's root.hints, I
> couldn't resolve grep.geek on my unbound server at 192.168.0.102,
> even
> though I could resolve it from the opennic root servers.
>
> Then I commented out
It turns out 80 of the issue was a syntax error in the ALSA configuration.
For an unknown reason this mostly only caused an issue for web browsers.
In fact I only detected it when running some third party alsa software that
displayed a warning.
? mostly only ? it must be bedtime :)
publickey -
12 matches
Mail list logo
