You've created your first redirect, awesome! But now this DNS thing appears..
DNS changes are necessary for letting the internet know where the server is for your domain. For example, when using redirect.pizza, we want to let the internet know example.com can be found at location 89.106.200.1. We do this by making DNS changes on the domain in question.
These DNS changes need to be made at your domain provider. In most cases, this can be done with your domain registrar. Examples of these are GoDaddy, Hover etc. If you use external nameservers (Cloudflare for instance), you need to make the changes there.
Unsure where your DNS is hosted? A good way to check this is to see where your nameservers point. You can check this with an online tool like WhatsMyDNS: https://www.whatsmydns.net/#NS/example.com
When you've set-up the redirect in your account, the required DNS changes are visible under the 'Hostnames' tab.
Both CNAME and A types are valid options. We recommend using CNAME for everything, except for non-www (apex) records, as DNS doesn't allow using CNAME's on the non-www aspect.
A big plus of using the CNAME is automatic IPV6 support and that it's always up-to-date if there ever is an IP change. View more info about the available DNS record types here.
Made the necessary DNS changes? It may take up to 24 hours before these changes are fully propagated! Please be patient. Once the DNS is verified, you still might run into browser cache when testing. See Troubleshooting new redirects
