How to point your DNS to Auware's vanity domain server

To use a vanity domain with Auware, you need to create a DNS A record that points your domain to Auware’s redirect server. This tells the internet to send visitors to Auware when they type your domain into their browser.

The IP address you need is: 164.90.134.34

After saving the DNS change, propagation typically takes 5 to 30 minutes, though it can occasionally take up to 48 hours depending on your registrar and DNS provider.

Below are step-by-step instructions for the most common domain registrars. If your registrar is not listed, the general process is the same - find the DNS management section, add or edit an A record for the root domain (@), and set the value to 164.90.134.34.

GoDaddy

1. Log in to your GoDaddy account and go to My Products
2. Find the domain you want to use and click the DNS button (or Manage DNS)
3. In the DNS Records section, look for an existing A record with Name set to @ (the root domain)
4. If an A record for @ exists, click the pencil icon to edit it. Change the Value field to 164.90.134.34
5. If no A record for @ exists, click Add Record, select Type A, set Name to @, and set Value to 164.90.134.34
6. Set the TTL to 1 Hour (or the lowest option available)
7. Click Save

GoDaddy’s official DNS help: https://www.godaddy.com/help/manage-dns-records-680

Namecheap

1. Log in to your Namecheap account and go to Domain List
2. Click the Manage button next to your domain
3. Go to the Advanced DNS tab
4. In the Host Records section, look for an existing A Record with Host set to @
5. If one exists, click the pencil icon and change the Value to 164.90.134.34
6. If none exists, click Add New Record, select A Record, set Host to @, and set Value to 164.90.134.34
7. Leave TTL set to Automatic
8. Click the green checkmark to save

Namecheap’s official DNS help: https://www.namecheap.com/support/knowledgebase/article.aspx/319/2237/how-can-i-set-up-an-a-address-record-for-my-domain/

Cloudflare

1. Log in to your Cloudflare dashboard and select the domain
2. Click DNS in the left sidebar, then click Records
3. Look for an existing A record with Name set to @ (shown as the domain name)
4. If one exists, click Edit and change the IPv4 address to 164.90.134.34
5. If none exists, click Add Record, select Type A, set Name to @, and set IPv4 address to 164.90.134.34
6. Important: Set the Proxy status to DNS only (click the orange cloud icon so it turns gray). Auware needs direct connections to your domain for automatic SSL certificate provisioning. If the proxy is enabled, the DNS check in Auware will show “DNS Mismatch” because Cloudflare’s IP addresses will resolve instead of Auware’s.
7. Click Save

Cloudflare’s official DNS help: https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/

Google Domains (now Squarespace Domains)

1. Log in to your Google Domains or Squarespace Domains account
2. Select the domain you want to configure
3. Go to the DNS section (in the left sidebar or under Settings)
4. Under Custom Records (or Resource Records), click Manage Custom Records
5. Add a new record with Host Name set to @ (or leave blank for the root domain), Type set to A, and Data set to 164.90.134.34
6. Click Save

Using a subdomain instead of the root domain

If you want to use a subdomain like go.mybrand.com or shop.mystore.com instead of the root domain, the process is the same except you set the Host or Name field to your subdomain prefix (go, shop, etc.) instead of @.

Verifying your DNS is configured correctly

After saving your DNS changes:

1. Go to Auware and open Settings, then click the Vanity Domains tab
2. Your domain should show a DNS status. If it says “DNS Verified” with a green checkmark, your domain is ready to use
3. If it says “DNS Pending,” the change has not propagated yet. Wait a few minutes and click the refresh icon to check again
4. If it says “DNS Mismatch,” your A record is pointing to the wrong IP address. Go back to your registrar and verify the value is 164.90.134.34

Troubleshooting

If your DNS has not propagated after an hour:

• Make sure you edited the A record for the root domain (@), not a subdomain or a CNAME record
• Check that there is no conflicting CNAME record for the same host name - CNAME and A records cannot coexist on the same name
• If using Cloudflare, verify the proxy is set to DNS only (gray cloud, not orange)
• Try clearing your local DNS cache. On Mac, run: sudo dscacheutil -flushcache. On Windows, run: ipconfig /flushdns
• Some registrars take longer to propagate. If everything looks correct, simply wait and check again later