Arch Linux

thelollies

Member

Registered: 2013-04-20

Posts: 21

Using pacman requires resolv.conf hack

Something is not quite right with my network config (very recent Arch install). Every time I want to use Pacman I have to

sudo vim /etc/resolv.conf

and add the line

options timeout:1

If I don't I get output of the like:

:: Synchronizing package databases...
error: failed retrieving file 'core.db' from mirror.aarnet.edu.au : Resolving timed out after 10520 milliseconds
error: failed retrieving file 'core.db' from archlinux.mirror.digitalpacific.com.au : Resolving timed out after 10520 milliseconds
error: failed retrieving file 'core.db' from ftp.iinet.net.au : Resolving timed out after 10520 milliseconds

I am using dhcpcd, the output of

sudo systemctl status dhcpd@enp7s0.service

is:

● dhcpcd@enp7s0.service - dhcpcd on enp7s0
   Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2015-04-15 08:24:25 NZST; 50min ago
  Process: 279 ExecStart=/usr/bin/dhcpcd -q -w %I (code=exited, status=0/SUCCESS)
 Main PID: 2958 (dhcpcd)
   CGroup: /system.slice/system-dhcpcd.slice/dhcpcd@enp7s0.service
           └─2958 /usr/bin/dhcpcd -q -w enp7s0

Apr 15 08:24:17 RoryDesktop dhcpcd[279]: DUID 00:01:00:01:1c:a6:7a:fe:1c:6f:65:d9:73:e6
Apr 15 08:24:17 RoryDesktop dhcpcd[279]: enp7s0: IAID 65:d9:73:e6
Apr 15 08:24:17 RoryDesktop dhcpcd[279]: enp7s0: soliciting an IPv6 router
Apr 15 08:24:18 RoryDesktop dhcpcd[279]: enp7s0: soliciting a DHCP lease
Apr 15 08:24:20 RoryDesktop dhcpcd[279]: enp7s0: offered 192.168.0.103 from 192.168.0.1
Apr 15 08:24:25 RoryDesktop dhcpcd[279]: enp7s0: leased 192.168.0.103 for 7200 seconds
Apr 15 08:24:25 RoryDesktop dhcpcd[279]: enp7s0: adding route to 192.168.0.0/24
Apr 15 08:24:25 RoryDesktop dhcpcd[279]: enp7s0: adding default route via 192.168.0.1
Apr 15 08:24:25 RoryDesktop systemd[1]: Started dhcpcd on enp7s0.
Apr 15 08:24:31 RoryDesktop dhcpcd[2958]: enp7s0: no IPv6 Routers available

An ideas what's going on here?

Head_on_a_Stick

Member

From: London

Registered: 2014-02-20

Posts: 7,748

Website

Re: Using pacman requires resolv.conf hack

Post your /etc/resolv.conf plz

---

Are you infected with Wetiko?

thelollies

Member

Registered: 2013-04-20

Posts: 21

Re: Using pacman requires resolv.conf hack

# Generated by resolvconf
nameserver 192.168.0.1
options timeout:1

With the second line being my addition.

headkase

Member

Registered: 2011-12-06

Posts: 1,977

Re: Using pacman requires resolv.conf hack

If the DNS on your router isn't working correctly you can always point to an Open DNS like Google DNS.

nameserver 8.8.8.8
nameserver 8.8.4.4

And if you want to preserve those changes between reboots:

sudo chattr +i /etc/resolv.conf

Which makes the file immutable, "-i" to make it normal again.

Any resolv.conf changes you make take effect immediately.

thelollies

Member

Registered: 2013-04-20

Posts: 21

Re: Using pacman requires resolv.conf hack

I just gave that a go and it worked, thank you. Is there any point having dhcpcd running now or should I disable it?

headkase

Member

Registered: 2011-12-06

Posts: 1,977

Re: Using pacman requires resolv.conf hack

Well, if you are getting your IP address from your router then you do need to keep dhcpcd running.  The original nameserver, 192.168.0.1, is within the subnet class C - a range reserved for your home network usually - and that specific address is typically where your router sits.  With your nameserver pointing at that then the router would be responsible for resolving the name to IP address requests.  It either doesn't do that or is not configured correctly to do so.  Your router, not your computer.  If you have a static IP, and you'll know it because you set it up, then you don't need dhcpcd.  You can configure your router to use static IPs if you like and then also configure your Arch machine with a static IP.

Using Google DNS is a patch for the issue, the real solution would be to find out why your router is not passing along the correct nameservers when you get your dhcp lease.  However, if the patch works for you then it's your choice whether or not to investigate further.