This guide is for clients managing their own DNS — keeping DNS at your registrar or another provider and entering records yourself. Most clients instead point their nameservers to us and let us manage everything; see Understanding DNS and How Bibliopolis Manages It. Either way, please coordinate changes with us so nothing breaks during your go-live.
Only touch the records below. Don't remove or modify your existing MX (email) records, or any other records unrelated to your website — this guide only concerns the A and CNAME records that point your site to us.
Set the TTL on these records to its lowest value, ideally 300 seconds (5 minutes), so changes propagate as quickly as possible. Changing the TTL itself can take 24–48 hours to propagate, so we often skip this step when launch timing is tight.
Step 1: Add four A records for yourdomain.com
Bibliopolis uses Fastly, a content delivery network (CDN), to serve your site quickly and reliably. To connect your domain to Fastly, add (or replace your existing A record with) these four A records:
| Host | TTL | Type | Value |
|---|---|---|---|
| yourdomain.com | 300 | A | 151.101.1.91 |
| yourdomain.com | 300 | A | 151.101.65.91 |
| yourdomain.com | 300 | A | 151.101.129.91 |
| yourdomain.com | 300 | A | 151.101.193.91 |
Having four A records is normal. This is how Fastly ensures reliability and performance across its global network.
Step 2: Update the CNAME record for www.yourdomain.com
- Find the record for
www.yourdomain.comand note whether it's an A record or a CNAME record. - Remove any existing A record for
www.yourdomain.comif one exists. - Create or update the CNAME record for
www.yourdomain.comand point it to:
n.sni.global.fastly.net
This routes all www traffic through Fastly for improved speed and reliability.
SSL / HTTPS
Once these records point to Fastly, a security certificate is provisioned automatically — there's nothing further to configure, and your visitors won't see a security warning during the switch. The only exception is if your domain uses DNSSEC, which can delay certificate issuance; let us know if that applies to you.
Notify us the moment changes are made. There may be a brief period of downtime during the transition, and our team will be standing by to resolve any issues right away. Email support@bibliopolis.com.
Prefer we handle your DNS for you? Email support@bibliopolis.com and we'll arrange access so we can make the changes for you — see Sharing Registrar Access with Bibliopolis.