Arch Linux

alexanders916

Member

Registered: 2017-05-30

Posts: 42

Every network command made in a console needs 5 seconds to start

If I enter one of the following commands it needs exactly 5 seconds to start the task after I hit enter:

ping -c3 google.com

pacman -Sy

wget google.com

The wget command is more verbose and looks like that (translated with google):

Resolving the host name google.com (google.com) ... 172.217.21.206, 2a00: 1450: 4001: 809 :: 200e
Connect to google.com (google.com) | 172.217.21.206 |: 80 ... connected.
HTTP request sent, response waiting ... 301 Moved Permanently
Place: http://www.google.com/ [following]
--2018-12-13 19: 20: 28-- http://www.google.com/
Resolving the host name www.google.com (www.google.com) ... 172.217.16.132, 2a00: 1450: 4001: 808 :: 2004
Connecting to www.google.com (www.google.com) | 172.217.16.132 |: 80 ... connected.
HTTP request sent, waiting for response ... 200 OK

It needs 5 seconds to print second line, so it looks like my machine has some problems with resolving the host name.
My router hasn't got any special settings.
It works without any problems on my laptop with Ubuntu.
It works without any problems on my machine with Windows.

Using fresh Arch Linux with Gnome.

Last edited by alexanders916 (2018-12-13 18:27:33)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,697

Re: Every network command made in a console needs 5 seconds to start

How do these behave?

LC_ALL=C dig google.com
LC_ALL=C dig @8.8.8.8 google.com

(Hint, see the LC_ALL=C export, please don't google translate output ;-)

If they're equally fast (no delay at all)

cat /etc/nsswitch.conf
ps aux | grep resolved

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc