DNS could not resolve the host name. NO LOG-IN !!!

Unable to connect to Second Life.
DNS could not resolve the host name.
Please verfiy that you can connect to the www.secondlife.com
web site. If you can, but continue to recieve this error,
please go to the support section and report this problem.

appears since 7/28/2007 5:07 PM PDT.
over 12 hours yet!!!

I think you're not alone, someone i'm waiting for doesn't appear since that exact date and time. And its driving me nuts.

wrote and fiilled out a support ticket,
but before monday,
so i guess,
the support dont answer.
also a call isnt possible before.

It's possible your ISP's DNS servers have gone wonky.

You could try using OpenDNS (free service) until they're fixed.

No software required. You just follow the instructions here:

Windows: http://www.opendns.com/start/windows.php
Mac: http://www.opendns.com/start/mac.php
Linux: http://www.opendns.com/start/unix.php

Just make a note of your previous settings in case you wish to revert in the future.

I've used OpenDNS for months because they outperform any ISP I've used by a long shot.

Its not your ISP, I got the same error.. although it let me in after a few more attempts.

Try what's described here: /111/fc/200558/1.html

Helped me out... even after only having the prob of being unable to connect.

hello deep,
after 1000 attemps over several hours
LOL
i cant log in!

Sorry to hear that Innocenti you might want to try what Evolon suggested, seems to have worked for some. But the notion that it is your isp would mean that isp providers in the UK, Australia, Michigan, and Minnesota, are all having the same problrms at the same time. I only say this because i know of people from all these areas experiencing the same thing at almost the same times, given a few minutes between different 'crash' relog attempts.

hello deep,
thanks so much for your information.
hope they fix the problem soon.

Germany
Frankfurt am Main,
t-com/t-online

Larrie Lane
Registered User

Join Date: Feb 2007
Posts: 28

Thumbs up This will Solve Login Problem
I along with many others have experienced login dificulties for the past 24hrs.

I can now log in and here's how.

1) Goto Control Panel
2)Open Network Connections
3) Right Click your icon that connects to internet
4) Highlight the TCP/ICP in the list then click properties
5) Click Advanced
6) Open the DNS Folder at top of Menu
7) On the top box, click add and type the following 194.25.2.129
then repeat this process with 194.25.2.130
9) click okay then restart computer

This has worked on 2 of my computers 1 with Vista the other with XP and I am now back in SL.

Good Luck hope this helps and resolves your problems

/111/3c/200566/1.html


Last edited by Larrie Lane : Today at 09:31 AM. Reason: mistyped 1)

...just don't forget to set the DNS servers back to automatic after a while-what you will effectively been using with these addresses I had dug up are German DNS servers belonging to 1&1.

DNS problems like these usually mean something has changed (at LL) and the DNS servers of some ISPs are too slow to catch up. Not really LL's fault this time.

thanks much Alyx

DO NOT FOLLOW THE STEPS INNOCENTI HAS GIVEN.

See my comment here for more information: /111/fc/200558/1.html#post1606953

Lex Neva
wears dorky glasses

Join Date: Nov 2004
Location: Suffugium
Posts: 1,266

DO NOT FOLLOW THIS SUGGESTION.

What you're doing if you follow this is to make use of a DNS server that is run by someone else. While they should have locked their server down to only accept requests from their customers, that's no excuse for everyone across the net to use them. What you're doing, in essence, is stealing server resources from the people that run this DNS server... you're using an ISP that you're not paying for service from.

This is also by no means a catch-all solution, as this DNS server is in Germany. Right now, there's a problem with some people who are using a certain ISP in germany that are unable to resolve login.agni.lindenlab.com, which results in the "DNS could not resolve" login error message. Anyone elsewhere in the world should most definitely not follow these directions, as all of their DNS resolutions for anything they do online would have to go through Germany, which would likely make things incredibly slow for them.

Finally, there are SECURITY RISKS associated with using a DNS server that you don't trust. A malicious DNS server could manipulate the web pages and other internet content that you see, sending you viruses and spyware.

I can't say this enough: DO NOT FOLLOW THESE INSTRUCTIONS. I don't care if they work, they're a bad idea. If you're getting DNS problems, talk to your ISP's support and LL's support.

...and finally, if you ignore me, make SURE, after this German DNS problem is solved, that you switch your DNS settings back to their original values!

since 2 days yet.
so i test again and no log in is possible.
Linden tickets are filled out.
nobody answer
wath should we do.
stop sl.
the buisnewss, the sl people, the island, n so on.
nobody tell a other way to log in!
and btw. this information comes from:
Larrie Lane

Lex

Valid comments and in my original posting re the DNS numbers I did state I was in Germany.

However, I think you were a bit strong with your opening header "DO NOT FOLLOW THESE STEPS". If you know so much about DNS Gateways then you could of offered a little help as to what alternatives there are.

The only valid point you raised was that yes the DNS numbers given would or could be possibly overwhelmed and slow things down.

As an alternative people can use Open DNS @ opendns.com. This is reported as being safe and in most cases quicker than most ISP's DNS Gateways, and many computer mags praise them for their services.

so we have a chance to participate!

Can I just agree here- we both said they're GERMAN DNS servers AND you should switch back as soon as possible.....Lex made it sound like we suggested switching off the firewall or something...

I think my comments are also valid in that using another ISP's DNS servers is illegal. It constitutes a theft of resources. I say this from experience: I once got in some pretty serious trouble for using someone else's DNS servers. I had no idea it was a problem, so I'm trying to warn people here off before they accidentally do something that's rather unethical.

Opendns.com, now that's a good solution to this problem. They have instructions for getting their DNS servers set up in most operating systems.

Granted, it's not as bad as that in this case, but telling someone to switch their DNS servers could be used as an attack vector as bad as switching firewall settings off. All in all, making these kinds of changes and not knowing what you're doing is a big problem, which is why I spoke so strongly. It'd be far better for people to contact the ISP(s) that are having trouble routing DNS requests to LL.

Problem is, as I said, most German ISPs I have used have customer support that makes LL appear positively caring and competent (caveat: I haven't yet had any bad experience with LL's support yet, but many people apparently had) and if you try to get anything done you would first have to explain to them what a DNS server actually is....only to have them tell you they have no idea what to do....
I keep forgetting not everyone has our experience (I started out with a C64 and was online even before actual proper modems existed, back in the early 80s, and have worked with computers and networks ever since).
Using German Telecom DNS servers for people in Germany is also not quite illegal as most other ISPs just rent their lines anyway.

The other 1/2 of problem, LL's DNS TTL for login.agni.lindenlab.com is 48 days!

oh, hooray.....

login.agni.lindenlab.com. 300 IN SOA ns-a.pnap.net. hostmaster.lindenlab.com. 1 43200 600 1209600 60

Let's see...

That first number is the serial number... kind of an odd serial number (1), but acceptable. 43200 is the interval for secondaries to refresh the zone. 600, 10 minutes, is the interval for secondaries to retry if the primary was down. 1209600, a lot of time, is the time until the data in the secondary expires and becomes invalid, if the primary is down for a long time. 60... crap, I forget what that is.

The 30 right after login.agni.lindenlab.com. is, I _think_, the ttl... 5 minutes. I'm not compeltely sure on all of this, but I think this means that the TTL isn't actually 48 days... it's been awhile since I was deep into DNS stuff.