The most difficult thing about configuring the DNS settings for a domain is designing a plan of action: making up one’s mind about what kind of services you envision and how you want to route the traffic. Here’s a primer on how to configure DNS using Route 53 or any other service.
The DNS system is broken. The sorry state of DNS security exposes your server and your end users to a variety of risks. Some of those risks are preventable.
When running your own mail server you have complete control over its performance and reliability. Here is how to get started with an open-source mail server on AWS EC2.
When migrating a web service or adjusting DNS settings you may come across unexpected behavior of your site long after all errors have been fixed (or so you thought before hitting the Reload button). The hard reality is that in their quest for speed, web browsers try not to make new DNS requests they deem unnecessary. The result is much screaming&steaming from administrators who are in the middle of a job.
With Amazon Route 53 Traffic Flow, the cloud provider introduced a traffic management service that lets you control how your end-users are routed to your application’s endpoints. (Route 53 is Amazon’s DNS and domain registration service.)