The Sucuri firewall functions as a reverse proxy, filtering all incoming traffic through the Sucuri networks, parsing good requests from bad requests. To accomplish this a change is made to your DNS settings.
Specifically, one or more A records are added to the existing configuration, or an existing ones are modified.
If not done carefully, these DNS changes can affect connectivity to other non-website services such as Mail, FTP, SFTP, or cPanel/WHM. A review of your DNS records and some small changes can resolve these issues.
DNS Configuration Updates
During the initial configuration of your website we provide you a clean Settings Page in your Website Firewall dashboard. This page provides you all the information you require. You can access the page by logging into your Sucuri firewall dashboard
Click the settings gear icon beside the affected domain and select General
On this page, you'll find the following information:
You want to pay special attention to the Hosting IP Address section. This IP belongs to your Host, it's where all the content for your website lives, it's where you will FTP / SFTP into to make changes, and where CPANEL is configured.
If you're used to connecting to your domain by navigating to ftp.example.com it may no longer work if the FTP record is pointing to your example.com domain. This domain is in turn pointing to the Sucuri IP (reference above).
To fix the issue, you will need to access your server using the Hosting IP Address:
Hosting IP Address: 66.xx.xx.78 (Your Hosting IP address)
If you're used to access CPANEL like this http://example.com/cpanel the same applies as the FTP.
You will want to adjust your URL string to use the Hosting IP address. It will not look like this:
CPANEL Access: http://66.xx.xx.78/cpanel
- or -
CPANEL Access: http://66.xx.xx.78:2082
Fixing Your Email
Email can stop working for the same reason. While every DNS provider is different, the basics of what has to happen are the same.
Email requires special DNS records named Mail Exchange Record (MX Record) which point to another record in your domain. Usually, the MX record for example.com is set to mail.example.com which causes the same issues with mail as it does for the other non-web services. The example.com domain can only receive web traffic, not mail traffic.
That, incorrect, configuration can have your MX records pointed to records that look like this.
If you're working off a typical CPANEL configuration, you will want to change the following in the MX Record section:
mail.example.com = >> [66.xx.xx.78]
If you're working off a typical GODADDY configuration, you will want to change the following in the MX (Mail Exchanger) section:
Host = @ -->> Host = [66.xx.xx.78]
Still Not Clear? Need Help?
Please open a General Support Request.
This will be assigned by a trained support agent that will access your DNS account and fix whatever issues you might be experiencing