Go BackFleek.co

Release Update - New DNS Configuration with CDN Perks & DDOS Protection

New upgrade coming for everyone hosting sites/apps on Fleek using custom DNS domains! You can now upgrade your site to our new DNS configuration to unlock extra CDN benefits, DDOS protection, and faster routing. Courtesy of Bunny CDN 😎

Our New DNS Configuration

We’re upgrading our custom DNS domain infrastructure to move away from HAProxy, and transition to using BunnyCDN so that we can supercharge all Fleek sites with extra CDN features, security, and a layer of redundancy when it comes to high-availability and 24/7 uptime.

The most important perks this change brings is adding a powerful and scalable anti-DDOS for all of our Fleek users, no matter their site’s size or plan, protecting their sites and apps automatically from all DDOS variants, without compromising their uptime or deliverability.

But, there’s more perks other than security. Bunny expands our CDN perks with a redundant perma-cache layer that ensures, even in the worst scenarios, your site will be up and their files served in the most optimized way possible, re-routing requests in real-time to avoid downtimes or inefficient requests.

Expect faster, and meaner sites on Fleek, since every single one of them will be enhnanced with these CDN perks⚡

Important: This new DNS configuration requires ANAME record support by the DNS service/provider where you have acquired and manage your domain. Make sure it does so before migrating, or move to a new provider if necessary.

Migrating Your Site to the New DNS ⚡

If you already have a site on Fleek, you need to migrate it from the dashboard to the new DNS configuration to take advantage of these new features. It only takes a minute!

If you are hosting a new site or app on Fleek, you don’t have to do anything but configure your DNS domain when you create it, since this new infrastructure is now the default setup for all newly created sites.

This new DNS configuration will deprecate the previous one, and custom domains using the legacy proxy/DNS will stop working by May 31st. If your site is using a DNS custom domain, update its settings now to avoid any performance issues, and have your site continue to work after May 31st.

Migrating Your DNS Configuration

Log into your Fleek account, and do this for every site that uses a custom DNS domain. Visit the hosting tab, and click on a site on the list to get started.

Once inside a site’s detail view, visit the SETTINGS tab and there, look for the Domain Management tab on the vertical sub-menu.

There, you will see the Custom Domains section, showing the Custom DNS Domain name you previously set up and connected to your Fleek site/app. Click on the “Upgrade DNS Configuration” button to re-configure your site.

In a nutshell, you will need to update your records on your DNS domain. This is because your custom domains needs to point to Fleek’s new upgraded infrastructure.

Root domain names (like space.storage) will ask for an ANAME record, whereas any subdomain or www. domain (like www.space.storage) will use CNAME.

What about DNSLink domains? Those will continue to point to your Fleek-assigned subdomain using a CNAME record, so keep them that way for now.

Remember that to utilize this, it is required that your DNS provider supports ANAME records. Check this before starting the upgrade. In some providers like Cloudflare, ANAME records are set as CNAME, so do check first with your provider’s documentation.

Once you have updated your record on your DNS provider, come back to Fleek to Verify the DNS Configuration. That is all! Your site will be updated to our new faster, and safer, DNS configuration.

What if my provider doesn’t support ANAME/ALIAS records?

Some providers, like Google Domains and GoDaddy don’t support ANAME/ALIAS records. To resolve this, the quickest option is to change your domain’s nameserver to point to Cloudflare and manage your DNS settings in Cloudflare.

This doesn’t mean you’re transfering your domain, you are only managing your DNS settings through Cloudflare, since it supports ANAME/ALIAS records. They need to be set as CNAME in Cloudflare, but they are auto-detected, and work just as fine.

Need an in-depth guide on how to do this? Check this article out! In short, you need to:

  1. Create a Cloudflare account.
  2. Configure your Domain in your old DNS provider to point to Cloudflare’s nameserver.
  3. Use Cloudflare’s DNS app to add your Fleek site’s DNS records, as shown above.
  4. Disable the Orange Cloud setting (HTTP proxy) on all records on Cloudflare.

That’s all, go back to Fleek’s domain management setting and verify your domain. Don’t forget to disable the Orange Cloud setting on Cloudflare. Else, your domain on Fleek will fail verification. This is how your DNS records should look like on Cloudflare. To disable the cloud, edit the record and click on the Orange Cloud on each record.

Wrapping it Up 🗞️

That is all for today! This week we are taking extra care on strengthening and scaling our hosting features to give maximum reliability to all the amazing users coming into the platform. Expect more news on this soon!