Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: ERR_NAME_NOT_RESOLVED

  1. #1

    Default ERR_NAME_NOT_RESOLVED

    Hello All,

    Suddenly after a routine update my browser stopped working, the reported error is ERR_NAME_NOT_RESOLVED.

    If I try pinging a website by name, e.g. www.yahoo.com, I got an error message saying unknown name or service
    If I ping an IP address, e.g. 8.8.8.8 I get a reply

    Nslookup doesn't work neither for website names nor for IP addresses, in both cases says connection timed out, no servers could be reached.

    Apologies for not having a precise cut and paste of the outputs but at the moment I am writing from my mobile, which is connected to the same network by the way.

    Any pointers?

    Many thanks in advance

  2. #2
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,478
    Blog Entries
    14

    Default Re: ERR_NAME_NOT_RESOLVED

    And what if you close the browser, then revisite the URL ?
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  3. #3
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    10,640
    Blog Entries
    1

    Default Re: ERR_NAME_NOT_RESOLVED

    Your ping test suggests a system problem, not limited to the web browser.

    What kind of update happened?
    Did you try rebooting?
    You may not have to reboot, did you try restarting your network service with the following command?
    Code:
    systemctl restart network
    You didn't do a system upgrade from a prior version of openSUSE recently?

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  4. #4

    Default Re: ERR_NAME_NOT_RESOLVED

    It was one of the routine updates, that yes, required a restart, which I did.

    I also tried your suggestion, but it did not work.

    To add a possible useful detail, I can access the devices on my home network (NAS, router), nothing outside that. Could it be a DNS issue? My router has a default DNS that cannot be changed, but I'm unsure whether my computer actually used that.

  5. #5
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    19,883
    Blog Entries
    1

    Default Re: ERR_NAME_NOT_RESOLVED

    Quote Originally Posted by MadSplinter View Post
    My router has a default DNS that cannot be changed, but I'm unsure whether my computer actually used that.
    You can check your current DNS settings with
    Code:
    grep name /etc/resolv.conf
    If desired you can explicitly set it by directly editing this file directly, or preferably by modifying your NetworkManager connection with an explicit DNS server, or if using wicked (then you can configure via YaST).
    openSUSE Leap 15.0; KDE Plasma 5

  6. #6

    Default Re: ERR_NAME_NOT_RESOLVED

    The grep command gives back an empty string, so I tried to manually set them from network manager.

    I tried to use the Google DNS first, and my router after, but in both cases I still get the same error from the browser. Actually it looks the only thing I can do is ping website by their IP, not by their names, even connecting to repositories doesn't happen

  7. #7
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    19,883
    Blog Entries
    1

    Default Re: ERR_NAME_NOT_RESOLVED

    Quote Originally Posted by MadSplinter View Post
    The grep command gives back an empty string, so I tried to manually set them from network manager.
    Did you restart the connection for the changes to take effect?

    You can try the following directly
    Code:
    echo nameserver 8.8.8.8 | sudo tee /etc/resolv.conf
    which should then take effect immediately.
    openSUSE Leap 15.0; KDE Plasma 5

  8. #8

    Default Re: ERR_NAME_NOT_RESOLVED

    Yes, I did restart the connection after every single attempt, with the command I just learnt from one of the above replies, i.e. systemctl restart network

  9. #9

    Default Re: ERR_NAME_NOT_RESOLVED

    Any other suggestions? I'm still stuck outside internet...

  10. #10
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,729

    Default AW: ERR_NAME_NOT_RESOLVED

    Post:
    Code:
    cat /etc/resolv.conf
    Please post with the conplete command-line and use Code-Tags here in the forum.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •