Jump to content
  • 0

Still can't log in - "DNS could not resolve the host name"


You are about to reply to a thread that has been inactive for 1685 days.

Please take a moment to consider if this thread is worth bumping.

Question

  • 0

From the KB article about that message ( http://community.secondlife.com/t5/English-Knowledge-Base/Login-failure/ta-p/700109#Section_.1.3a ):

DNS could not resolve the host name

This error may also appear as:

  • Host http not found 
  • Login failed. Unable to connect to a simulator.

These messages indicate that your computer has a general networking issue with the domain name service (DNS) that translates numerical IP addresses into human-readable ones.  

Confirm that you can reach internet sites such as secondlife.com, Google, or others.  Once your computer can connect to these websites, this error should no longer occur.  

Also check whether there is a wider issue with Seond Life, as described below.

Usually, restarting your computer and your router will resolve this issue.   If not, contact your internet service provider.  You may also wish to try using Google's DNS servers to see if that will resolve the issue.  See Using Google Public DNS for more information.

  • Like 1
Link to post
Share on other sites

5 answers to this question

Recommended Posts

  • 0

From the KB article about that message ( http://community.secondlife.com/t5/English-Knowledge-Base/Login-failure/ta-p/700109#Section_.1.3a ):

DNS could not resolve the host name

This error may also appear as:

  • Host http not found 
  • Login failed. Unable to connect to a simulator.

These messages indicate that your computer has a general networking issue with the domain name service (DNS) that translates numerical IP addresses into human-readable ones.  

Confirm that you can reach internet sites such as secondlife.com, Google, or others.  Once your computer can connect to these websites, this error should no longer occur.  

Also check whether there is a wider issue with Seond Life, as described below.

Usually, restarting your computer and your router will resolve this issue.   If not, contact your internet service provider.  You may also wish to try using Google's DNS servers to see if that will resolve the issue.  See Using Google Public DNS for more information.

  • Like 1
Link to post
Share on other sites
  • 0

That means the sim you are trying to log into is in severe need of a restart.
Log into a silent region such as Smith.
If the sim you can't log into is a private estate sim, contact the sim owner and request a restart, if the sim is on mainland, file a support ticket requesting a restart.

 

Link to post
Share on other sites
  • 0

Your viewer and SL's servers have temporarily lost the ability to talk to each other because there are squirrels on the line. Unless there's a problem with the servers (Always check http://status.secondlifegrid.net/ first), it's probably something on your end. So....

(1) Try shutting off your computer, unplugging the router and modem for a couple of minutes, and then plugging them back in and restarting. That simple step may clear up everything

(2) Add Google's free public DNS servers to whatever your ISP assigns you as a default. Here's how >>> http://code.google.com/speed/public-dns/

(3) If things are STILL messed up, contact your ISP. Maybe they are working on their Internet connections. Mine go down for about 20 minutes once a month or so while they are vacuuming dust out of their servers, or whatever they do.

 

Link to post
Share on other sites
  • 0

I have had this issue for years with no resolution that worked, I use Vista. My sister gave me her old laptop with Windows XP professional on it, I put the same security software provided by my ISP on it as my main, logged into the same network/ router, it ran it fine, my main with Vista "DNS cannot resolve host name". I believe now it is a SL viewer software issue and has nothing to do with DNS at all. Much like the problem with MAC OS sometime back that got a patch. Thing is this needs a patch witch I don't see coming out.

After talking to a bunch of people they all said to them it has to be a software issue on their end not a DNS/ISP issue since it  ran one version and broke again on an update, now I am pretty sure they were right.

Link to post
Share on other sites
You are about to reply to a thread that has been inactive for 1685 days.

Please take a moment to consider if this thread is worth bumping.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...