Ubuntu 18.04 LTS upgrade to 18.10: how to fix site not reachable in browser but ping and dig works?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












Yesterday I updated Ubuntu from 18.04 LTS to 18.10, all is working fine, but I'm having some problems with networking stuff. Maybe DNS.



ping my-website-.com


is working fine, as well as



dig my-website-.com


And I can connect to the website by its IP from my cell, on the same network (both Wi-Fi) of the PC.
However I'm not able to connect to it via browser (Chrome & Firefox).



How can I fix this, since while on Ubunut 18.04 it was working fine?



UPDATE



This is my /etc/resolv.conf:



$ cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53


This is the output of systemd-resolve --status



Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

Link 7 (br-d5068a395ed0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 6 (br-93c587738553)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 5 (br-696c2c38ba83)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 4 (docker0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 3 (wlp2s0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.43.228
DNS Servers: 192.168.43.228
DNS Domain: ~.

Link 2 (enp1s0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no


Update 2
I set the fallbackDNS and restarted network-manager but still not working.



root@1z10:/home/izio# cat /etc/systemd/resolved.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See resolved.conf(5) for details

[Resolve]
#DNS=
FallbackDNS=8.8.8.8,8.8.4.4
#Domains=
#LLMNR=no
#MulticastDNS=no
#DNSSEC=no
#DNSOverTLS=no
#Cache=yes
#DNSStubListener=yes









share|improve this question























  • 1. Why did you upgrade from 18.04 LTS to 18.10? 2. Have you got a current backup of the 18.04 LTS system?
    – sudodus
    15 hours ago










  • I was having troubles with wifi turning off after a while. Now it doesn't. Unlickely, I don't.
    – 1Z10
    14 hours ago










  • @sudodus I updated my question with the cat of /etc/resolv.conf, do you know why it uses a local IP as DNS nameserver?
    – 1Z10
    13 hours ago










  • $ ls -al /etc/resolv.conf lrwxrwxrwx 1 root root 29 nov 12 18:59 /etc/resolv.conf -> ../run/resolvconf/resolv.conf
    – 1Z10
    13 hours ago











  • sudo systemctl restart systemd-resolved
    – GAD3R
    13 hours ago














up vote
0
down vote

favorite












Yesterday I updated Ubuntu from 18.04 LTS to 18.10, all is working fine, but I'm having some problems with networking stuff. Maybe DNS.



ping my-website-.com


is working fine, as well as



dig my-website-.com


And I can connect to the website by its IP from my cell, on the same network (both Wi-Fi) of the PC.
However I'm not able to connect to it via browser (Chrome & Firefox).



How can I fix this, since while on Ubunut 18.04 it was working fine?



UPDATE



This is my /etc/resolv.conf:



$ cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53


This is the output of systemd-resolve --status



Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

Link 7 (br-d5068a395ed0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 6 (br-93c587738553)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 5 (br-696c2c38ba83)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 4 (docker0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 3 (wlp2s0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.43.228
DNS Servers: 192.168.43.228
DNS Domain: ~.

Link 2 (enp1s0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no


Update 2
I set the fallbackDNS and restarted network-manager but still not working.



root@1z10:/home/izio# cat /etc/systemd/resolved.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See resolved.conf(5) for details

[Resolve]
#DNS=
FallbackDNS=8.8.8.8,8.8.4.4
#Domains=
#LLMNR=no
#MulticastDNS=no
#DNSSEC=no
#DNSOverTLS=no
#Cache=yes
#DNSStubListener=yes









share|improve this question























  • 1. Why did you upgrade from 18.04 LTS to 18.10? 2. Have you got a current backup of the 18.04 LTS system?
    – sudodus
    15 hours ago










  • I was having troubles with wifi turning off after a while. Now it doesn't. Unlickely, I don't.
    – 1Z10
    14 hours ago










  • @sudodus I updated my question with the cat of /etc/resolv.conf, do you know why it uses a local IP as DNS nameserver?
    – 1Z10
    13 hours ago










  • $ ls -al /etc/resolv.conf lrwxrwxrwx 1 root root 29 nov 12 18:59 /etc/resolv.conf -> ../run/resolvconf/resolv.conf
    – 1Z10
    13 hours ago











  • sudo systemctl restart systemd-resolved
    – GAD3R
    13 hours ago












up vote
0
down vote

favorite









up vote
0
down vote

favorite











Yesterday I updated Ubuntu from 18.04 LTS to 18.10, all is working fine, but I'm having some problems with networking stuff. Maybe DNS.



ping my-website-.com


is working fine, as well as



dig my-website-.com


And I can connect to the website by its IP from my cell, on the same network (both Wi-Fi) of the PC.
However I'm not able to connect to it via browser (Chrome & Firefox).



How can I fix this, since while on Ubunut 18.04 it was working fine?



UPDATE



This is my /etc/resolv.conf:



$ cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53


This is the output of systemd-resolve --status



Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

Link 7 (br-d5068a395ed0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 6 (br-93c587738553)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 5 (br-696c2c38ba83)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 4 (docker0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 3 (wlp2s0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.43.228
DNS Servers: 192.168.43.228
DNS Domain: ~.

Link 2 (enp1s0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no


Update 2
I set the fallbackDNS and restarted network-manager but still not working.



root@1z10:/home/izio# cat /etc/systemd/resolved.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See resolved.conf(5) for details

[Resolve]
#DNS=
FallbackDNS=8.8.8.8,8.8.4.4
#Domains=
#LLMNR=no
#MulticastDNS=no
#DNSSEC=no
#DNSOverTLS=no
#Cache=yes
#DNSStubListener=yes









share|improve this question















Yesterday I updated Ubuntu from 18.04 LTS to 18.10, all is working fine, but I'm having some problems with networking stuff. Maybe DNS.



ping my-website-.com


is working fine, as well as



dig my-website-.com


And I can connect to the website by its IP from my cell, on the same network (both Wi-Fi) of the PC.
However I'm not able to connect to it via browser (Chrome & Firefox).



How can I fix this, since while on Ubunut 18.04 it was working fine?



UPDATE



This is my /etc/resolv.conf:



$ cat /etc/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53


This is the output of systemd-resolve --status



Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

Link 7 (br-d5068a395ed0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 6 (br-93c587738553)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 5 (br-696c2c38ba83)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 4 (docker0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no

Link 3 (wlp2s0)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 192.168.43.228
DNS Servers: 192.168.43.228
DNS Domain: ~.

Link 2 (enp1s0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no


Update 2
I set the fallbackDNS and restarted network-manager but still not working.



root@1z10:/home/izio# cat /etc/systemd/resolved.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See resolved.conf(5) for details

[Resolve]
#DNS=
FallbackDNS=8.8.8.8,8.8.4.4
#Domains=
#LLMNR=no
#MulticastDNS=no
#DNSSEC=no
#DNSOverTLS=no
#Cache=yes
#DNSStubListener=yes






ubuntu networking dns






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 13 hours ago

























asked 15 hours ago









1Z10

417




417











  • 1. Why did you upgrade from 18.04 LTS to 18.10? 2. Have you got a current backup of the 18.04 LTS system?
    – sudodus
    15 hours ago










  • I was having troubles with wifi turning off after a while. Now it doesn't. Unlickely, I don't.
    – 1Z10
    14 hours ago










  • @sudodus I updated my question with the cat of /etc/resolv.conf, do you know why it uses a local IP as DNS nameserver?
    – 1Z10
    13 hours ago










  • $ ls -al /etc/resolv.conf lrwxrwxrwx 1 root root 29 nov 12 18:59 /etc/resolv.conf -> ../run/resolvconf/resolv.conf
    – 1Z10
    13 hours ago











  • sudo systemctl restart systemd-resolved
    – GAD3R
    13 hours ago
















  • 1. Why did you upgrade from 18.04 LTS to 18.10? 2. Have you got a current backup of the 18.04 LTS system?
    – sudodus
    15 hours ago










  • I was having troubles with wifi turning off after a while. Now it doesn't. Unlickely, I don't.
    – 1Z10
    14 hours ago










  • @sudodus I updated my question with the cat of /etc/resolv.conf, do you know why it uses a local IP as DNS nameserver?
    – 1Z10
    13 hours ago










  • $ ls -al /etc/resolv.conf lrwxrwxrwx 1 root root 29 nov 12 18:59 /etc/resolv.conf -> ../run/resolvconf/resolv.conf
    – 1Z10
    13 hours ago











  • sudo systemctl restart systemd-resolved
    – GAD3R
    13 hours ago















1. Why did you upgrade from 18.04 LTS to 18.10? 2. Have you got a current backup of the 18.04 LTS system?
– sudodus
15 hours ago




1. Why did you upgrade from 18.04 LTS to 18.10? 2. Have you got a current backup of the 18.04 LTS system?
– sudodus
15 hours ago












I was having troubles with wifi turning off after a while. Now it doesn't. Unlickely, I don't.
– 1Z10
14 hours ago




I was having troubles with wifi turning off after a while. Now it doesn't. Unlickely, I don't.
– 1Z10
14 hours ago












@sudodus I updated my question with the cat of /etc/resolv.conf, do you know why it uses a local IP as DNS nameserver?
– 1Z10
13 hours ago




@sudodus I updated my question with the cat of /etc/resolv.conf, do you know why it uses a local IP as DNS nameserver?
– 1Z10
13 hours ago












$ ls -al /etc/resolv.conf lrwxrwxrwx 1 root root 29 nov 12 18:59 /etc/resolv.conf -> ../run/resolvconf/resolv.conf
– 1Z10
13 hours ago





$ ls -al /etc/resolv.conf lrwxrwxrwx 1 root root 29 nov 12 18:59 /etc/resolv.conf -> ../run/resolvconf/resolv.conf
– 1Z10
13 hours ago













sudo systemctl restart systemd-resolved
– GAD3R
13 hours ago




sudo systemctl restart systemd-resolved
– GAD3R
13 hours ago















active

oldest

votes











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f481289%2fubuntu-18-04-lts-upgrade-to-18-10-how-to-fix-site-not-reachable-in-browser-but%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f481289%2fubuntu-18-04-lts-upgrade-to-18-10-how-to-fix-site-not-reachable-in-browser-but%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?