You've created your first redirect and redirect.pizza now asks you to change the DNS of your domain. This article explains what that change does, where to make it and what to expect afterwards.
Why DNS?
DNS (Domain Name System) tells the internet which server handles a domain. For redirect.pizza to redirect example.com, the DNS of example.com must point at our edge network. Until it does, requests for the domain keep going to wherever they went before, and we never see them.
The DNS change is the only thing you need to do outside redirect.pizza. Everything else, including the SSL certificate, is handled on our side.
Which records to add
After you create a redirect, the required records are listed under Hostnames in your account. Depending on the hostname you add one of these:
- A CNAME record pointing to
edge.redirect.pizza. Use this for every subdomain, such aswww.example.com. It automatically includes IPv6 and stays correct if our IP addresses ever change. - An A record pointing to
89.106.200.1, optionally with an AAAA record for2a12:5240::1. Use these for the apex (non-www) domain, such asexample.com, because DNS doesn't allow a CNAME there.
See What DNS types can I use? for the full list, including the records for email forwarding.
Where to make the change
DNS records are managed by your DNS provider. In most cases that's the company where you registered the domain, such as GoDaddy, Namecheap or TransIP. If you use external nameservers, such as Cloudflare, make the change there instead.
Not sure where your DNS is hosted? Look up the nameservers of your domain with a tool like WhatsMyDNS. The nameservers tell you which provider is in charge.
We have step-by-step walkthroughs for popular providers, such as GoDaddy, Namecheap and Cloudflare. You'll find the full list on the support page. On the Pro plan and up, automatic DNS can apply the records for you.
After the change
DNS changes can take up to 24 hours to propagate, although it's usually much faster. redirect.pizza keeps checking and shows a green checkmark once the records are detected. The SSL certificate follows shortly after.
Once verified, your browser may still show the old website for a while because of caching. See Troubleshooting new redirects.