ionmich
November 14, 2019, 3:14am
1
After an upgrade from Leapn 15.0 to 15.1 I can ping successfully but cannot connect to any sites via browsers.
:~> ping 208.67.222.222PING 208.67.222.222 (208.67.222.222) 56(84) bytes of data.
64 bytes from 208.67.222.222: icmp_seq=1 ttl=50 time=49.4 ms
64 bytes from 208.67.222.222: icmp_seq=2 ttl=50 time=39.5 ms
64 bytes from 208.67.222.222: icmp_seq=3 ttl=50 time=44.5 ms
^C
--- 208.67.222.222 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 39.553/44.490/49.415/4.026 ms
:~> grep "nameserver" /etc/resolv.conf
nameserver 208.67.222.222
nameserver 208.67.220.220
nameserver 8.8.8.8
:~> ping www.google.com
ping: www.google.com: Name or service not known
Settings in YaST are the same as the machine running 15.1 next to it. Where do I start to diagnose the problem?
ionmich:
After an upgrade from Leapn 15.0 to 15.1 I can ping successfully but cannot connect to any sites via browsers.
:~> ping 208.67.222.222PING 208.67.222.222 (208.67.222.222) 56(84) bytes of data.
64 bytes from 208.67.222.222: icmp_seq=1 ttl=50 time=49.4 ms
64 bytes from 208.67.222.222: icmp_seq=2 ttl=50 time=39.5 ms
64 bytes from 208.67.222.222: icmp_seq=3 ttl=50 time=44.5 ms
^C
--- 208.67.222.222 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 39.553/44.490/49.415/4.026 ms
:~> grep "nameserver" /etc/resolv.conf
nameserver 208.67.222.222
nameserver 208.67.220.220
nameserver 8.8.8.8
:~> ping www.google.com
ping: www.google.com: Name or service not known
Settings in YaST are the same as the machine running 15.1 next to it. Where do I start to diagnose the problem?
Hi
Have you run the following command as root user?
netconfig update -f
ionmich
November 14, 2019, 3:22am
3
Sorry I forgot to mention. Using Wicked.
ionmich
November 14, 2019, 3:29am
4
Yes and I rebooted with no effect.
Hi
What about the dig command?
dig www.google.com
dig @8.8.8.8 www.google.com
If not, go into YaST Network Settings and delete the entries, save, go back in and re-add and see how that goes with the above commands.
ionmich
November 14, 2019, 3:42am
6
Switching to Network Manager does not change anything. There is also no firewall activated.
ionmich
November 14, 2019, 3:50am
7
malcolmlewis:
Hi
What about the dig command?
dig www.google.com
dig @8.8.8.8 www.google.com
If not, go into YaST Network Settings and delete the entries, save, go back in and re-add and see how that goes with the above commands.
:~> dig 8.8.8.8
; <<>> DiG 9.11.2 <<>> 8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 41048
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;8.8.8.8. IN A
;; AUTHORITY SECTION:
. 3600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019111301 1800 900 604800 86400
;; Query time: 46 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Wed Nov 13 20:43:50 CST 2019
;; MSG SIZE rcvd: 111
ion@linux-dqd8:~> dig @8.8.8.8 www.google.com
; <<>> DiG 9.11.2 <<>> @8.8.8.8 www.google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32750
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.google.com. IN A
;; ANSWER SECTION:
www.google.com. 142 IN A 172.217.9.164
;; Query time: 48 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Nov 13 20:44:30 CST 2019
;; MSG SIZE rcvd: 59
ion@linux-dqd8:~>
ionmich:
:~> dig 8.8.8.8
; <<>> DiG 9.11.2 <<>> 8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 41048
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;8.8.8.8. IN A
;; AUTHORITY SECTION:
. 3600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019111301 1800 900 604800 86400
;; Query time: 46 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Wed Nov 13 20:43:50 CST 2019
;; MSG SIZE rcvd: 111
ion@linux-dqd8:~> dig @8.8.8.8 www.google.com
; <<>> DiG 9.11.2 <<>> @8.8.8.8 www.google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32750
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.google.com. IN A
;; ANSWER SECTION:
www.google.com. 142 IN A 172.217.9.164
;; Query time: 48 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Nov 13 20:44:30 CST 2019
;; MSG SIZE rcvd: 59
ion@linux-dqd8:~>
Hi
And without the dns reference;
dig www.google.com
ionmich
November 14, 2019, 4:11am
10
:~> dig www.google.com
; <<>> DiG 9.11.2 <<>> www.google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34688
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.google.com. IN A
;; ANSWER SECTION:
www.google.com. 300 IN A 172.217.9.132
;; Query time: 52 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Wed Nov 13 21:06:50 CST 2019
;; MSG SIZE rcvd: 59
ionmich:
:~> dig www.google.com
; <<>> DiG 9.11.2 <<>> www.google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34688
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.google.com. IN A
;; ANSWER SECTION:
www.google.com. 300 IN A 172.217.9.132
;; Query time: 52 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Wed Nov 13 21:06:50 CST 2019
;; MSG SIZE rcvd: 59
Hi
So that’s working…
What about;
dig forums.opensuse.org
ping forums.opensuse.org
ionmich
November 14, 2019, 4:33am
12
:~> dig forums.opensuse.org
; <<>> DiG 9.11.2 <<>> forums.opensuse.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8759
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;forums.opensuse.org. IN A
;; ANSWER SECTION:
forums.opensuse.org. 300 IN A 130.57.66.6
;; Query time: 95 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Wed Nov 13 21:29:14 CST 2019
;; MSG SIZE rcvd: 64
ion@linux-dqd8:~> ping forums.opensuse.org
ping: forums.opensuse.org: Name or service not known
ion@linux-dqd8:~>
ionmich:
:~> dig forums.opensuse.org
; <<>> DiG 9.11.2 <<>> forums.opensuse.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8759
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;forums.opensuse.org. IN A
;; ANSWER SECTION:
forums.opensuse.org. 300 IN A 130.57.66.6
;; Query time: 95 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Wed Nov 13 21:29:14 CST 2019
;; MSG SIZE rcvd: 64
ion@linux-dqd8:~> ping forums.opensuse.org
ping: forums.opensuse.org: Name or service not known
ion@linux-dqd8:~>
Hi
Can you switch to root user and try the ping, or create a test user and try.
ionmich
November 14, 2019, 4:41am
14
Pinged as root. No difference.
Hi
Added any firewall rules, can you switch off temporarily and see if that helps.
systemctl stop firewalld
ionmich
November 14, 2019, 4:58am
16
firewalld.service is not loaded.
tsu2
November 14, 2019, 4:59am
17
Solution should be simple.
The nameservers starting with 208 likely are run by your ISP, and they aren’t performing.
Solution:
Remove those nameservers, leaving the Google nameserver (8.8.8.8) as your only listed nameserver.
When configuring nameservers, best practice is to list only one highly reliable and performing nameserver.
A second might be listed, but typically it wouldn’t be used unless queries using the first times out which would mean a really slow experience.
A third or more can be listed but since it would not be used until <both> the first and then the second times out, you probably won’t still be waiting for name resolution after minutes of waiting… So these are probably useless.
HTH,
TSU
ionmich
November 14, 2019, 5:02am
18
tsu2:
Solution should be simple.
Solution:
Remove those nameservers, leaving the Google nameserver (8.8.8.8) as your only listed nameserver.
HTH,
TSU
I tried that a few posts ago leaving only 8.8.8.8. Nothing changed.
tsu2:
Solution should be simple.
The nameservers starting with 208 likely are run by your ISP, and they aren’t performing.
Solution:
Remove those nameservers, leaving the Google nameserver (8.8.8.8) as your only listed nameserver.
When configuring nameservers, best practice is to list only one highly reliable and performing nameserver.
A second might be listed, but typically it wouldn’t be used unless queries using the first times out which would mean a really slow experience.
A third or more can be listed but since it would not be used until <both> the first and then the second times out, you probably won’t still be waiting for name resolution after minutes of waiting… So these are probably useless.
HTH,
TSU
Hi
They are openDNS servers and functional and super reliable, my local DNS servers use them (well the parental versions ending in 123)…
Same here, so I’m not sure about that advice.