You are not logged in.
- Topics: Active | Unanswered
#1 2007-08-01 05:19:42
- occam
- Member
- From: Melbourne, Australia
- Registered: 2005-01-16
- Posts: 82
Yet another "Transient resolver failure" situation
I have read the threads in the forums that deal with this problem - none applies to my situation.
I installed the base system (Duke) only, as recommended; edited confifuration files and tried an pacman -Suy
The response was the repetition of messages of file inaccessabilty and "Transient resolver failure", both for my 'handwritten' servers and for servers I had just uncommented in the pacman.d/* files.
I can ping local hosts, so my ethernet interface is ok and running.
The output of route is (says my handwritten notes):
Destination Gateway Genmask Flags Metric Ref Use Iface
localnet * 255.255.255.0 U 0 0 0 eth0
default Urd.Asgard 0.0.0.0 UG 0 0 0 eth0
which is almost identical to my Slackware 12 output:
Destination Gateway Genmask Flags Metric Ref Use Iface
localnet * 255.255.255.0 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default Urd.Asgard 0.0.0.0 UG 1 0 0 eth0
(Urd.Asgard is my ADSL modem/router)
Ping does not work over the ADSL link (firewalled at ISP?), and python is not yet installed - so I see no easy way of further testing of internet access etc.
One solution is of course to do a 'full' install (with re-editing of the configuration files) and see if I can find more clues.
The other solution is to write this post and hope someone can help me.
Meanwhile I am running Slackware and having to do without some nice software.. but why build from source when Arch gives me ready-made packages?
Moduli non sunt multiplicandi praeter necessitatem
Offline
#2 2007-08-01 13:26:33
- abhidg
- Member
- From: City of Kol
- Registered: 2006-07-01
- Posts: 184
- Website
Re: Yet another "Transient resolver failure" situation
have you given the DNS in /etc/resolv.conf? Sometimes, it does not automatically pick up from the router.
Offline