Connection to EQFollow

I was able to get the dns fixes to work last night when I went to log on to see if we were gonna raid, of course it was cancelled and all until further notice due to this wonderful issue. They say it is due to they forgot to pay their internet bill, how in the world does somebody who works for a major corporation such as SOE forget to pay the 1 bill that makes you the most money. I am personally calling BS! on this and it is more then likely an excuse for another issue. Anywho.......so far this morning can't log on to game, SOE website, forums or anything of theirs, so any of you computer geeks got a fix for this I think they might need your help, cause it looks like their IT people are slacking.

Try this post at https://everquest.allakhazam.com/forum.html?forum=1&mid=1405419109293491850&h=50&p=1#30 -- OP may need to do multiple flushes to get it to work. Might try simply ipconfig also, which is how I got mine to clear after several attempts using the /flushdns option. Just in case that might help.

Yther Ore.

The first address goes directly to Sony's dns server (which they've presumably updated with the correct address/name correlations). The second goes to a google dns server (which looks like is one of the first tier A record servers). So presumably safe to use.

Yeah. My understanding is that the contact email went into the bit bucket (or at least that is what they are claiming, you'd think someone at NS would have actually contacted Sony directly, but I suppose the process could just be automated or something). There's a ton of possible explanations, but I'd lean towards a scenario where some nutty networking engineer created an ugly spaghetti-like mess of network namespace interconnections and dependencies that only he really understood. It worked for years. Then he left the company and no one touched it because it was working. Add about 5 more layers of namespace redirection on top of that, and it's entirely possible that you'd not even realize that somewhere buried in the guts of your system was a dependency on the .net namespace.

I've seen this sort of thing happen. And you almost never find and fix such things until after they bite you. And you usually don't have a clue why it bit you either. You just yank out the old rats nest and replace it with something new and shiny and hope that in 10 years, that's not also going to look like a complete mess that only a crazy person would have constructed like that.