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 VIP for the site to be publicly available at that domain.
VIP recommends using
ALIAS records to route DNS for root domains whenever possible.
- Navigate to the VIP Dashboard for the application that the domain is associated with.
- Select the environment that the domain will point to (e.g., Production, Develop) from the dropdown located at the upper left of the dashboard.
- Select the “Domains” panel option at the left.
- Select the “•••” button located to the right of the domain.
- Select “DNS information” from the overflow menu.
- The “Setup your DNS” panel in the VIP Dashboard provides the values to point a domain to VIP using
A Records for root domains, and
CNAMErecords 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.
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 are correctly updated
dig <domain> command can be run in a terminal to confirm that the DNS is correctly pointed to VIP:
Output from the command will display settings for the domain’s
A record, or
CNAME. The settings in the output should match the setting information provided for the domain in the VIP Dashboard.
Each domain listed in the Domains panel of the VIP Dashboard will display one of the following status messages in the DNS & ROUTE STATUS column for the domain’s DNS settings:
- ⚠️ Status unavailable: VIP’s status service is not available to respond.
- ❌ Route to VIP 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 VIP.
- ✅ DNS pointed to VIP: The domain’s DNS is successfully pointed to VIP
- ✅ Route to VIP available: The domain’s DNS is not pointed to VIP, but there is a route for an HTTP request. This status is often returned for domains assigned to a site with a reverse proxy configuration.