PDA

View Full Version : Cant get MM.net through AOL


Blackened300a
02-28-2006, 05:12 PM
Im not sure if its just my computer but for the past Year I have never had a issue logging onto the site, today I go into my favorite places, click the link and it says the site dont exsist.
I can go through the internet explorer without a problem, Its only AOL thats preventing me from connecting to the site.
Any Ideas??
I cleaned out my history, Restarted the computer, ran all my spyware and virus programs and they all came up clean.

So whats the deal???
blackf0rk
02-28-2006, 05:18 PM
AOL is the devil. The do stuff sometimes that boggles the mind.

Well speaking of MM.net site problems, it been going on and off for me the past few days. It was just down several minutes ago - same for everyone else?
Blackened300a
02-28-2006, 05:22 PM
Well speaking of MM.net site problems, it been going on and off for me the past few days. It was just down several minutes ago - same for everyone else?

I guess Im not the only one then. I can only get the site through the internet explorer.
This is the only Site Im having a problem with.
MM2004
02-28-2006, 06:30 PM
AOL is the devil. The do stuff sometimes that boggles the mind.

Well speaking of MM.net site problems, it been going on and off for me the past few days. It was just down several minutes ago - same for everyone else?

Couldn't get to this site on 2 different machines, both running IE6.

Mike.
Dark_Knight7096
02-28-2006, 06:32 PM
RoyLPita just IMed me saying he was having trouble accessing the site through both AOL AND IE, idk what's going on, AOL always tells me this stie doesn't exist but IE always bring me right here.
Logan
02-28-2006, 06:42 PM
Should I mention that I just finished migrating the site to brand new servers in a different data center and we're now running on 64 bit Linux...

...and that that transition is why anyone might've had issues accessing the site?

As for AOL or anything else, my testing includes seeing if me, myself and I can access the site from my house. If I can, it's good. The rest of ya, you're on your own... ;)
Blackened300a
02-28-2006, 07:13 PM
As for AOL or anything else, my testing includes seeing if me, myself and I can access the site from my house. If I can, it's good. The rest of ya, you're on your own... ;)


Hey, Have I told you lately How Much I loved your hat you wore on Motorweek??? :D

No shot getting this working on AOL again so its Internet Explorer for now on!
Thanks Chief!
sweetair
02-28-2006, 08:31 PM
I had the same issue aerlier today, now all is well and the sun shines on...:banana2:
bagpiper
02-28-2006, 08:51 PM
Had the same problem today,Thought maybe it was on my end.
Agent M79
02-28-2006, 10:01 PM
It seems to be a DNS propagation issue. It'll clean up as everyones DNS servers get updated. AOL will be last. They are usually slow.
BK_GrandMarquis
03-01-2006, 05:09 AM
It seems to be a DNS propagation issue. It'll clean up as everyones DNS servers get updated. AOL will be last. They are usually slow.

Yeah, looks like that was the problem. I had problems at work yesterday but it cleared up just before I left. At home I was not able to connect till this morning.

Whew, I was starting to have withdrawal symtoms already. :D
CRUZTAKER
03-01-2006, 05:33 AM
AOL users might try flushing their DNS... :dunno:

Go to a command prompt, C:\ , and enter the following:

ipconfig /flushdns
2003CTMarauder
03-01-2006, 05:56 AM
I couldnt get on for a while yesterday but its all good now.
Logan
03-01-2006, 06:14 AM
The new box is bigger badder and newer. The old server is coming in for some R&R and a OS refresh, then it'll be redeployed as a backup to the server the site is now on...
MM03MOK
03-01-2006, 06:17 AM
backup is always a good thing.....
SID210SA
03-01-2006, 06:29 AM
Yeah, looks like that was the problem. I had problems at work yesterday but it cleared up just before I left. At home I was not able to connect till this morning.

Whew, I was starting to have withdrawal symtoms already. :D

I was was having withdrawal as well, I was getting all worked up thinking that I could not get back on the site....My friend SVT could access it here localy so I thought maybe my work put this site restricted cause I was on here too much....WHEW! Glad that was not the case. I have Yahoo dsl no aol here....Could not access all day...I was keeping my fingers crossed this morning:D
ckadiddle
03-01-2006, 07:53 AM
Should I mention that I just finished migrating the site to brand new servers in a different data center and we're now running on 64 bit Linux...

...and that that transition is why anyone might've had issues accessing the site?

As for AOL or anything else, my testing includes seeing if me, myself and I can access the site from my house. If I can, it's good. The rest of ya, you're on your own... ;)
I assumed that Master Logan had the site down for upgrade or repairs. Thanks for all your hard work Logan!! I only suffered minor withdrawal symptoms, bit the end of my tongue off during withdrawal seizure. Duct tape and it's nearly as good as new. But I thalk a liddle thfunny noww.
jim geary
03-01-2006, 08:16 AM
All is well. I couldn't get on for almost 2 days.Very stressful. Glad to see it
wasn't my server and just Logan upgrading. Thanks Logan.
Jim Geary.
Blackened300a
03-01-2006, 03:48 PM
OK back to normal here

Thanks Chief!
Logan
03-01-2006, 05:31 PM
Unfortunately, there's wee little bastard called "TTL" or Time to live that DNS servers use to control how often the DNS servers refresh themselves. So any physical change to IP information takes "time" to refresh across the net. Most places run a 12 hour TTL, but some are 24 hours or longer which causes problems.
Black Terror
03-01-2006, 07:10 PM
I am using AOL Explorer version 1.2.5.15 and have had no problem accessing the MM.Net site.
TooManyFords
03-01-2006, 07:32 PM
Unfortunately, there's wee little bastard called "TTL" or Time to live that DNS servers use to control how often the DNS servers refresh themselves. So any physical change to IP information takes "time" to refresh across the net. Most places run a 12 hour TTL, but some are 24 hours or longer which causes problems.

Here's a tip from one ISP to another... When you get ready to make an IP move of a website, reduce the Caching TTL in your SOA record to a really low value (say 300) a week or two before the switch. This will reduce the TTL cache of remote DNS servers and allow you to switch IP space almost instantaneously. If you really have strong DNS servers, you can actually set this to ZERO and make ALL requests come straight to the source for every resolver request thus making this immediate. I don't recommed this but it can be done.

I did a check of you servers and see that your SOA Refresh is a tad high at 86400. This can also cause DNS "limbo".

Your SOA Expire valuse of 3600000 (about 6 weeks!) If your secondary server can't find your primary in less time than this, you've either moved to Tahiti or your network is down for good. (hehe)

But the one that would have helped the most is the SOA MINIMUM TTL, which is set to 86400 (24 hrs). This is why many could not find you for over a day or so. Next time you move something, set this to 300 at least 48 hrs in advance and then you will never lose someone again.

This all can be viewed here:
http://www.dnsreport.com/tools/dnsreport.ch?domain=mercurymar auder.net

Oh yes, and be sure to set your SPF record to help prevent spammers from using your domain names.

Also, in the future, I run DNS servers 24/7 so if you want to use one of my boxes for an offsite backup DNS (with access) you're more than welcome. This will also protect the site from a DNS crash or your local DNS servers having problems. I see yours are on the same class C and this would help. Just PM me and it is yours.

Cheers!

john