On 10/14/18 12:45 AM, goli...@dyne.org wrote:
On 2018-10-14 01:52, Rick Moen wrote:
Anyhow, it can be vital to know _what_ server is answering (well or
otherwise) your system's DNS questions by default. Looking at
/etc/resolv.conf should answer that question.
I don't have anything in
Hi, Steve!
On 17/10/18 at 07:34, Steve Litt wrote:
> Yes, yes, yes, yes, YES!
> I just got thru updating my unbound doc at
> http://troubleshooters.com/linux/unbound_nsd/unbound.htm , and added a
> new glossary.
i noticed a couple of lines are missing in the reverse-zone
definitions of the
Quoting goli...@dyne.org (goli...@dyne.org):
> Can't say for sure. Wouldn't Comcast/Spectrum/RoadRunner(TWC) be
> able to throttle traffic more effectively using their in-house DNS
> service? Maybe unbound escapes their reach?
I don't think this is likely for various reasons including the fact
On Wed, 17 Oct 2018 11:31:41 -0500, goli...@dyne.org wrote in message
:
> On 2018-10-15 22:22, mett wrote:
> > On 2018年10月16日 11:16:30 JST, goli...@dyne.org wrote:
> >>> On Sat, Oct 13, 2018 at 05:30:56PM -0500, goli...@dyne.org wrote
> >>>
> >> It is incredibly annoying to be connected to
On 2018-10-15 22:22, mett wrote:
On 2018年10月16日 11:16:30 JST, goli...@dyne.org wrote:
On Sat, Oct 13, 2018 at 05:30:56PM -0500, goli...@dyne.org wrote
It is incredibly annoying to be connected to a rather fast pipe yet
have
to travel on what feels like 56k connection to get to where I can
Quoting Steve Litt (sl...@troubleshooters.com):
> I just got thru updating my unbound doc at
> http://troubleshooters.com/linux/unbound_nsd/unbound.htm , and added a
> new glossary. This is very necessary because there are so many
> contradictory terms for things over the Internet. I'm not saying
On Tue, 16 Oct 2018 10:46:29 +0200
Didier Kryn wrote:
> Le 16/10/2018 à 07:10, Rick Moen a écrit :
> > Quoting goli...@dyne.org (goli...@dyne.org):
> >
> >> With help from my Devuan friends the connection times have improved
> >> significantly. After little poking around and a very
On Sun, 14 Oct 2018 02:30:09 -0500
goli...@dyne.org wrote:
>
> wicd finds a connection automatically. I think it uses DHCP. All
> these years I have managed to avoid the fine points of networking
> because it's always "just worked".
> > Anyway, /etc/resolv.conf is one of the primary
On Sun, 14 Oct 2018 09:13:12 +0200
Didier Kryn wrote:
> Hi Golinux.
>
> Did you try to list your favorite sites in /etc/hosts ? This is
> a primitive and oldfashioned, but very simple, way to see if you hit
> a DNS issue or are routed to a slow lane.
>
> Didier
Nice!
SteveT
Le 16/10/2018 à 20:28, Rick Moen a écrit :
Quoting Didier Kryn (k...@in2p3.fr):
Any reading to recommend about recursive, authoritative or
what else name servers ?
Not trying to be perverse, but: What would you like to know?
I'll give you two answers, where the first one is my effort
Am 16/10/2018 um 10:46 schrieb Didier Kryn:
>
> Any reading to recommend about recursive, authoritative or what else
> name servers ?
IIRC it doesn't cover everything and by no means is it technical,
detailed or deep, but it's way too cute not to mention it:
https://howdns.works/
--
Quoting Didier Kryn (k...@in2p3.fr):
> Any reading to recommend about recursive, authoritative or
> what else name servers ?
Not trying to be perverse, but: What would you like to know?
I'll give you two answers, where the first one is my effort to avoid
seeming to promote my own writings.
Le 16/10/2018 à 07:10, Rick Moen a écrit :
Quoting goli...@dyne.org (goli...@dyne.org):
With help from my Devuan friends the connection times have improved
significantly. After little poking around and a very interesting
talk with my ISP, I decided that the ISP's DNS resolver was
contributing
Quoting goli...@dyne.org (goli...@dyne.org):
> With help from my Devuan friends the connection times have improved
> significantly. After little poking around and a very interesting
> talk with my ISP, I decided that the ISP's DNS resolver was
> contributing significantly to the slow connection
On 2018年10月16日 11:16:30 JST, goli...@dyne.org wrote:
>> On Sat, Oct 13, 2018 at 05:30:56PM -0500, goli...@dyne.org wrote
>>
>It is incredibly annoying to be connected to a rather fast pipe yet
>have
>to travel on what feels like 56k connection to get to where I can
>benefit from it.
>>
>>
On Sat, Oct 13, 2018 at 05:30:56PM -0500, goli...@dyne.org wrote
It is incredibly annoying to be connected to a rather fast pipe yet have
to travel on what feels like 56k connection to get to where I can
benefit from it.
golinux
With help from my Devuan friends the connection times have
Quoting Didier Kryn (k...@in2p3.fr):
> Avahi daemon is the Linux dnssd service. dnssd is a protocol
> for service discovery on LAN (formerly known as Apple "Bonjour").
> The essential utility for me is to allow to discover CUPS servers on
> the LAN, because recent versions of CUPS advertise
Quoting Hendrik Boom (hend...@topoi.pooq.com):
> On Sat, Oct 13, 2018 at 11:52:34PM -0700, Rick Moen wrote:
> >
> > If you look in /etc/resolv.conf, you'll see one or more 'nameserver'
> > lines. Mine on my server is like this:
> >
> > $ cat /etc/resolv.conf
> > search linuxmafia.com
Rick Moen wrote:
> It's the most versatile and reliable tool around for testing DNS
> functionality -- which in turn is useful to be able to test separately
> from the separate task of actually making connections for services after
> resolving DNS names to find where to reach them.
+1 for that
Am 2018-10-14 14:23, schrieb Hendrik Boom:
And OT do I even need avahi installed at all?
What is it needed for?
try "aptitude why avahi-daemon" to see why it was installed. Your
normally don't need it. Maybe it was installed as a recommend.
Avahi is a zeroconf tool like Apples Bonjour to
Le 14/10/2018 à 09:45, goli...@dyne.org a écrit :
I don't have anything in /etc/resolvconf except an avahi-daemon in
/update-libc.d/ Maybe I should start by putting 8.8.8.8 in
/etc/resolvconf?
And OT do I even need avahi installed at all?
Avahi daemon is the Linux dnssd service.
On Sun, 14 Oct 2018 08:23:09 -0400
Hendrik Boom wrote:
> On Sun, Oct 14, 2018 at 02:45:07AM -0500, goli...@dyne.org wrote:
> ...
> >
> > And OT do I even need avahi installed at all?
>
> What is it needed for?
I do not really know, if you have DNS set up correctly, it isn't
required and guess
On Sun, Oct 14, 2018 at 02:45:07AM -0500, goli...@dyne.org wrote:
...
>
> And OT do I even need avahi installed at all?
What is it needed for?
>
> OK. I am a complete idiot and ignored the dot in the filename so didn't
> even see the resolv.conf file. This is what's in it:
>
> domain
On Sat, Oct 13, 2018 at 11:52:34PM -0700, Rick Moen wrote:
> Quoting goli...@dyne.org (goli...@dyne.org):
>
> > Well, I picked a few names at random. netflix pops up as soon as I
> > hit enter. Ditto Microsoft, outlook, Apple, twitter, instagram,
> > reddit, snapchat and facebook. Redhat is in a
Quoting goli...@dyne.org (goli...@dyne.org):
> I don't have anything in /etc/resolvconf except an avahi-daemon in
> /update-libc.d/ Maybe I should start by putting 8.8.8.8 in
> /etc/resolvconf?
I didn't say _/etc/resolvconf_ (which is a directory).
I said _/etc/resolv.conf_ (which is a regular
On 2018-10-14 01:52, Rick Moen wrote:
Anyhow, it can be vital to know _what_ server is answering (well or
otherwise) your system's DNS questions by default. Looking at
/etc/resolv.conf should answer that question.
I don't have anything in /etc/resolvconf except an avahi-daemon in
On 2018-10-14 01:52, Rick Moen wrote:
Quoting goli...@dyne.org (goli...@dyne.org):
Well, I picked a few names at random. netflix pops up as soon as I
hit enter. Ditto Microsoft, outlook, Apple, twitter, instagram,
reddit, snapchat and facebook. Redhat is in a slower lane as is the
Linux
Le 14/10/2018 à 04:38, goli...@dyne.org a écrit :
On 2018-10-13 20:59, Hendrik Boom wrote:
On Sat, Oct 13, 2018 at 05:30:56PM -0500, goli...@dyne.org wrote:
On 2018-10-13 09:05, Steve Litt wrote:
> On Fri, 12 Oct 2018 14:21:19 -0500
> goli...@dyne.org wrote:
>
> > Greetings everyone,
> >
> >
Quoting goli...@dyne.org (goli...@dyne.org):
> Well, I picked a few names at random. netflix pops up as soon as I
> hit enter. Ditto Microsoft, outlook, Apple, twitter, instagram,
> reddit, snapchat and facebook. Redhat is in a slower lane as is the
> Linux Foundation. Even Ubuntu takes a while.
On 2018-10-13 22:22, mett wrote:
On 2018年10月14日 10:59:54 JST, Hendrik Boom
wrote:
On Sat, Oct 13, 2018 at 05:30:56PM -0500, goli...@dyne.org wrote:
On 2018-10-13 09:05, Steve Litt wrote:
> On Fri, 12 Oct 2018 14:21:19 -0500
> goli...@dyne.org wrote:
>
> > Greetings everyone,
> >
> > Something
On 2018年10月14日 10:59:54 JST, Hendrik Boom wrote:
>On Sat, Oct 13, 2018 at 05:30:56PM -0500, goli...@dyne.org wrote:
>> On 2018-10-13 09:05, Steve Litt wrote:
>> > On Fri, 12 Oct 2018 14:21:19 -0500
>> > goli...@dyne.org wrote:
>> >
>> > > Greetings everyone,
>> > >
>> > > Something funny is
On 2018-10-13 20:59, Hendrik Boom wrote:
On Sat, Oct 13, 2018 at 05:30:56PM -0500, goli...@dyne.org wrote:
On 2018-10-13 09:05, Steve Litt wrote:
> On Fri, 12 Oct 2018 14:21:19 -0500
> goli...@dyne.org wrote:
>
> > Greetings everyone,
> >
> > Something funny is going on with my networking.
On Sat, Oct 13, 2018 at 05:30:56PM -0500, goli...@dyne.org wrote:
> On 2018-10-13 09:05, Steve Litt wrote:
> > On Fri, 12 Oct 2018 14:21:19 -0500
> > goli...@dyne.org wrote:
> >
> > > Greetings everyone,
> > >
> > > Something funny is going on with my networking. It's taking a very
> > > long
On 2018-10-13 09:05, Steve Litt wrote:
On Fri, 12 Oct 2018 14:21:19 -0500
goli...@dyne.org wrote:
Greetings everyone,
Something funny is going on with my networking. It's taking a very
long time to resolve host IPs across all browsers. It's been
happening for a week or two but I'm just now
On Fri, 12 Oct 2018 14:21:19 -0500
goli...@dyne.org wrote:
> Greetings everyone,
>
> Something funny is going on with my networking. It's taking a very
> long time to resolve host IPs across all browsers. It's been
> happening for a week or two but I'm just now getting annoyed enough
> to
On 13-10-18 00:26, Rick Moen wrote:
> Quoting goli...@dyne.org (goli...@dyne.org):
>
>>> Disabling IPv6 can be done with adding in /etc/sysctl.conf:
>>>
>>> net.ipv6.conf.all.disable_ipv6 = 1
>>>
>>> and executing sysctl -p or reboot
>>>
>>> Grtz.
>>>
>>> Nick
>>>
>>>
>> Thanks Nick. Much
On 10/12/18 4:55 PM, Gregory Nowak wrote:
On Fri, Oct 12, 2018 at 04:35:17PM -0500, goli...@dyne.org wrote:
Thanks for the responses. I suspect that IPv6 might indeed be the culprit.
I doubt it, since both traceroutes are using IPv4, and both have odd delays.
$ traceroute google.com
On Fri, Oct 12, 2018 at 04:35:17PM -0500, goli...@dyne.org wrote:
> Thanks for the responses. I suspect that IPv6 might indeed be the culprit.
I doubt it, since both traceroutes are using IPv4, and both have odd delays.
> $ traceroute google.com
> traceroute to google.com (74.125.129.102), 30
Quoting Antony Stone (antony.st...@devuan.open.source.it):
> True, if it's IPv6 *only*.
>
> That's pretty unusual at present.
My point being that this assumption should be borne in mind and if
necessary revisited, if shutting off IPV6.
___
Dng
On Saturday 13 October 2018 at 00:26:04, Rick Moen wrote:
> Quoting goli...@dyne.org:
> > >Disabling IPv6 can be done with adding in /etc/sysctl.conf:
> > >
> > >net.ipv6.conf.all.disable_ipv6 = 1
> > >
> > >and executing sysctl -p or reboot
> >
> Well, might make it really difficult to use
Quoting goli...@dyne.org (goli...@dyne.org):
> >Disabling IPv6 can be done with adding in /etc/sysctl.conf:
> >
> >net.ipv6.conf.all.disable_ipv6 = 1
> >
> >and executing sysctl -p or reboot
> >
> >Grtz.
> >
> >Nick
> >
> >
>
> Thanks Nick. Much appreciated. Will sort that later and report
On 2018-10-12 17:06, info at smallinnovations dot nl wrote:
On 12-10-18 23:35, goli...@dyne.org wrote:
On 2018-10-12 15:25, Rick Moen wrote:
Quoting info at smallinnovations dot nl (i...@smallinnovations.nl):
I had something similar but with ssh. Some debugging learned that
IPv6
was
On 12-10-18 23:35, goli...@dyne.org wrote:
> On 2018-10-12 15:25, Rick Moen wrote:
>> Quoting info at smallinnovations dot nl (i...@smallinnovations.nl):
>>
>>> I had something similar but with ssh. Some debugging learned that IPv6
>>> was preferred but my ISP connection does not have IPv6. After
On 2018-10-12 15:25, Rick Moen wrote:
Quoting info at smallinnovations dot nl (i...@smallinnovations.nl):
I had something similar but with ssh. Some debugging learned that IPv6
was preferred but my ISP connection does not have IPv6. After 60
seconds
ssh time out and changed back to IPv4 and
Quoting info at smallinnovations dot nl (i...@smallinnovations.nl):
> I had something similar but with ssh. Some debugging learned that IPv6
> was preferred but my ISP connection does not have IPv6. After 60 seconds
> ssh time out and changed back to IPv4 and made connection after all.
> After
On 12-10-18 21:21, goli...@dyne.org wrote:
> Greetings everyone,
>
> Something funny is going on with my networking. It's taking a very
> long time to resolve host IPs across all browsers. It's been happening
> for a week or two but I'm just now getting annoyed enough to
> troubleshoot.
>
> When
Greetings everyone,
Something funny is going on with my networking. It's taking a very long
time to resolve host IPs across all browsers. It's been happening for a
week or two but I'm just now getting annoyed enough to troubleshoot.
When I ping Google at 8.8.8.8 or various websites, they
47 matches
Mail list logo
