Linking your developments to public domains and subdomains can be a difficult, error-ridden and slow process. Here's how you can fix this with now, step by step:
| Host | IP | IPV6 |
|---|---|---|
| a.zeit.world | 96.45.80.1 | 2600:180a:1001::1 |
| b.zeit.world | 46.31.236.1 | 2600:180b:2001::1 |
| c.zeit.world | 43.247.170.1 | 2600:180c:3001::1 |
| d.zeit.world | 96.45.81.1 | 2600:180a:4001::1 |
| e.zeit.world | 46.31.237.1 | 2600:180b:5001::1 |
| f.zeit.world | 43.247.171.1 | 2600:180c:6001::1 |
When you deploy and subsequently run now alias we:
ALIAS or CNAME records.www)Let's say you want to deploy a Node.js app. First, you would deploy with
▲ nowThat will give you a URL to your new deployment (or list with now ls). Then run:
▲ now alias <deployment> <target domain>And you're set! now alias will verify the ownership of your domain and automatically configure it.
Additionally, you can manage DNS records with the now dns command.
For example, this is how you can add a MX record.
▲ now dns add my-app.com @ MX mail.awesome-now.us 10ALIAS or CNAME manually.We wrote a series of benchmarks against the legacy [city].zeit.world and deployed them to 12 major locations around the world. The result? Up to 28x faster DNS lookup performance.