Unable to contact Authentication server?
- Thread starter toleranse
- Start date
Kannkor
Ogre
There's an issue with something [router/dns] some where between part of US and the auth server. I can confirm 100% the auth server is working as many of us can connect fine, however there is a decent size group of you that can't.
We're discussing in IRC at the moment.. but it seems like it's not on the users end, and not on my end, it's some where inbetween. So it's a waiting game.
Kannkor
Ogre
It seems like it is a DNS issue affecting some people.
Note: This is NOT on my end, and not on your end, it's some where inbetween.
I'm not an expert in this area, however here is the information I have, and a temporary solution.
The basics: What is DNS? Think of it like an electronic phone book. On your cell phone, you could select "Call Kannkor", it has to go look up the phone number for "Kannkor". The same thing happens with all webpages. You type in www.google.com and your computer looks up the phone number (well, IP address, but you get the idea).
The problem: A major DNS isn't able to find the IP address for my auth server (as well as many other webpages). Without the IP (or phone number), it doesn't have a way to contact the auth server.
A temporary fix: You can tell your computer the IP address for any entry you wish (in this case, you can say Ogre's auth servers IP address is _____). Below I'll show you how to do this. Before hand, there is an issue with doing that. Webpage IP addresses change, this is why we use names (and it's easier to remember). When the auth servers IP changes this fix will stop working, and actually prevent it from working. Then you have two options, update the file every time the IP changes (bad option), or delete the entry and let the DNS do it's job (good option).
Again: After you manually add this, once the DNS issue is resolved, you'll want to remove it.
How to manually add the auth server to your local host file.
Locate the file: c:\Windows\Systems32\drivers\etc\host
Edit the file (such as with notepad).
Add the following to the bottom of the file, on a new line
174.133.59.78 logan.warpigs.us
Save the file and everything should work fine.
If you do this, I highly recommend you remove this entry tomorrow (assuming the DNS is resolved).
Note: This is NOT on my end, and not on your end, it's some where inbetween.
I'm not an expert in this area, however here is the information I have, and a temporary solution.
The basics: What is DNS? Think of it like an electronic phone book. On your cell phone, you could select "Call Kannkor", it has to go look up the phone number for "Kannkor". The same thing happens with all webpages. You type in www.google.com and your computer looks up the phone number (well, IP address, but you get the idea).
The problem: A major DNS isn't able to find the IP address for my auth server (as well as many other webpages). Without the IP (or phone number), it doesn't have a way to contact the auth server.
A temporary fix: You can tell your computer the IP address for any entry you wish (in this case, you can say Ogre's auth servers IP address is _____). Below I'll show you how to do this. Before hand, there is an issue with doing that. Webpage IP addresses change, this is why we use names (and it's easier to remember). When the auth servers IP changes this fix will stop working, and actually prevent it from working. Then you have two options, update the file every time the IP changes (bad option), or delete the entry and let the DNS do it's job (good option).
Again: After you manually add this, once the DNS issue is resolved, you'll want to remove it.
How to manually add the auth server to your local host file.
Locate the file: c:\Windows\Systems32\drivers\etc\host
Edit the file (such as with notepad).
Add the following to the bottom of the file, on a new line
174.133.59.78 logan.warpigs.us
Save the file and everything should work fine.
If you do this, I highly recommend you remove this entry tomorrow (assuming the DNS is resolved).
pz
Active Member
we've not received any actual information on what occurred yet, but the issue seems to have cleared up (though it may not be instantly resolved at your individual locations/isps).
the nameservers at Hurricane Electric (he.net) seem to have completely stopped serving dns zones earlier this afternoon for a period of roughly 90 minutes. we've added another nameserver outside of their network as an added precaution.
apologies for the inconvenience!
the nameservers at Hurricane Electric (he.net) seem to have completely stopped serving dns zones earlier this afternoon for a period of roughly 90 minutes. we've added another nameserver outside of their network as an added precaution.
apologies for the inconvenience!