Point DNS for a domain to WPVIP

Once a site is ready to launch, the DNS for a site’s new domain must be updated with the DNS provider and pointed at WPVIP for the site to be publicly available at that domain.

• DNS settings for ALIAS, ANAME, and A Record are provided for root domains.
• DNS settings for CNAME records are provided for subdomains. 
• WPVIP recommends using ALIAS records to route DNS for root domains whenever possible.

A different set of DNS records for a custom domain are required in order to send emails from a WordPress environment with the domain instead of the default email address  donotreply@wpvip.com.

Access

The DNS settings for a domain are available only after a domain has been added to the VIP Dashboard and verification for the domain has been successfully completed.

Domains have specific application and environment associations.

1. Navigate to the VIP Dashboard for the application that the domain is associated with.
2. Select the environment that the domain will point to (e.g., production, develop) from the dropdown located at the upper left of the dashboard.
3. Select “Domains & TLS” from the sidebar navigation at the left of the screen.
4. Select the “•••” button located to the right of the domain.
5. Select “DNS Instructions” from the overflow menu.
6. The “Setup your DNS” panel in the VIP Dashboard provides the values to point a domain to WPVIP using ALIAS, ANAME, or A Records for root domains, and CNAME records for subdomains. Select and copy a record value from the “Setup your DNS” panel and follow the instructions from the domain’s DNS provider to add or update a new DNS entry.

DNS propagation

Once the DNS settings for the domain have been updated with the DNS provider, the speed at which the updated DNS will fully take effect is dependent on the domain’s Time To Live (TTL). The dig command can be used to check the domain’s current DNS record TTL, and any updates to a domain’s TTL must be made with the DNS provider. DNS can take up to a full 24 hours to propagate around the world, and a service like DNS Checker can be used to track progress of propagation.

Confirm DNS settings

The status of a domain’s DNS settings are displayed in the column labeled “DNS”. If an unexpected DNS status is displayed, use the dig command to confirm the domain’s DNS settings and make sure that they match the values that were provided by WPVIP.

Command line

The  dig <domain>  command can be run in a terminal to confirm that the DNS is correctly pointed to WPVIP:

dig www.example.com

Output from the command will display settings for the domain’s ALIAS, ANAME, A record, or CNAME. The settings in the output should match the setting information provided for the domain in the VIP Dashboard.

VIP Dashboard

Each domain listed in the Domains panel of the VIP Dashboard will display one of the following status messages in the DNS column for the domain’s DNS settings:

• ⚠️ Unavailable: WPVIP’s status service is not available to respond.
• ❌ Route not detected: DNS is not pointed to VIP, and there is no route for an HTTP request. Updates to the domain’s DNS settings are needed for the domain to successfully point to WPVIP.
• ✅ Pointed to VIP: The domain’s DNS is successfully pointed to WPVIP
• ✅ Route found: The domain’s DNS is not pointed to VIP, but the x-powered-by HTTP response header added by WPVIP has been detected. This indicates that there is a route for an HTTP request. This status is often returned for domains that are assigned to a site with a reverse proxy configuration.