asked on Website / Email outage - -If so How long?
I am trying to confirm if there will be a EMAIL / WEBSITE outage due to making changes to DNS provider / changing WHOIS tech contact or any other unforseen changes
What can cause a outage to EMAIL and or website with what we are going?
- website domain is xyz.com DNS managed by MNSI.NET and currently hosted by go daddy
- Email domain is also xyz.com hosted by office 365 and emails MX record hit barracuda email security cloud service first
- We are launching a new website no longer going to be hosted by go daddy and DNS hosted by a different provider other than MNSI.NET
What can cause a outage to EMAIL and or website with what we are going?
* MXMicrosoft 365DNS
Last Comment
kenfcamp
ASKER CERTIFIED SOLUTION
Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a questionChanging DNS contacts should never cause any kind of outage.
No, but not updating relevant IP changes in your DNS record sure will
Did you verify the IP information in your DNS was updated properly to reflect the service changes?
DNS - New host/provider
DOMAIN - New host
Mail Servers - If you changed these too
Your help has saved me hundreds of hours of internet surfing.
fblack61
There's no such thing as a website for outage as far as I concern, You need to have skills to determine if a site went down. The issues vary, for example.
1- DDOS attack.
2- Cluster Down.
3- DNS forwarding issues.
4- TDL issues (that never happens but no bad to put it here)
5- Routing issues (load balancing, DNS round robbing, bad cache.
Again, the issue varies.
Something you can do is look for that particular website, see if you can telnet to it, try to ping it. Do a Nslookup find the name server that belongs to, see if the registrar is having issues, give them a call. Again, the problem might vary.