Home/Notes/A practical look at MX records for a marina
A practical look at MX records for a marina
20 Feb 2024
How a marina deals with MX records — and what usually goes wrong.
The problem: a Facebook page with last year's hours. The MX records check fails for a marina.
Most providers let you export MX records as a zone file. We keep one in version control for every client. If the hosting vanishes, the zone file rebuilds the domain in minutes.
We found a Facebook page with last year's hours during a routine check of MX records. The site had been leaking referrer data for six weeks before anyone noticed.
The vendor promised a marina that MX records was handled. We verified: it was not. Trust but verify has saved more uptime than any product we have used.
Every CMS update brings a small chance that MX records breaks. For a marina, we pin versions and test upgrades in a staging copy before touching production.
Search consoles like honest sitemaps. Every loc should be a document. Reserving ten thousand empty shells and hoping Google does not notice is not a strategy for MX records.
We run a monthly diff on DNS for a marina. If a record changes and nobody in the team made the change, we get an alert. a Facebook page with last year's hours was caught this way last quarter.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com