You are not logged in.

#1 2022-04-12 00:49:40

dead101
Member
Registered: 2021-12-07
Posts: 21

Temporary failure in name resolution

I was using the internet via wifi peacefully yesterday and suddenly after I open the google it didn't work. Then I ping google.com and got this.

ping: google.com: Temporary failure in name resolution

Then I restarted NetworkManager and did all the various things that I know, still doesn't work.

However after I did `sudo dhcpcd` it worked.

~   ❯ sudo dhcpcd                                                                                                                                             06:10:27
[sudo] password for dead: 
dhcpcd-9.4.1 starting
dev: loaded udev
DUID 00:04:00:02:00:03:00:04:00:05:00:06:00:07:00:08:00:09
wlan0: connected to Access Point: DAMNIT
enp2s0: waiting for carrier
wlan0: IAID 2d:20:6a:c8
ipv6leakintrf0: IAID d6:9d:cf:52
wlan0: soliciting an IPv6 router
ipv6leakintrf0: soliciting an IPv6 router
wlan0: rebinding lease of 192.168.1.100
wlan0: probing address 192.168.1.100/24
ipv6leakintrf0: soliciting a DHCP lease
wlan0: leased 192.168.1.100 for 259200 seconds
wlan0: adding route to 192.168.1.0/24
wlan0: adding default route via 192.168.1.1
forked to background, child pid 82

But this is only for that session. I mean after I reboot everything goes and again there's the same issue.

This is what my `resolv.conf` looks like
when there's the error; nameserver ::1
after the dhcpcd; nameserver 208.67.222.222
nameserver 208.67.220.220

Please give a solutions for this error as I can't use the internet properly?

Offline

#2 2022-04-12 00:53:53

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,441
Website

Re: Temporary failure in name resolution

What networking services are you using, and which ones do you intend to use?  What's the output of `find /etc/systemd/ -name '*.service'`


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#3 2022-04-12 01:00:51

dead101
Member
Registered: 2021-12-07
Posts: 21

Re: Temporary failure in name resolution

Sorry to bother you guys! I did know that there's something wrong with the DHCP client. I looked into the dhcpcd.service and saw that It was disabled and inactive. Then I just enable it and reboot, and now for the heaven's sake it works. Btw thank you guys!

Offline

#4 2022-04-12 01:36:55

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,409

Re: Temporary failure in name resolution

That doesn't sound like a fix. Please post the output asked for. You should not mix NetworkManager and dhcpcd.

Offline

#5 2022-04-12 06:22:19

seth
Member
Registered: 2012-09-03
Posts: 49,946

Re: Temporary failure in name resolution

"nameserver ::1" is the IPv6 localhost, likely set by resolved - the absence of an IPv4 resolver suggests that you might not have a lease when resolved strolls along and the pure IPv4 servers added by openresolv suggest that you probably don't have IPv6 coverage.
=> You didn't fix the situation *at all*, but introduced one more problem (conflicting network managers)

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
sudo journalctl -b | curl -F 'file=@-' 0x0.st

Online

Board footer

Powered by FluxBB