Report of a Problem

[AmandaHoliday]

What's up? Now 3:14 PM MDT. I've tried logging in since 1:30 and get a message, the "The DNS cannot resolve the login.  ….Report this problem...."

[Rolig Loon]

From the fine folks who created the Firestorm wiki:

General

If you have DNS errors trying to log in, or simply get disconnected during or immediately on log in, try flushing your DNS cache; how to do that is explained here for Windows, Linux, and Mac.

If this doesn't help, then try setting your DNS to Google: Google Public DNS

Should using Google as a DNS not work for you then see here for alternate servers, or grab DNS Bench to help you locate one.

See below for other causes which are specific to your operating system.

Windows

DNS errors might be caused by anti-virus software; see this page for more on that.

Edited August 5, 2019 by Rolig Loon

[Oz Linden]

When reporting a DNS problem, it is helpful if you describe what you were doing (opening a browser to the marketplace, logging in the viewer, ...), specifically where you are, if possible including what ISP you are connecting through.

DNS is a global distributed system, with potentially many layers of caching between you and the systems that provide the information about our current names and addresses; some of those layers don't follow all the rules or are buggy enough that they are sometimes not in sync with us.

Flushing your local cache may sometimes help, but won't help with the cache you probably have in your home router, the ones in your ISP, or any of the others that may be in the path. Debugging this can be very frustrating.

There's a pretty good page on debugging DNS at https://www.a2hosting.com/kb/getting-started-guide/internet-and-networking/troubleshooting-dns-with-dig-and-nslookup

As far as I can tell we didn't change anything last night involved with this, and right now I don't see major providers that have bad data.

[AmandaHoliday]

About how long does the DNS flush take? Granted, I'm anxious to get on, but it seems an awfully long time since I started, a half hour.

Never mind. I finally hit enter, and the command given in the Hofstinger Tutorials page is not recognized as z valid command.

Got another one?

 

Edited August 5, 2019 by AmandaHoliday

[Will Shabtay]

I have been having the same DNS error problem all afternoon/evening (SLT+3) with no luck resolving. I am on Windows 10 and did the DNS flush (it took no time at all on a SSD). Unfortunately it has not resolved the problem. The SL Client and Firestorm both fail, although everything else on my system/network are working normally. Given a little extra time on my hands, I also did a clean install on both clients to no effect. I have submitted a help ticket but those take time.

Having been around SL for a while I am guessing there is a bug in the system with will take time to resolve and don't feel like doing major surgery to my system only to find out it was SL. Other advice is welcome, hope others have submitted tickets.

[Rolig Loon]

Have you tried adding the free Google DNS server to the list in your router?  I did that years ago and have never had DNS problems since.

[Whirly Fizzle]

Another affected person on the JIRA

BUG-227462 - DNS error when logging in

[AmandaHoliday]

 

Oz Linden,

I logged in for the morning, took a break for lunch. That's when on the attempt to log in again the problem started. By my clock, around 1:30 PM MDT. I tried every step suggested by Rolig Loon. Never got it fixed when I decided to go to sleep instead of fightin' a lost battle to the bitter end. Went to sleep around 9 MDT.

Woke the next morning about 4 AM, MDT, tried to log in and did with no fight. It might be connected to that problem mentioned on the Linden Blog site.

Does that help despite its tardiness?

Addendum: If you need to log in on my account, go ahead. I'm willing if you need to. Just need to know whether I should be logged in or out while you're there.

 

Edited August 11, 2019 by AmandaHoliday