Friday, May 20, 2011

Unable to connect to Second Life. DNS could not resolve the host name.

Unable to connect to Second Life.
DNS could not resolve the host name.
Please verify that you can connect to
web site. If you can, but continue to receive this error,
please go to the support section and and report this problem.
Are you seeing this error? Well, the good news is there's nothing wrong with the viewer you downloaded. The bad news is that the Domain Name Service (DNS) you use can't figure out the internet address of some URL inside the viewer that it's trying to access.

LL has a wiki page on it here that is marginally helpful.

Anubis Vlad Tepas left a comment on my 2.6.1 posting that is very helpful. It's sort of buried now, so I wanted to bring it back up to the forefront.

Anubis Vlad Tepas said...

For those who have DNS errors, there's a solution that worked (for me, at least).

Go the System Preference -> Network -> Airport (if you're using Airport, otherwise I guess it should be the same with Ethernet) -> DNS.
There, add two adresses :
I have no idea why this new version of SL messes with DNS servers. And I don't like playing with these settings. But oh well, it's likely to be temporary only.

Hope it works for you as well.

On Linux, you'd add these to your /etc/resolv.conf file like this. The part with the # is just a comment, don't include it.

sudo cp /etc/resolv.conf /etc/resolve.conf.pre-kittin # Make sure you back it up first!
sudo echo "nameserver" >> /etc/resolv.conf # Add the first DNS
sudo echo "nameserver" >> /etc/resolv.conf # Add the second DNS


  1. Back when viewer 2 first came out I had this issue, I wound up switching to Emerald. Later I tried viewer 2 again, same thing I then downloaded the then Snowglobe version that used viewer 2 in it voila that worked. That showed me it was an SL issue. I finally found a version that worked, well up to version 2.5, I am now back to the same error. Nothing worked not even changing the DNS. I am just using 2.4 till eventually maybe they fix it..AGAIN lol.

  2. Ray, try google's DNS instead:

  3. well... it appears to be LLs problem. I did both the fixes described here and when i finaly logged back in I found someone with the exact problem who loged in at the same time with me and did nothing to fix it earlier as i did.