Skip to content

DNS Recommendations

In order to accommodate the autoscaling cloud features of Stratus, the configuration of Domain Name Servers is an important step is configuring a Stratus installation.

With Mojo Stratus, there are three options for configuring your DNS.

  1. PreferredRoute 53 is provided with Stratus and can host domains through the Stratus DNS management system. Domains configured using the MageMojo Route 53 instance are pointed to a CloudFront distribution directly and will take full advanted of CloudFront Global Edge Node caching.
  2. Acceptable — DNS solutions that support CNAME ALIAS for flattening may be used. This method is supported by Cloudflare as well as Route 53. When using Cloudflare do not use the Cloudflare CDN alongside Stratus.
  3. For Temporary Use Only — A DNS A record may be used to point to a particular CloudFront edge note. However, this IP is very likely to change and would require updates to A records. This method is not supported or guaranteed to work.

NOTE: Free Let's Encrypt SSL Certificates provided by MageMojo will only work with the Preferred method.

Using the Stratus Route 53 DNS

When a domain is added to Stratus, a DNS zone is also created. The nameservers are then available above the DNS zone.

NOTE: The nameservers will also be slightly different for every domain, since Route 53 has many different nameservers.

To retrieve the necessary nameservers for a given domain,

  1. Open DNS panel in the Stratus Control panel.
  2. Select the domain in the left column.

The right panel will show the four nameservers to use to configure a domain to point to Route 53.

It may take up to 24 hours for DNS changes to fully propagate.

Using Third-Party Nameservers

NOTE: MageMojo cannot provide Let's Encrypt Certificates for use with non-Stratus Route 53 namesevers.

Due to the sophistication of the Stratus AWS platform, configuring an outside nameserver can take several important steps.

Please note that the instructions for configuring a third-party nameserver must be all completed for Stratus to work properly. MageMojo Support will gladly help if asked.

  1. Go to DNS in the Stratus Control panel.
  2. Select a domain name shown in the left column. The full DNS zone will appear in the right column.
  3. Use the items listed in Other Records to populate the third-party DNS.
  4. Note the CloudFront Endpoint Url shown under Root Record.

In the third-party domain, use the Cloudfront Endpoint as a CNAME record for "@"(apex), "www" or any other sub-domains that will point to the Stratus instance (e.g. "store"). Use CNAME flattening or an ALIAS if the DNS host supports it. Otherwise an A record is required (but not preferred).

Once the DNS changes propagate, return to the DNS panel and ensure the proper domains are set per Url guidelines.

Using an A record

If an A record must be used,

  1. Go to the DNS panel in the Stratus Control panel sidebar menu.
  2. Select the domain in the left column. The full DNS zone will appear in the right column.
  3. Copy the CloudFront Endpoint shown.
  4. Use the dig command to discover the IP number for the CloudFront endpoints.
bash
dig d1xq81t8a33nfn.cloudfront.net
; <<>> DiG 9.10.3-P4-Debian <<>> d1xq81t8a33nfn.cloudfront.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16848
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;d1xq81t8a33nfn.cloudfront.net. IN      A

;; ANSWER SECTION:
d1xq81t8a33nfn.cloudfront.net. 30 IN    A       54.230.195.26
d1xq81t8a33nfn.cloudfront.net. 30 IN    A       54.230.195.46
d1xq81t8a33nfn.cloudfront.net. 30 IN    A       54.230.195.80
d1xq81t8a33nfn.cloudfront.net. 30 IN    A       54.230.195.220
  1. Pick any of the IPs available. They will vary depending on your geographic location.
  2. In the third-pary DNS, set any A records to any of the discovered IP numbers as needed.

Note that CloudFront Endpoint IPs can often change and will require these steps are repeated.

SSL Certificate Generation

DNS settings are important because they tie into the automatic SSL certificate generation service included with Stratus. Once correctly configured, the file verification check for Let’s Encrypt will start working.

Clearing Local DNS Cache

If the proper DNS results are not being observed after a reasonable propagation period, clear the local DNS cached:

Clearing DNS Cache in Windows 10

  1. Enter "cmd" in the Cortona search text box.
  2. Right-click Command Prompt and select Run as Administrator.
  3. Run the following command: ipconfig /flushdns If the command succeeds, the system returns the following message: Successfully flushed the DNS Resolver Cache.

Clearing DNS Cache in Windows 7

  1. Click the Start button.
  2. Enter "cmd" in the Start menu search text box.
  3. Right-click Command Prompt and select Run as Administrator.
  4. Run the following command: ipconfig /flushdns If the command succeeds, the system returns the following message: Windows IP configuration successfully flushed the DNS Resolver Cache.

Clearing DNS Cache in MacOS 10.10.4+

  1. Go to Applications > Utilities in the Finder.
  2. Open the Terminal application.
  3. Run the following command: sudo killall -HUP mDNSResponder and enter the Administrator password when prompted. If the command succeeds, the system does not return any output.

Flush public DNS Cache

DNS can take up to 24 hours to fully propagate. A DNS Propagation checker may be used to view the propagation progress.

If propagation time is slower than expected, Nameserver caches may be flushed using any of the following:

  1. Google Public DNS
  2. OpenDNS
  3. Cloudflare