On Fri, Dec 28, 2018 at 2:37 PM Florian Weimer wrote:
>
> * kamaraju kusumanchi:
>
> > I see a lot of differences between trial_6.txt and trial_4.txt. Does
> > that mean anything or is this variation expected?
>
> The first hop should be the same in all cases and reachable (no
> stars). It looks
* kamaraju kusumanchi:
> On Fri, Dec 28, 2018 at 3:51 AM wrote:
>>
>> Whenever your DNS fails try a "traceroute 8.8.8.8". Compare its results
>> to what you get when you do it at times where your DNS works. Perhaps
>> this sheds some light on it.
>
> That is tough to capture because the problem i
On Fri, Dec 28, 2018 at 3:51 AM wrote:
>
> Whenever your DNS fails try a "traceroute 8.8.8.8". Compare its results
> to what you get when you do it at times where your DNS works. Perhaps
> this sheds some light on it.
That is tough to capture because the problem is intermittent. When I
retry it s
On Fri, Dec 28, 2018 at 11:57:35AM +0100, Pascal Hambourg wrote:
> Le 28/12/2018 à 09:51, to...@tuxteam.de a écrit :
> >On Thu, Dec 27, 2018 at 11:41:48PM -0500, kamaraju kusumanchi wrote:
> >>How to debug intermittent name resolution failures on a Debian Stretch
> >>
Le 28/12/2018 à 09:51, to...@tuxteam.de a écrit :
On Thu, Dec 27, 2018 at 11:41:48PM -0500, kamaraju kusumanchi wrote:
How to debug intermittent name resolution failures on a Debian Stretch machine?
I take your DNS server is 8.8.8.8
And 8.8.4.4, as can be seen in /etc/resolv.conf.
My top
On Thu, Dec 27, 2018 at 11:41:48PM -0500, kamaraju kusumanchi wrote:
> How to debug intermittent name resolution failures on a Debian Stretch
> machine?
[...]
> ;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 11 ms
I take your DNS server is 8.8.8.8 (kids, do we have to hand off eve
How to debug intermittent name resolution failures on a Debian Stretch machine?
When it does not work:
% dig +trace github.com
; <<>> DiG 9.10.3-P4-Debian <<>> +trace github.com
;; global options: +cmd
;; connection timed out; no servers could be reached
When it works
7 matches
Mail list logo
