Rick Moen wrote:
>> IFF we are going to put stuff in to work around problems for one set
>> of edge cases (and IMO it's debatable whether we should), then why not
>> also cater for what is possibly a larger group of edge cases ? Your
>> argument seems to be "this is the only set of edge cases I'm
On Wed, 04 Jan 2017, Jaromil wrote:
> On Wed, 04 Jan 2017, Alessandro Selli wrote:
> > How's the experiment been so far?
>
> still have to start the first experiment, I thought we could now, but
> then I like too much the ASCII art in the thread to cheerlead towards
> a web platform...
>
> howe
Rick Moen wrote:
> I wasn't suggesting a distro installer checkbox item offering local
> recursive nameservice for use during installation. I was suggesting a
> checkbox item offering to install a local recursive nameserver (and
> resolver conf to use it) on the installed system.
Fair enough -
Quoting Simon Hobson (li...@thehobsons.co.uk):
> I'm suggesting that spending a lot of valuable dev time knocking a few
> seconds off* an install isn't the best use of that resource.
I wasn't suggesting a distro installer checkbox item offering local
recursive nameservice for use during installat
Rick Moen wrote:
> Why settle for bad when you can have excellent for free? But you don't
> see it, so we're wasting time talking.
Actually I do see exactly what you are saying - and I have come across
resolvers with poor performance. For **for the duration of an install**, just
how many DNS
Quoting Simon Hobson (li...@thehobsons.co.uk):
> So, OK add it as an option in an advanced level install.
That would be pointless. I've already detailed why. This is just a
complicated way of saying 'We're not bothering'. If you-all don't want
to bother, fine. Do it the simple way, by doing n
Rick Moen wrote:
>> IFF we are going to put stuff in to work around problems for one set
>> of edge cases (and IMO it's debatable whether we should), then why not
>> also cater for what is possibly a larger group of edge cases ? Your
>> argument seems to be "this is the only set of edge cases I'm
I just realised I probably need to correct an error:
> PowerDNS Recursor is the recursive-server matching element to PowerDNS
> Authoritative Server from the same folks. Both are back-ended into SQL
> databases (default MyS
Quoting Simon Hobson (li...@thehobsons.co.uk):
> IFF we are going to put stuff in to work around problems for one set
> of edge cases (and IMO it's debatable whether we should), then why not
> also cater for what is possibly a larger group of edge cases ? Your
> argument seems to be "this is the o
On 5 Jan 2017, at 23:33, Rick Moen wrote:
> Quoting Simon Hobson (li...@thehobsons.co.uk):
>> Rick Moen wrote:
>>
>>> Without objection, I'll point out that one leading advantage of a local
>>> recursive server (what you probably mean when you say 'caching DNS
>>> server'[1]) is that it Just W
On Thu, 5 Jan 2017 09:21:08 -0600 (CST), ja...@beau.org wrote in
message <54290.192.168.250.61.1483629668.squir...@beau.org>:
> > Il giorno Wed, 4 Jan 2017 15:11:36 -0800
> > Rick Moen ha scritto:
>
> >> There is obviously a happy middle ground.
>
> > Yes, it's called: "let the user decide".
I wrote:
> I didn't think it necessary to belabour the fact that if a network
> daemon, one that inherently needs open Internet access to work, is
> prevented from having open Internet access, it won't work.
I should hasten to add, sure, there is also the hotel wifi
captive-portal annoyance. Mig
Quoting Simon Hobson (li...@thehobsons.co.uk):
> Rick Moen wrote:
>
> > Without objection, I'll point out that one leading advantage of a local
> > recursive server (what you probably mean when you say 'caching DNS
> > server'[1]) is that it Just Works
>
> Unless you are in one of the situations
Quoting Steve Litt (sl...@troubleshooters.com):
[BIND9:]
> I didn't like it for that same reason, but always wondered if it were
> just a case of my drinking the djb kool aid.
Dan's many criticisms of BIND9 and of its BIND8 predecessor (a
from-scratch rewrite separating the two) were always wel
ja...@beau.org wrote:
> I kind of like:
>
> A) Beginner
> B) Experienced
> C) Expert
> D) NetGod
Isn't this missing the point ?
If the problem is working around broken DHCP and/or local resolvers, then it
comes down to :
A) If network configuration works and we can resolve the names we need to
On Thu, 5 Jan 2017 13:47:14 -0800
Rick Moen wrote:
> Quoting Steve Litt (sl...@troubleshooters.com):
>
> > Which of the preceding is best? I've always been partial to
> > dnscache/tinydns, but installing it is a long cumbersome procedure
> > giving Arch installation a run for its money. I've nev
Quoting Steve Litt (sl...@troubleshooters.com):
> Yes yes yes, I understand that now. I hadn't really thought it through
> when I asked that question.
>
> In general though, I like the idea of public DNS as something that
> *just works*. I can later switch to the DNS server suggested by my DHCP
>
Quoting Steve Litt (sl...@troubleshooters.com):
> I really like djbdns, but its installation is long and error prone, and
> djb uses directories like /service that no distro will ever use.
Dan really hates FHS. ;->
I haven't really properly investigated the three (arguably still four)
maintaine
Quoting Steve Litt (sl...@troubleshooters.com):
> Which of the preceding is best? I've always been partial to
> dnscache/tinydns, but installing it is a long cumbersome procedure
> giving Arch installation a run for its money. I've never heard of
> Unbound, PowerDNS Recursor, or Deadwood.
The que
On Thu, 5 Jan 2017 15:02:09 -0500
Steve Litt wrote:
> Which of the preceding is best? I've always been partial to
> dnscache/tinydns, but installing it is a long cumbersome procedure
> giving Arch installation a run for its money. I've never heard of
> Unbound, PowerDNS Recursor, or Deadwood.
O
On Wed, 4 Jan 2017 15:11:36 -0800
Rick Moen wrote:
> Quoting Alessandro Selli (alessandrose...@linux.com):
>
> > This is something that belongs to a different stage in the OS
> > installation, when:
> >
> > 1) the user determined that a DNS server must be installed;
> > 2) that it has to run as
On Wed, 04 Jan 2017 22:00:29 +
Rainer Weikusat wrote:
> Steve Litt writes:
> > On Tue, 3 Jan 2017 11:06:53 +0100
> > Jaromil wrote:
> >
> >> On Mon, 02 Jan 2017, Jaromil wrote:
> >>
> >> > what a pity Debian has switched to Google's DNS by default.
> >>
> >> for the record and the
On Wed, 4 Jan 2017 21:27:36 +0100 (CET)
k...@aspodata.se wrote:
> Rick Moen:
> ...
> > But yet again, nobody is yet thinking to include what seems most
> > obvious to me:
> >
> > [ ] Run Unbound as local recursive nameserver on this host.
> > [ ] Run PowerDNS Recursor as local recursive namese
Hendrik Boom writes:
> On Wed, Jan 04, 2017 at 10:00:29PM +, Rainer Weikusat wrote:
>> I'm running a caching resolver locally because that "always works"
>> (unless blocked by the ISP which may become mandatory in the UK 'soon'
>> ...), even if an out-of-the-ordinary cache flush is called for
> Il giorno Wed, 4 Jan 2017 15:11:36 -0800
> Rick Moen ha scritto:
>> There is obviously a happy middle ground.
> Yes, it's called: "let the user decide". Level (0) menu:
> A) Let the install program choose all the required settings (basic,
> no-frills,
> automatic install, zero questions a
Quoting Alessandro Selli (alessandrose...@linux.com):
I skipped down to the very bottom of your latest, and found:
> It's not any silly if you are to perform an install in a corporate,
> locked-down datacenter. The fact that you never had to operate in such
> an environment
...which is the
Il giorno Thu, 5 Jan 2017 02:26:25 -0800
Rick Moen ha scritto:
> Quoting Alessandro Selli (alessandrose...@linux.com):
>
>> I followed the same logic when I listed 26 alternate public DNS servers to
>> choose from. I know it contradicts my own argument that the install
>> program should ask the
Quoting Alessandro Selli (alessandrose...@linux.com):
> I followed the same logic when I listed 26 alternate public DNS servers to
> choose from. I know it contradicts my own argument that the install program
> should ask the fewest possible questions.
Before I follow you further down this rabbi
Il giorno Wed, 4 Jan 2017 15:11:36 -0800
Rick Moen ha scritto:
> Quoting Alessandro Selli (alessandrose...@linux.com):
>
>> This is something that belongs to a different stage in the OS
>> installation, when:
>>
>> 1) the user determined that a DNS server must be installed;
>> 2) that it has to
Quoting Hendrik Boom (hend...@topoi.pooq.com):
> Which brings us around full circle to the original question -- how to
> do a cache flush!
If the process that's caching is local to you, then restart the process
or (if supported) instruct it to throw away its state). If the process
doing caching
On Wed, Jan 04, 2017 at 10:00:29PM +, Rainer Weikusat wrote:
>
> I'm running a caching resolver locally because that "always works"
> (unless blocked by the ISP which may become mandatory in the UK 'soon'
> ...), even if an out-of-the-ordinary cache flush is called for because
> of a 'recent'
On 01/04/2017 07:24 AM, KatolaZ wrote:
> On Wed, Jan 04, 2017 at 01:10:31PM +0100, Alessandro Selli wrote:
>
> [cut]
>
>>> I'm kind of envisioning this as part of the initial system setup, so a
>>> little more like this.
>>> Though I fully admit caffeine hasn't kicked in yet, so I may be
>>
Quoting Alessandro Selli (alessandrose...@linux.com):
> This is something that belongs to a different stage in the OS
> installation, when:
>
> 1) the user determined that a DNS server must be installed;
> 2) that it has to run as a local recursive nameserver;
> 3) that a particular implementatio
> [alessandro@wkstn03 ~]$ ll /etc/resolv.conf
> lrwxrwxrwx 1 root root 27 set 28 20:24 /etc/resolv.conf ->
> /run/resolvconf/resolv.conf
> [alessandro@wkstn03 ~]$ head -2 /etc/resolv.conf
> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by
> resolvconf(8)
> # DO NOT EDIT THIS FIL
Il 03/01/2017 23:47, Rick Moen ha scritto:
> Quoting Simon Hobson (li...@thehobsons.co.uk):
>
>> OK, I stand corrected. But it's still having to manually "fix"
>> something that wasn't (as people point out) broken for 30 years and
>> now suddenly (and without warning) is now broken.
> As with Arnt
Quoting Rainer Weikusat (rweiku...@talktalk.net):
> Steve Litt writes:
> > What's wrong with 8.8.8.8?
>
> Why would I want to send a list of all web sites I visit to an
> advertising company providing a 'free' service who wants to have this
> information because it's valuable business data?
An
Simon Hobson wrote:
> The current version of the system resolver has a hard coded fall-back - if
> you don't specify any resolvers then it will automatically use Google's
> (silently) !
> Short version - a bug was raised, DD responded that it's important to protect
> people from having no DNS
Il 04/01/2017 20:45, Rick Moen ha scritto:
> Quoting Alessandro Selli (alessandrose...@linux.com):
>
>> "Your network stinks. What DNS servers do you want to use?
> [amazing list, ending with:]
>
>> [ ] Pick random ones
>> [ ] Pick the geographically closest ones
>> [ ] No DNS configuration now
>>
Steve Litt writes:
> On Tue, 3 Jan 2017 11:06:53 +0100
> Jaromil wrote:
>
>> On Mon, 02 Jan 2017, Jaromil wrote:
>>
>> > what a pity Debian has switched to Google's DNS by default.
>>
>> for the record and the sake of historical correctness:
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cg
Quoting k...@aspodata.se (k...@aspodata.se):
> Best suggestion to date.
>
> Regards,
> /Karl Hammar
Tack så mycket. (So as not to show undue favouritism among Scandinavian
languages. ;-> )
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglis
Rick Moen:
...
> But yet again, nobody is yet thinking to include what seems most obvious to
> me:
>
> [ ] Run Unbound as local recursive nameserver on this host.
> [ ] Run PowerDNS Recursor as local recursive nameserver on this host.
> [ ] Run BIND9 as local recursive nameserver on this host.
Quoting Alessandro Selli (alessandrose...@linux.com):
> "Your network stinks. What DNS servers do you want to use?
[amazing list, ending with:]
> [ ] Pick random ones
> [ ] Pick the geographically closest ones
> [ ] No DNS configuration now
>
> Given there is choice, why artificially limit peo
Hendrik Boom wrote:
> Don't several system comopnents, such as dhcp clients, happily rewrite
> resolve.conf, wiping out anything the sysadmin may have set up.
Yes, but if you are using DHCP to configure your interfaces, there's an
implicit assumption that you want "stuff" configured by a servi
Il giorno Wed, 4 Jan 2017 15:34:20 +
KatolaZ ha scritto:
> On Wed, Jan 04, 2017 at 04:18:10PM +0100, Alessandro Selli wrote:
>
> [cut]
>
> > > I am strongly convinced that we don't want to (and we should not, by
> > > any means) be responsible for DNS configuration, mainly because we
> > >
On 2017-01-04 05:26, Jaromil wrote:
On Wed, 04 Jan 2017, Alessandro Selli wrote:
[ ] Pick random ones
[ ] Pick the geographically closest ones
[ ] Show a list of public DNS servers to choose from
[ ] No DNS configuration now
What do you think?
running this and other similar polls could be
On Wed, Jan 04, 2017 at 03:34:20PM +, KatolaZ wrote:
> On Wed, Jan 04, 2017 at 04:18:10PM +0100, Alessandro Selli wrote:
>
> [cut]
>
> > > I am strongly convinced that we don't want to (and we should not, by
> > > any means) be responsible for DNS configuration, mainly because we
> > > don't
On Wed, Jan 04, 2017 at 04:18:10PM +0100, Alessandro Selli wrote:
[cut]
> > I am strongly convinced that we don't want to (and we should not, by
> > any means) be responsible for DNS configuration, mainly because we
> > don't want to have users complaining because they "..have set up the
> > fall
Il giorno Wed, 4 Jan 2017 12:24:40 +
KatolaZ ha scritto:
> On Wed, Jan 04, 2017 at 01:10:31PM +0100, Alessandro Selli wrote:
>
> [cut]
>
> > > I'm kind of envisioning this as part of the initial system setup, so a
> > > little more like this.
> > > Though I fully admit caffeine hasn't kic
On Wed, 4 Jan 2017 13:31:32 +0100
Jaromil wrote:
> On Wed, 04 Jan 2017, Alessandro Selli wrote:
>
> > > we did open Devuan's "community group" on Loomio to experiment
> > > with https://www.loomio.org/g/aZupNlWS
> >
> > How's the experiment been so far?
>
> still have to start the first expe
On Wed, 04 Jan 2017, Alessandro Selli wrote:
> > we did open Devuan's "community group" on Loomio to experiment with
> > https://www.loomio.org/g/aZupNlWS
>
> How's the experiment been so far?
still have to start the first experiment, I thought we could now, but
then I like too much the ASCII
On Wed, Jan 04, 2017 at 01:10:31PM +0100, Alessandro Selli wrote:
[cut]
> > I'm kind of envisioning this as part of the initial system setup, so a
> > little more like this.
> > Though I fully admit caffeine hasn't kicked in yet, so I may be
> > spouting more crazy than normal :).
> >
> > [*]
Il giorno Wed, 4 Jan 2017 12:26:35 +0100
Jaromil ha scritto:
>
> On Wed, 04 Jan 2017, Alessandro Selli wrote:
> >
> > [ ] Pick random ones
> > [ ] Pick the geographically closest ones
> > [ ] Show a list of public DNS servers to choose from
> > [ ] No DNS configuration now
> >
> > What do yo
Il giorno Wed, 04 Jan 2017 06:25:51 -0500
Dan Purgert ha scritto:
> Quoting Alessandro Selli :
>
> > Il giorno Wed, 04 Jan 2017 05:53:56 -0500
> > Dan Purgert ha scritto:
> >
> >> Quoting Alessandro Selli :
> >>
> >> > On Tue, 3 Jan 2017 at 22:03:47 + Arnt Gulbrandsen
> >> > wrote:
> >> >
Quoting Alessandro Selli :
Il giorno Wed, 04 Jan 2017 05:53:56 -0500
Dan Purgert ha scritto:
Quoting Alessandro Selli :
> On Tue, 3 Jan 2017 at 22:03:47 + Arnt Gulbrandsen
> wrote:
>
>> Alessandro Selli writes:
>>> This still doesn't explain why they decided to force-feed Google's DNS
On Wed, 04 Jan 2017, Alessandro Selli wrote:
>
> [ ] Pick random ones
> [ ] Pick the geographically closest ones
> [ ] Show a list of public DNS servers to choose from
> [ ] No DNS configuration now
>
> What do you think?
running this and other similar polls could be beneficial to inform
deci
Il giorno Wed, 04 Jan 2017 05:53:56 -0500
Dan Purgert ha scritto:
> Quoting Alessandro Selli :
>
> > On Tue, 3 Jan 2017 at 22:03:47 + Arnt Gulbrandsen
> > wrote:
> >
> >> Alessandro Selli writes:
> >>> This still doesn't explain why they decided to force-feed Google's DNS
> >>> server on
Quoting Alessandro Selli :
On Tue, 3 Jan 2017 at 22:03:47 + Arnt Gulbrandsen
wrote:
Alessandro Selli writes:
This still doesn't explain why they decided to force-feed Google's DNS
server on the user without prompting the poor fellow any possible choice.
"Your network sucks. Do you wa
On Tue, 3 Jan 2017 at 22:03:47 + Arnt Gulbrandsen
wrote:
> Alessandro Selli writes:
>> This still doesn't explain why they decided to force-feed Google's DNS
>> server on the user without prompting the poor fellow any possible choice.
>
> "Your network sucks. Do you want to [ ] use google o
On Tue, 3 Jan 2017 18:42:37 -0500
Hendrik Boom wrote:
> Don't several system comopnents, such as dhcp clients, happily
> rewrite resolve.conf, wiping out anything the sysadmin may have set
> up.
Well, yes they do - and even if we don't want to solve that by KISSing
away e.g. network-manager and
Quoting Hendrik Boom (hend...@topoi.pooq.com):
> Don't several system components, such as dhcp clients, happily rewrite
> resolve.conf, wiping out anything the sysadmin may have set up.
This well-known problem also has a somewhat known solution, a piece of
software called resolvconf . (Note to
On Tue, 3 Jan 2017 20:35:22 +0100
Alessandro Selli wrote:
> On 03/01/2017 at 18:20, Steve Litt wrote:
> > On Tue, 3 Jan 2017 11:06:53 +0100
> > Jaromil wrote:
> >
> >> On Mon, 02 Jan 2017, Jaromil wrote:
> >>
> >>> what a pity Debian has switched to Google's DNS by default.
> >> for the
On Tue, Jan 03, 2017 at 06:42:37PM -0500, Hendrik Boom wrote:
[cut]
>
> Don't several system comopnents, such as dhcp clients, happily rewrite
> resolve.conf, wiping out anything the sysadmin may have set up.
>
Not if you have "chattr +a /etc/resolv.conf", as I normally do. I
think the proble
On Tue, Jan 03, 2017 at 08:55:40PM +, Simon Hobson wrote:
> Steve Litt wrote:
>
> > What's wrong with 8.8.8.8? It's Google's public DNS, and for me, it
> > always works.
>
> That's fine - no-one is saying that you shouldn't use them if **you** want to.
>
> What people object to is a hidden
Consulting https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658, I
am able to hazard a guess at the answer to this question:
> Any idea which... talented person wrote that changeset for the system
> resolver? And how I avoid sharing cities, time zones, preferably
> continents, etc. with him/h
Quoting Simon Hobson (li...@thehobsons.co.uk):
> The current version of the system resolver has a hard coded fall-back
> - if you don't specify any resolvers then it will automatically use
> Google's (silently) !
I don't normally me-too content-free comments, but:
Wow. Just wow. {boggle}
I r
Rick Moen wrote:
> You probably have some data on this matter that I lack.
I read the Debian bug report someone linked to some messages back in this
thread.
> Is this some
> systemd brain-damage you're referring to? Some file that gets consulted
> instead of /etc/resolv.conf ?
The current ve
Quoting Simon Hobson (li...@thehobsons.co.uk):
> OK, I stand corrected. But it's still having to manually "fix"
> something that wasn't (as people point out) broken for 30 years and
> now suddenly (and without warning) is now broken.
As with Arnt and me, we stand in strenuous agreement.
> But yo
Rick Moen wrote:
>> Even worse is when there isn't a
>> mechanism for turning this off.
>
> Well, not quite. if you know *ix at all[0]:
>
> # sed -i 's/^nameserver/#nameserver/' /etc/resolv.conf
>
>
> To disable system DNS (but not /etc/hosts) entirely:
>
> # cp /etc/nsswitch.conf /etc/nssw
On Tue, 03 Jan 2017, Rick Moen wrote:
> I would suggest, if the installing sysadmin has opted to not
> configure any DNS nameservice at all, i.e., was prompted for
> nameserver IP and provided none, and also had did not opt to have
> one given to the host with a DHCP lease, then the installing
> s
On Tue, Jan 03, 2017 at 12:42:48PM -0800, Rick Moen wrote:
> I would suggest, if the installing sysadmin has opted to not configure
> any DNS nameservice at all, i.e., was prompted for nameserver IP and
> provided none, and also had did not opt to have one given to the host
> with a DHCP lease, the
Alessandro Selli writes:
This still doesn't explain why they decided to force-feed Google's DNS
server on the user without prompting the poor fellow any possible choice.
"Your network sucks. Do you want to [ ] use google or [ ] just give up?"
BTW, how many Debian installations are perform
Quoting Arnt Gulbrandsen (a...@gulbrandsen.priv.no):
> I wrote:
> >This year I've seen...
>
> No I haven't ;) Happy new year, everyone!
Og godt nytt år! ;->
(Watching season one of Okkupert lately, sometimes even turning off the
subtitles.)
___
Dng
Simon Hobson writes:
For the rest of us, if we have no DNS servers in resolv.conf
then we expect the system to respect that and not do DNS
resolution. That is the **ONLY** correct behaviour.
What is absolutely, 100%, not acceptable behaviour is what's
been done - to silently do something that
On 03/01/2017 at 22:38, Arnt Gulbrandsen wrote:
> Alessandro Selli writes:
>> Why are Debian
>> folks so eager at increasing Google's traffic and "free" "services"?
>
> Just a guess: Because so many of the resolvers at random hotels suck,
> and that suckage causes support load.
>
> This year I've s
Quoting Arnt Gulbrandsen (a...@gulbrandsen.priv.no):
> Alessandro Selli writes:
> >Why are Debian
> >folks so eager at increasing Google's traffic and "free" "services"?
>
> Just a guess: Because so many of the resolvers at random hotels
> suck, and that suckage causes support load.
Many ISP rec
Rick Moen writes:
You might not have noticed that you were strenuously agreeing with me.
I mixed up the participants in the thread while reading through the posts.
Sorry.
Arnt
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/c
Quoting Arnt Gulbrandsen (a...@gulbrandsen.priv.no):
> Rick Moen writes:
> >One recursive namserver per LAN is obviously better than several on
> >grounds of multiple considerations that I won't belabour here.
>
> Is it, really? Significantly?
Really but absolutely _not_ significantly. As I als
I wrote:
This year I've seen...
No I haven't ;) Happy new year, everyone!
Arnt
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Alessandro Selli writes:
Why are Debian
folks so eager at increasing Google's traffic and "free" "services"?
Just a guess: Because so many of the resolvers at random hotels suck, and
that suckage causes support load.
This year I've seen almost infinitely slow resolvers, resolvers that filter
Steve Litt writes:
What's wrong with 8.8.8.8? It's Google's public DNS, and for me, it
always works.
Didn't work for me at the captive portal in the hotel I was in two weeks
ago.
There are two kinds of hotel networks that block 8.8.8.8: Hotels in China,
and ones that block all DNS except th
Rick Moen writes:
One recursive namserver per LAN is obviously better than several on
grounds of multiple considerations that I won't belabour here.
Is it, really? Significantly?
It eases the load on the root and big-zone TLDs. I've heard that most of
their load is caused by other factors, th
Am concurring, but quibbling on a minor detail, anyway.
Quoting Simon Hobson (li...@thehobsons.co.uk):
> What is absolutely, 100%, not acceptable behaviour is what's been done
> - to silently do something that no sane admin would expect, and many
> people have objections to doing. Even worse is w
On 03/01/2017 at 21:47, Rick Moen wrote:
> Quoting Steve Litt (sl...@troubleshooters.com):
>
>> What's wrong with 8.8.8.8?
> Nothing at all if you want it. When asked for namservice IPs, just enter
> '8.8.8.8' and '8.8.4.4'. Done.
>
> Jaromir's question amounted to 'If the installing sysadmin has
Steve Litt wrote:
> What's wrong with 8.8.8.8? It's Google's public DNS, and for me, it
> always works.
That's fine - no-one is saying that you shouldn't use them if **you** want to.
What people object to is a hidden change, where something that **should** work
one way (DNS lookups fail if no
Quoting Simon Hobson (li...@thehobsons.co.uk):
> Rick Moen wrote:
>
>> My modest suggestion is that it's in Linux users' interest to not
>> outsource recursive service to anyone at all. Having the necessary
>> recursive nameservice be on one of one's own local machines improves
>> network perfo
Quoting Steve Litt (sl...@troubleshooters.com):
> What's wrong with 8.8.8.8?
Nothing at all if you want it. When asked for namservice IPs, just enter
'8.8.8.8' and '8.8.4.4'. Done.
Jaromir's question amounted to 'If the installing sysadmin has opted
neither for a recursive namserver IP nor DHC
Quoting Jaromil (jaro...@dyne.org):
> for the record and the sake of historical correctness:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658
I install Debian so rarely (and always supply my own recursive
nameserver IP when I do) that I never noticed this policy decision. The
only good
On 03/01/2017 at 18:20, Steve Litt wrote:
> On Tue, 3 Jan 2017 11:06:53 +0100
> Jaromil wrote:
>
>> On Mon, 02 Jan 2017, Jaromil wrote:
>>
>>> what a pity Debian has switched to Google's DNS by default.
>> for the record and the sake of historical correctness:
>>
>> https://bugs.debian.org/cgi-b
On Tue, Jan 03, 2017 at 12:20:09PM -0500, Steve Litt wrote:
[cut]
>
> What's wrong with 8.8.8.8? It's Google's public DNS, and for me, it
> always works. There are two kinds of people: Those who like Google, and
> those who hate it. The first group can take pride in using Google's
> public DNS,
On Tue, 3 Jan 2017 11:06:53 +0100
Jaromil wrote:
> On Mon, 02 Jan 2017, Jaromil wrote:
>
> > what a pity Debian has switched to Google's DNS by default.
>
> for the record and the sake of historical correctness:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658
>
> there is howev
On Mon, 02 Jan 2017, Jaromil wrote:
> what a pity Debian has switched to Google's DNS by default.
for the record and the sake of historical correctness:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658
there is however an issue we need to look at for Devuan: it seems the
default dns res
Rick Moen wrote:
> It should be noted that many programs presume to cache DNS, e.g., Web
> browsers do, as does the Java runtime.
Indeed.
Not only that, but many cache content as well - browser caching can be a real
PITA when it caches "the wrong thing", and especially with "clever" browsers
t
On Mon, Jan 02, 2017 at 07:20:36AM +0100, Jaromil wrote:
> dear Rick,
>
> On Sun, 01 Jan 2017, Rick Moen wrote:
>
> > In skimming through the dnscrypt source code, I see that it's a DNS
> > tool to proxy queries over DNSCrypt protocol (that invokes ldns in
> > the process of doing its work) -- bu
dear Rick,
On Sun, 01 Jan 2017, Rick Moen wrote:
> In skimming through the dnscrypt source code, I see that it's a DNS
> tool to proxy queries over DNSCrypt protocol (that invokes ldns in
> the process of doing its work) -- but it is not a recursive
> nameserver
yes you are right here, dnscrypt
Quoting Jaromil (jaro...@dyne.org):
> On Sun, 01 Jan 2017, Rick Moen wrote:
>
> > IMO look no further than Unbound
>
> I disagree :^) It is worth looking further here.
>
> In Dowse, our free software project focusing on layer 2 and 3
> awareness on LAN, we are working a lot on DNS using dnscryp
On Sun, 01 Jan 2017, Rick Moen wrote:
> IMO look no further than Unbound
I disagree :^) It is worth looking further here.
In Dowse, our free software project focusing on layer 2 and 3
awareness on LAN, we are working a lot on DNS using dnscrypt.
This is the surface http://crowd.dowse.eu
knowin
Quoting Hendrik Boom (hend...@topoi.pooq.com):
> I'll look for the various programs mentioned here, and see if they are
> present on my system...
Realistically, they won't be unless you put them there.
(I've long tried to gently poke Linux users, and indeed Linux
distributions, into ceasing to
On Sun, Jan 01, 2017 at 02:11:27PM -0800, Rick Moen wrote:
> Quoting Simon Hobson (li...@thehobsons.co.uk):
>
> > What do /etc/resolv.conf and /etc/nssswitch.conf have in them ?
> > Though to be honest, other than the systems I have BIND running on,
> > DNS resolution is something of a black box t
Quoting Rowland Penny (rpenny241...@gmail.com):
> He is probably running dnsmasq (well part of it), is there a line
> in /etc/hosts that starts '127.0.1.1' ?
If he does, then he has caching at (at least) two places, in Dnsmasq
(which is a caching forwarder) and in the real recursive namserver to
On Sun, 1 Jan 2017 14:11:27 -0800
Rick Moen wrote:
> Quoting Simon Hobson (li...@thehobsons.co.uk):
>
> > What do /etc/resolv.conf and /etc/nssswitch.conf have in them ?
> > Though to be honest, other than the systems I have BIND running on,
> > DNS resolution is something of a black box to me.
1 - 100 of 105 matches
Mail list logo
