• 0

Dead server prevent reciept of all email


Question

The server my website is presently hosted on has completely failed and the hosting company are taking ages to restore from a backup to a new server - in the meantime I'm unable to recieve any email whatsoever.

My setup is as follows:

Domain has namerserver 1 and 2 set to the server (which is presently down).

MX records were set through WHM on the server, these pointed mail to Google Apps for Business.

As the server is down and thus completely missing the MX records basically don't exist and thus no mail ends up in Gmail (Google Apps for Business).

I was wondering... is there anyway to set MX records or point mail to Gmail directly at the domain level without having to go through the server and thus wait for the server to come back online?

I must admit I only know the basics of how to set the above up - my logic says it should be possible for example to set a third nameserver so if the first two namerservers are "missing" mail still ends up at Gmail?

4 answers to this question

Recommended Posts

  • 0

Thanks,

Think I've been very unfortunate with the death of the server. Being hosted with them maybe 10 years and no problems till now.

Looking at their tech support forums which has a "sever status" section of their 1000+ servers it looks like mine is the only one that has ever had any serious issue - doh.

New server now running - hurray!

Seems like logically it would make sense to have the ability to set my domains namerservers to my host, whilst also having mx records set at the registrar. The current configuration adds another layer of hardware into the sequence that seems somewhat unnecessary.

  • 0

no it doesn't make sense. the nameserver is the one that tells people what all the records on your domain are. what you want to do would essentially create 2 tiers of name servers, one that only has some records, and another, second one that has more records. that's unnecessarily complicated.

also, you're not adding another layer of hardware. the record of where the nameserver itself is, isn't hosted by your registrar, by by the people that run your domain's TLD. the registrar's interface is only used to let you update your records. the difference between chosing "default" versus choosing your host at your registrar's control panel just changes whether that points to your registrar's servers or your host's servers.

(this is kind of a poor explanation but hopefully gets the gist across)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Hello, Also known for https://www.theguardian.com/technology/2009/jan/29/adware-internet.   Regards, Aryeh Goretsky    
    • Hello, I have used a few TEAM Group SSDs, USB flash drives, and Micro SDXC cards in the past. They all seemed to work fine. Regards, Aryeh Goretsky
    • "just $100 per TB"? Just? Are we trying to make this seem like the new normal? Kinda weird to make it sound like that is not a ridiculously expensive asking price.
    • The reviews you refer to mean nothing. Where there is no journalism there is no reason to call the gaming media's opinion pieces "reviews". For GP games there is indeed a metric for success - increasing subscriptions. Which turns in revenue. The only circumstance in which subs do not rise when great is being released is a Game Pass system where the company is close to fully saturated with customers in a subscription. However, in that case as the theory goes you spend aplenty in all kind of games - from shady live service cash cows and customer offending agitprop crap in purple colours to robust and entertaining single player games. And keep a solid level of profitability. Ignoring the simply innocuous but mid games MGS has released primarily of the second kind.
    • Report: Microsoft to use AWS to help GitHub deal with a major surge in demand by Pradeep Viswanathan Thanks to the surge of coding AI agents, GitHub's usage has skyrocketed over the past 12 months. To meet this demand, GitHub started with a plan in October 2025 to increase capacity by 10x. However, by early this year, the company realized that it needed 30x scale. This rapid growth has caused severe strain on the platform's reliability, resulting in several small outages over the past few months. In April, GitHub published a long blog post explaining the steps it is taking to resolve these reliability issues. In the post, the company also confirmed that it is working toward a multi-cloud architecture for better resilience. Today, Business Insider reported that GitHub is turning to Amazon Web Services to help deal with a major surge in AI-driven coding activity. It is important to note that GitHub is still in the process of moving completely to the Azure cloud. The current plan is to move the platform fully to Azure by 2027 so that it can scale better as per developer demand. Therefore, the current decision to utilize AWS might be part of a short-term plan to meet immediate demand. A Microsoft spokesperson confirmed that GitHub is using multiple cloud providers with the following statement: For Microsoft, the decision highlights the operational pressure behind the AI boom. GitHub has to stay reliable for developers at a time when rivals such as Codex, Cursor, Claude Code, and other AI coding tools are gaining attention. And the decision to use AWS for computing capacity seems practical given the circumstances.
  • Recent Achievements

    • Collaborator
      vjlex earned a badge
      Collaborator
    • Reacting Well
      Dys Topia earned a badge
      Reacting Well
    • Conversation Starter
      NovaEdgeX earned a badge
      Conversation Starter
    • One Year In
      Console General earned a badge
      One Year In
    • Week One Done
      Twozo Technologies earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      182
    3. 3
      PsYcHoKiLLa
      106
    4. 4
      Steven P.
      88
    5. 5
      ATLien_0
      68
  • Tell a friend

    Love Neowin? Tell a friend!