Kevin

Are you on a VPS? I've seen this in WHM on various VPSs, but I don't see those options in WHM as a reseller. Would be great to be able to take advantage of those backup options there.

"Most are only about 14 hours before the outage, one or two servers are 48 hours or so." - https://forums.mddhosting.com/topic/1583-major-outage-092118-client-discussion/?p=6923

Awesome, thanks!

Just to double check, since there was no mention of IP changes in the Jasmine email, that means IPs will stay the same, right? Wasn't sure if that was still a possibility to come later.

When will you be rebooting?

this should help http://www.mddhosting.com/support/knowledgebase/113/What-nameservers-should-I-use.html whereever you have your domain registered, you should be able to update the nameservers with the info above

May or may not work, but did you try port 26?

You could check out http://whmeasybackup.com/ but it won't store to Amazon S3

I think the 200 hourly max has been in place and in the mailing policy since about the second half of 2008, so the policy has been there a while. Before that it was 500. The old policy used to have a couple lines "Anytime you're sending a message no matter how large your e-mail list is you must throttle it. We recommend you throttle it to no faster than sending 1 email every 6 seconds." and "If the mailing list software you're using does not allow you to throttle you must switch to something else." but I see that's gone now.

If you click on the "help me understand" link on that page, it explains what is happening pretty well. gemini.supportedns.com is the website the SSL certificate is issued to and and that is the server your cPanel/WHM account is on. It's ok to click "proceed anyway" because gemini.supportedns.com can be trusted. You should be careful though when you see this message and only proceed if you know for sure you can trust the site. Otherwise, just access your cPanel/WHM accounts at https://gemini.supportedns.com:2083/ or https://gemini.supportedns.com:2087/ and you won't see the message anymore.

You could try this method with an htaccess file... Sorry i want to add a link but i am posting from my smartphone and the link keeps getting trimmed for some reason. So, just google htaccess maintenance david walsh Hopefully you get the right post i am talking about

Looks like my account is being transferred over now so this message can be ignored

Not that it is a huge deal to me but was wondering if you have an update on the progress of the transfers. Thanks

I posted this at http://www.webhostingtalk.com/showthread.php?p=8211838 but decided to post it here too ___________________________________________________________________________________ I’ve been with MDDHosting for just about a year now so I figured it was time for a review. I have one shared account with them and a reseller account (to be specific, I have had the shared account for about a year and the reseller account since January 2012). I did extensive research before deciding to purchase MDD’s services and so far I have not been disappointed. For the shared account, I have DNS failover monitoring so when the server at MDD goes down, it will switch over to a backup location. Over the past year, I think it has only switched over less than five times and those were for only a matter of minutes so the reliability I have seen has been excellent. For a shared account I think this is really good to have this few unplanned outages. They also have planned outages from time-to-time and that’s ok with me because I know they are trying to improve services. For the reseller account, which is on a different server than the shared account, I have had a similar experience and have noticed an increase in the overall speed of the websites I host compared to my previous web host. Support has been great and no matter when I submit a ticket, they are responded to extremely fast. Overall I am a very satisfied customer! For further reading if interested, here is a list of a few of the things I really like about MDDHosting: Keeping customers updated – The forum on their website has a server and network announcements area and they keep it updated regularly so if there is a problem, you know exactly what’s going on. Also their server status page is really nice to see what’s going on and they use pingdom to monitor all servers Fast and reliable servers – As stated above, I have had very few issues and all of my sites run very fast. Legal Info – I really appreciate the fact that they have very clear terms of service, support scope, privacy policy and mailing policy listed on the site. That’s really important so I know exactly what I can and can’t do and I also think they have some strong policies in place and that makes me feel good because I know if someone is abusing the system they won’t be allowed to stay. Taking care of current clients – While MDD runs promotions to try and get new customers (like most hosting providers), they also run promos from time to time for current customer Mike (the owner) is very honest and will tell you like it is. He won’t tell you something just to make a sale or make you happy, but I believe he is someone that really wants the best for each client/potential client.

I'm not sure if you are checking back at this since it has been a few days since you posted but I will throw in a couple thoughts as I am a current DNS Made Easy customer that is using the failover service. My current setup is fairly complex I think, but it has been well worth it. I have been on a great web host and failover only kicked in two times in two years...I had very little down time. DNS Made Easy only monitors the servers and switches the traffic, you have to do all the mirroring setup and such...below is some of my experiences Anyway, my setup was in the VPS environment so I am not sure it would necessarily work in the shared environment because of the things I had to set up. I had my website completely mirrored, meaning I was running MySQL replication and also used RSYNC to transfer files over to my mirror server. I set the RSYNC interval at 20 minutes, so every 20 minutes, new files would transfer and it would delete any files I changed on the main server. MySQL replication was instant. On a shared server, I would probably just put a static page on another server somewhere that says the main server is down and then maybe provide some contact info. Then I could also provide updates on that page. A couple things to consider, any changes made on the mirror server will not get made on the main server. So, if you do anything on the mirror, you would have to transfer files back to the main server manually. In the DNS Made Easy system, you can specify whether you want to have the DNS automatically switch back after the main server comes back up or if you want to manually switch it back. In my setup, I had it switch back automatically. However in my admin section on the site, I had a setting that would check the current IP of the server. If the IP was the mirror, I locked out the admin area and would not allow changes to the database. The reason I did that was because setting up MySQL replication is fairly painful so I tried to avoid making any changes because otherwise I would have to set it up all over again. For your question about email, I believe it can be done but I have a concern with that. If your main server goes down and it switches over to the mirror, and your email starts going there, when the main one comes back up, the emails won't be on that one. If your clients are pulling messages off the server with POP, then it probably is less of an issue and that might work great. But, if they rely on having the emails stored online, that would be a problem. Another thing I would recommend for the mirror is being on a different host (not setting up a second account with MDD). This will help insulate you from network issues or other issues at the data center. I was lucky enough to be with a host that had servers in both Washington DC and Los Angeles. It was great because they had the same server setups at each location and I could manage everything (billing, support, etc.) with one host. It was also nice because their networks were inter-connected cross country which made it super fast so when running RSYNC, things transferred really fast...the data transfer was not counted as used bandwidth either because it was considered within their network Anyway, so overall while I highly recommend DNS Made Easy and failover in general, it is not something I would jump into unless you have the right client. It will double your cost (since you need two server) and system setup and monitor can take a lot of time. So, if you have that special client that really needs it, then I would do it but it will be costly (especially if you have a complex setup with MySQL replication and such). If it is an ecommerce site, then that is going to require even more...SSL certificates at both locations, not to mention billing concerns and a whole boat load of other things I really can't totally grasp. However, if you want to do a setup that is just a static page with updates of what is happening, this would be fairly painless. I hope this helps you understand a little more. If you have more questions, feel free to ask and hopefully I can help