Subject: Re: Slow connections - DNS problems?
Further to my 20-30 second delay when firing up slrnpull:
Here are some of your responses and my replies:
On Wed Mar 24 13:08:20 2021 <tomas@tuxteam.de> wrote:
> On Tue, Mar 23, 2021 at 10:32:27PM -0700, Charlie Gibbs wrote:
>> [contents of /etc/resolv.conf -> /run/NetworkManager/resolv.conf]
>> # Generated by NetworkManager
>> search telus
>> nameserver 192.168.0.1
>> nameserver 75.153.171.122
>> nameserver 2001:568:ff09:10a::56
>> # NOTE: the libc resolver may not support more than 3 nameservers.
>> # The nameservers listed below may not be recognized.
>> nameserver 2001:568:ff09:10b::122
> The 20-30 seconds hint at a DNS timeout.
>
> Try removing your first entry (192.168.0.1) from resolv.conf and
> see whether this changes (don't restart, NM will clobber your
> changes!)
I tried removing the 192.168.0.1 line along with the "search telus"
line. I didn't notice any difference, but could this be because
this stuff is buffered somewhere? Perhaps I need to kick something
to make sure the new file is read.
On Wed Mar 24 13:08:25 2021 Darac Marjal <mailinglist@darac.org.uk> wrote:
> Do you have an IPv6 address? If you run "ip -c -6 a", do you have an
> address with "scope global"? You may have one with "scope link", but
> that won't help at the moment. If you do, then congratulations: Telus
> have provided you with a connection to the modern internet. If not, then
> you won't be able to reach these resolver addresses.
1: [36mlo: [0m<LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000
inet6 [34m::1[0m/128 scope host
valid_lft forever preferred_lft forever
2: [36menp0s25: [0m<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state
[32mUP [0mqlen 1000
inet6 [34m2001:569:74d8:9900:b476:fd78:f387:922c[0m/64 scope
global temporary dynamic
valid_lft 14655sec preferred_lft 14355sec
inet6 [34m2001:569:74d8:9900:5eff:35ff:fe07:33d2[0m/64 scope
global dynamic mngtmpaddr noprefixroute
valid_lft 14655sec preferred_lft 14355sec
inet6 [34mfe80::5eff:35ff:fe07:33d2[0m/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: [36mwlp3s0: [0m<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state
[32mUP [0mqlen 1000
inet6 [34m2001:569:74d8:9900:f953:7d51:de1c:b63d[0m/64 scope
global dynamic noprefixroute
valid_lft 14655sec preferred_lft 14355sec
inet6 [34mfe80::fb30:bc15:abf9:1f48[0m/64 scope link noprefixroute
valid_lft forever preferred_lft forever
On Wed Mar 24 13:08:45 2021 pioruns2019 <pioruns2019@gmx.com> wrote:
> You can use DNS Benchmark by Steve Gibson, written like 20 years ago
> in assembly language. This will test your various DNS configurations
> and diagnose them:
>
> https://www.grc.com/dns/benchmark.htm
>
> Use Wine to run it.
>
> wine DNSBench.exe
>
> It will tell you what's wrong, if anything, with your DNS configuration.
I have Windows XP running under VirtualBox on another machine;
I downloaded and ran DNSBench there. It was happy with my
network, and claimed that 192.168.0.1 was one of the fastest
DNS servers available.
On Wed Mar 24 13:10:44 2021 Greg Wooledge <greg@wooledge.org> wrote:
> Or, you could simply run
>
> dig @192.168.0.1 www.debian.org
>
> And see what happens. I bet it times out after about 30 seconds.
It came back instantly with
; <<>> DiG 9.11.5-P4-5.1+deb10u3-Debian <<>> @192.168.0.1 www.debian.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52104
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.debian.org. IN A
;; ANSWER SECTION:
www.debian.org. 218 IN A 149.20.4.15
www.debian.org. 218 IN A 128.31.0.62
;; Query time: 8 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Wed Mar 24 13:13:11 PDT 2021
;; MSG SIZE rcvd: 75
I tried again with the command "dig @192.168.0.1 news.newsguy.com",
since that's the news server it takes so long to connect to. After
a barely-discernible pause, it came back with
; <<>> DiG 9.11.5-P4-5.1+deb10u3-Debian <<>> @192.168.0.1 news.newsguy.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7019
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;news.newsguy.com. IN A
;; ANSWER SECTION:
news.newsguy.com. 3550 IN A 74.209.136.90
news.newsguy.com. 3550 IN A 74.209.136.91
news.newsguy.com. 3550 IN A 74.209.136.82
news.newsguy.com. 3550 IN A 74.209.136.88
news.newsguy.com. 3550 IN A 74.209.136.94
news.newsguy.com. 3550 IN A 74.209.136.95
news.newsguy.com. 3550 IN A 74.209.136.89
news.newsguy.com. 3550 IN A 74.209.136.92
;; Query time: 7 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Wed Mar 24 13:13:18 PDT 2021
;; MSG SIZE rcvd: 173
On Wed Mar 24 13:52:56 2021 David Christensen <dpchrist@holgerdanske.com>
wrote:
> Please run the following commands when your computer is connected to a
> given network:
$ cat /etc/debian_version
10.8
$ uname -a
Linux cjglap2 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30)
x86_64 GNU/Linux
$ nmcli g status
STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN
connected full enabled enabled enabled enabled
$ nmcli c show
NAME UUID TYPE
DEVICE
mundie 6 f877f569-e0a2-4ff8-96d5-a1e9d39f41ce wifi
wlp3s0
Wired connection 1 3a662505-1ba3-4d66-9407-477a0eb47a8f ethernet
enp0s25
(plus 14 lines for wifi connections I've had in the past) --
$ nmcli d show
GENERAL.DEVICE: enp0s25
GENERAL.TYPE: ethernet
GENERAL.HWADDR: 5C:FF:35:07:33:D2
GENERAL.MTU: 1500
GENERAL.STATE: 100 (connected)
GENERAL.CONNECTION: Wired connection 1
GENERAL.CON-PATH:
/org/freedesktop/NetworkManager/ActiveConnection/152
WIRED-PROPERTIES.CARRIER: on
IP4.ADDRESS[1]: 192.168.0.33/24
IP4.GATEWAY: 192.168.0.1
IP4.ROUTE[1]: dst = 0.0.0.0/0, nh =
192.168.0.1, mt = 100
IP4.ROUTE[2]: dst = 192.168.0.0/24, nh =
0.0.0.0, mt = 100
IP4.ROUTE[3]: dst = 169.254.0.0/16, nh =
0.0.0.0, mt = 1000
IP4.DNS[1]: 192.168.0.1
IP4.DNS[2]: 75.153.171.122
IP4.DOMAIN[1]: telus
IP6.ADDRESS[1]:
2001:569:74d8:9900:b476:fd78:f387:922c/64
IP6.ADDRESS[2]:
2001:569:74d8:9900:5eff:35ff:fe07:33d2/64
IP6.ADDRESS[3]: fe80::5eff:35ff:fe07:33d2/64
IP6.GATEWAY: fe80::1278:5bff:fec8:34d0
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 100
IP6.ROUTE[2]: dst = 2001:569:74d8:9900::/64,
nh = ::, mt = 100
IP6.ROUTE[3]: dst = ::/0, nh =
fe80::1278:5bff:fec8:34d0, mt = 100
IP6.DNS[1]: 2001:568:ff09:10a::56
IP6.DNS[2]: 2001:568:ff09:10b::122
GENERAL.DEVICE: wlp3s0
GENERAL.TYPE: wifi
GENERAL.HWADDR: 18:3D:A2:A6:56:14
GENERAL.MTU: 1500
GENERAL.STATE: 100 (connected)
GENERAL.CONNECTION: mundie 6
GENERAL.CON-PATH:
/org/freedesktop/NetworkManager/ActiveConnection/153
IP4.ADDRESS[1]: 192.168.0.44/24
IP4.GATEWAY: 192.168.0.1
IP4.ROUTE[1]: dst = 0.0.0.0/0, nh =
192.168.0.1, mt = 600
IP4.ROUTE[2]: dst = 192.168.0.0/24, nh =
0.0.0.0, mt = 600
IP4.DNS[1]: 192.168.0.1
IP4.DNS[2]: 75.153.171.122
IP4.DOMAIN[1]: telus
IP6.ADDRESS[1]:
2001:569:74d8:9900:f953:7d51:de1c:b63d/64
IP6.ADDRESS[2]: fe80::fb30:bc15:abf9:1f48/64
IP6.GATEWAY: fe80::1278:5bff:fec8:34d0
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 600
IP6.ROUTE[2]: dst = 2001:569:74d8:9900::/64,
nh = ::, mt = 600
IP6.ROUTE[3]: dst = ::/0, nh =
fe80::1278:5bff:fec8:34d0, mt = 600
IP6.DNS[1]: 2001:568:ff09:10a::56
IP6.DNS[2]: 2001:568:ff09:10b::122
GENERAL.DEVICE: lo
GENERAL.TYPE: loopback
GENERAL.HWADDR: 00:00:00:00:00:00
GENERAL.MTU: 65536
GENERAL.STATE: 10 (unmanaged)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
IP4.ADDRESS[1]: 127.0.0.1/8
IP4.GATEWAY: --
IP6.ADDRESS[1]: ::1/128
IP6.GATEWAY: --
IP6.ROUTE[1]: dst = ::1/128, nh = ::, mt = 256
GENERAL.DEVICE: gpd0
GENERAL.TYPE: tun
GENERAL.HWADDR: (unknown)
GENERAL.MTU: 1500
GENERAL.STATE: 10 (unmanaged)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
IP4.GATEWAY: --
IP6.GATEWAY: --
$ time host -v -t A www.debian.org 208.67.222.222
Trying "www.debian.org"
Using domain server:
Name: 208.67.222.222
Address: 208.67.222.222#53
Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21468
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.debian.org. IN A
;; ANSWER SECTION:
www.debian.org. 300 IN A 128.31.0.62
www.debian.org. 300 IN A 149.20.4.15
Received 64 bytes from 208.67.222.222#53 in 584 ms
real 0m0.609s
user 0m0.021s
sys 0m0.012s
$ time host -v -t A news.newsguy.com 208.67.222.222
Trying "news.newsguy.com"
Using domain server:
Name: 208.67.222.222
Address: 208.67.222.222#53
Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35638
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;news.newsguy.com. IN A
;; ANSWER SECTION:
news.newsguy.com. 3600 IN A 74.209.136.82
news.newsguy.com. 3600 IN A 74.209.136.88
news.newsguy.com. 3600 IN A 74.209.136.89
news.newsguy.com. 3600 IN A 74.209.136.90
news.newsguy.com. 3600 IN A 74.209.136.91
news.newsguy.com. 3600 IN A 74.209.136.92
news.newsguy.com. 3600 IN A 74.209.136.94
news.newsguy.com. 3600 IN A 74.209.136.95
Received 162 bytes from 208.67.222.222#53 in 118 ms
real 0m0.139s
user 0m0.009s
sys 0m0.013s
$ nmcli d show | perl -ae 'print $F[1],"\n" if $F[0] =~
/IP\d\.DNS\[\d+\]/' | xargs -n 1 host -v -t A www.debian.org
Trying "www.debian.org"
Using domain server:
Name: 192.168.0.1
Address: 192.168.0.1#53
Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56105
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.debian.org. IN A
;; ANSWER SECTION:
www.debian.org. 263 IN A 149.20.4.15
www.debian.org. 263 IN A 128.31.0.62
Received 64 bytes from 192.168.0.1#53 in 8 ms
Trying "www.debian.org"
Using domain server:
Name: 75.153.171.122
Address: 75.153.171.122#53
Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49283
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.debian.org. IN A
;; ANSWER SECTION:
www.debian.org. 263 IN A 128.31.0.62
www.debian.org. 263 IN A 149.20.4.15
Received 64 bytes from 75.153.171.122#53 in 8 ms
Trying "www.debian.org"
Using domain server:
Name: 2001:568:ff09:10a::56
Address: 2001:568:ff09:10a::56#53
Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19558
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.debian.org. IN A
;; ANSWER SECTION:
www.debian.org. 300 IN A 149.20.4.15
www.debian.org. 300 IN A 128.31.0.62
Received 64 bytes from 2001:568:ff09:10a::56#53 in 147 ms
Trying "www.debian.org"
Using domain server:
Name: 2001:568:ff09:10b::122
Address: 2001:568:ff09:10b::122#53
Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24974
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.debian.org. IN A
;; ANSWER SECTION:
www.debian.org. 263 IN A 149.20.4.15
www.debian.org. 263 IN A 128.31.0.62
Received 64 bytes from 2001:568:ff09:10b::122#53 in 7 ms
Trying "www.debian.org"
Using domain server:
Name: 192.168.0.1
Address: 192.168.0.1#53
Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7081
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.debian.org. IN A
;; ANSWER SECTION:
www.debian.org. 263 IN A 149.20.4.15
www.debian.org. 263 IN A 128.31.0.62
Received 64 bytes from 192.168.0.1#53 in 9 ms
Trying "www.debian.org"
Using domain server:
Name: 75.153.171.122
Address: 75.153.171.122#53
Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39449
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.debian.org. IN A
;; ANSWER SECTION:
www.debian.org. 263 IN A 128.31.0.62
www.debian.org. 263 IN A 149.20.4.15
Received 64 bytes from 75.153.171.122#53 in 8 ms
Trying "www.debian.org"
Using domain server:
Name: 2001:568:ff09:10a::56
Address: 2001:568:ff09:10a::56#53
Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52529
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.debian.org. IN A
;; ANSWER SECTION:
www.debian.org. 300 IN A 128.31.0.62
www.debian.org. 300 IN A 149.20.4.15
Received 64 bytes from 2001:568:ff09:10a::56#53 in 22 ms
Trying "www.debian.org"
Using domain server:
Name: 2001:568:ff09:10b::122
Address: 2001:568:ff09:10b::122#53
Aliases:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48596
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.debian.org. IN A
;; ANSWER SECTION:
www.debian.org. 263 IN A 149.20.4.15
www.debian.org. 263 IN A 128.31.0.62
Received 64 bytes from 2001:568:ff09:10b::122#53 in 7 ms
> The second to last command uses opendns.org's primary DNS server.
I threw in one with a call to news.newsguy.com as well,
since that's the server I'm having trouble connecting to.
> The last command uses whatever DNS servers Network Manager is
> currently using.
Thanks to all for your help.
--
cgibbs@surfnaked.ca (Charlie Gibbs)
Reply to: