Manage DNS and website protection
Manage DNS records, proxying, website protection, origins, and SSL settings.
Connect your domain, protect your website and manage each setting
Start with what DNS, the proxy and Website Protection do. Then follow the steps for each feature, check the result, and learn how to recover safely if a change does not work as expected.
What is this service about?
DNS tells visitors where to find your domain's website, email and other services. The BlazingFast DNS manager lets you create a domain's DNS zone, manage its records and optionally route supported website records through the BlazingFast proxy and Website Protection service.
These are three different functions:
| Function | What it does | When to use it |
|---|---|---|
| DNS hosting | Publishes records such as website IP addresses, mail destinations and verification text. | Connect a domain to hosting, configure email or verify ownership with another service. |
| Proxy | Sends supported website traffic through BlazingFast before forwarding it to your backend, also called the origin. | Put the proxy between visitors and your website and manage the visitor-facing SSL certificate. |
| Website Protection / WAF | Applies supported security checks to traffic reaching the proxy. | Help filter unwanted website requests and use the available access controls. |
Adding a DNS zone does not register or transfer the domain, buy hosting, change your registrar's nameservers or automatically prove that a website is protected. The proxy is for supported website traffic; it is not a proxy for email, SSH or every DNS record type. It does not prevent direct access to an origin that remains publicly reachable.
Before you start
Have access to your BlazingFast account, your domain registrar and the correct hosting/backend IP address. Complete any billing-profile prompt in the portal. Changes may be unavailable for suspended or administrator-locked services.
Before moving an existing domain, save its current records, especially MX, SPF, DKIM, DMARC and verification TXT records. Record the previous nameservers and check whether DNSSEC is already enabled. Do not remove a working DNS service or signing configuration until the replacement has been prepared and checked.
The examples below use example.com and the documentation-only IP 203.0.113.10. Replace them with your own domain and real backend IP. Use the nameservers displayed in your portal rather than copying an address from an unrelated example.
1. Open the DNS manager and add a domain
Purpose: Create the DNS zone that will hold your domain's records.
- Sign in to the customer portal and open DNS at Manage DNS.
- On the Zones tab, select Add domain.
- Enter the registered root domain, such as example.com, without https://, a path or www.
- Select a Template if you want a saved starting layout, or leave it as None.
- Select Add and wait for the zone to become Active. Open the domain to manage its records.
Check: The domain appears in your Zones list and its DNS records page opens. A Creating or error state is not a completed setup; refresh once, then contact support if it remains unresolved. Do not repeatedly create duplicate zones.
Make BlazingFast authoritative for the domain
Purpose: Make public DNS use the records you manage here.
- Copy or import all required records into the new zone and check the website, mail and verification entries.
- Copy the authoritative Nameservers shown in the DNS manager.
- At the company where you registered the domain, replace the domain's nameservers with that exact set. Adding NS records inside the zone is not a substitute for this registrar change.
- If the old provider uses DNSSEC, coordinate removal or replacement of the parent DS records before changing providers. A stale DS record can make the entire domain fail DNS validation.
- Allow cached DNS answers and delegation information to expire, then verify that public lookups use the intended nameservers and records.
Check: Both authoritative answers and public lookups return the intended configuration. If the registrar still delegates to Cloudflare or another provider, editing this BlazingFast zone alone will not replace that provider's public DNS answers. An alternative external-DNS protection setup must follow the routing instructions supplied for that setup; do not guess proxy IP addresses.
2. Add DNS records
Purpose: Connect individual names to websites, mail servers and other services.
- Open the domain's DNS records tab and expand Add record if necessary.
- Select the record Type and enter its Name. Use @ for example.com, www for www.example.com, or ***** for a wildcard name.
- Choose the TTL, which controls how long DNS answers may be cached. The form offers 300, 600, 3600 or 7200 seconds.
- Enter the Content or the type-specific fields described below. For an A record, use Add IP address for additional IPv4 backends.
- For an eligible A record, choose whether Protect should be enabled. Disabled publishes the entered IP directly; enabled requests routing through the proxy.
- Select Add. Wait for the record and any protection state to finish updating.
| Record | What it is for | What to enter |
|---|---|---|
| A | A website or other hostname using IPv4. | Name @ or www; content your real IPv4 address, for example 203.0.113.10. |
| AAAA | A hostname using IPv6. | A valid IPv6 address. Do not assume an AAAA record is protected just because the A record is protected. |
| CNAME | An alias to another hostname. | For example, www pointing to example.com. Do not enter a URL or IP address. The zone apex @ cannot be a CNAME here. |
| MX | The server that receives your domain's email. | The mail provider's Priority and mail-server Target. Lower priority numbers are preferred. |
| TXT | SPF, DKIM, DMARC and ownership-verification values. | The exact text supplied by the service. Put DKIM and DMARC at their specified record names, not automatically at @. |
| NS | Delegation of a child DNS zone, or the zone's nameserver records. | Nameserver hostnames. Changing these records does not itself change registrar delegation. |
| SRV | Discovery of a service on a specific host and port. | Service-specific name, Priority, Weight, Port and Target supplied by the application. |
| CAA | Which certificate authorities may issue certificates. | The required Flags, Tag such as issue or issuewild, and authority Value. An overly restrictive CAA policy can prevent certificate issuance. |
Advanced types are also available. To add one, select its type in Add record, enter the parameters supplied by the responsible DNS or application administrator, then select Add:
| Advanced record | Purpose and required content |
|---|---|
| SSHFP | SSH host-key fingerprint: algorithm, fingerprint type and hexadecimal fingerprint. |
| TLSA | Certificate association for a named service: usage, selector, match type and association data. It requires a correctly designed DNSSEC/DANE setup. |
| DS / DNSKEY | Public DNSSEC delegation or key data. Use the DNSSEC tab for this domain's managed signing workflow; do not place its registrar DS record into this same zone. Child-zone delegation is a separate advanced use. |
| NAPTR / LOC | Application-specific service discovery or location data in the required DNS presentation format. |
| PTR | A reverse-name target. Public IP reverse DNS normally must be set by the IP provider; adding a PTR to your ordinary forward zone does not change that provider's reverse zone. |
SOA records are managed by the platform; SOA editing is disabled in this record editor. Do not replace system-managed signing records manually.
Check: The record appears under the intended type and name. Check its answer at the authoritative nameservers and again after cached answers expire. Preserve working email records when changing only website routing.
3. Edit or delete a DNS record
Purpose: Change an existing destination, correct a value or remove an obsolete record.
- Find the record on DNS records. Check its name and type carefully.
- Select the pencil icon, edit the TTL or content, then select the save/check icon. Use Cancel to discard an unfinished edit.
- For multiple A-record backends, use Add IP address or the remove-IP control, then save the whole edited record.
- To remove a record, select its trash icon. If a deletion countdown and Undo appear, use Undo before that countdown finishes to cancel it.
- Refresh and verify the final record state and the affected service.
Check: The saved value or deletion is visible after refresh. A successful save does not immediately remove answers already cached by visitors or resolvers. Deleting a record can break website, email or verification services that rely on it.
4. Import a zone or reuse a template
Import an existing zone
Purpose: Bring a domain's existing DNS records into BlazingFast without retyping every entry.
- Export the zone from the old provider in BIND zone-file format and keep the original export as a backup.
- In DNS → Zones, select Import zone.
- Paste the zone file. Include its $ORIGIN line, for example $ORIGIN example.com., so the domain can be identified.
- Review the detected domain and select Import. Correct any reported line or format errors rather than repeatedly submitting the same file.
- Open the resulting zone and check all records and protection states before changing registrar nameservers.
Check: Website, mail, verification and delegation records are present. Importing a zone file is not a promise that every imported address is protected or that registrar delegation has changed.
Create, edit or remove a template
Purpose: Save a reusable DNS layout for future domains.
- Open DNS → Templates and select Add template.
- Enter a template name and its Zone file (BIND format), then save it.
- When adding a new domain, choose that template in the Template field.
- To update your template, use its Edit template action and save the revised file. Existing domains do not automatically inherit later template edits.
- Use Hide template where available to remove it from your normal selection, Show hidden to find hidden entries, or Remove template for a personal template you no longer need. System templates may have different permissions.
Check: Test the template on the intended new zone and review generated hostnames and IPs. Templates are starting points, not backups of every existing domain.
5. Enable Website Protection and proxying
Purpose: Route an eligible website hostname through BlazingFast and apply its supported protection checks.
- Open the domain and check the Website Protection or Free website protection included status.
- Eligible BlazingFast hosting origins may have included protection. For other origins, use Get WAF or the displayed protection purchase option, review the current price and protected-domain capacity, and complete checkout if required.
- On DNS records, locate the website's A record and switch Proxy on. For a new A record, you can instead enable Protect when adding it.
- Switch Protection on if the record shows a separate protection control. It requires proxying to be enabled.
- Repeat for each website hostname you need, such as @ and www. Review the wildcard record separately; protecting one record does not automatically establish the state of every other record.
- Wait until the record reports Protection enabled and no pending or attention state remains.
Check: Public DNS routes the intended hostname through the supplied proxy addresses, and the site works over HTTP and HTTPS. The portal may continue showing your backend IP as the editable value while public DNS advertises proxy IPs; that is expected for a proxied record.
An active paid plan is an entitlement, not proof that every record has completed synchronization. Protection pending, Protection needs attention, or pending backends require review. Do not treat a saved setting with an incomplete synchronization error as a confirmed activation.
Turn protection off or return to direct DNS
Purpose: Stop security checks for a record, or stop routing it through the proxy.
- Note the current backend IPs and the current Proxy and Protection states.
- To change security checks while keeping proxy routing, use the record's separate Protection control where supported. Re-read the resulting state rather than assuming the proxy was removed.
- To publish the origin directly, switch Proxy off. Review the warning and final record state.
- If using a domain-level Disable Protection action, read its result carefully: that workflow can restore direct DNS. Do not assume it is identical to a record-level toggle.
- Check authoritative DNS and the website again, allowing for cached proxy addresses until TTL expiry.
Check: The observed route matches your intention. Direct DNS exposes the origin IP and sends visitors directly to its own TLS certificate. Disabling routing does not cancel a subscription; manage billing separately.
6. Change the backend/origin IP
Purpose: Keep a protected hostname connected to the correct server after a hosting migration or IP change.
- Obtain the new server's real IP and confirm that it serves this hostname correctly, including its intended HTTP/HTTPS behavior.
- In DNS records, edit the protected A record's backend IP values. Enter the origin IP, not a BlazingFast proxy IP and not a URL.
- Save the change and wait for synchronization to finish. Use the service's origin sync action only if that action is available in your service workflow or supported API integration; the DNS editor does not require a separate origin-sync button.
- If you entered multiple IPv4 backends, inspect their applied/pending state. A saved address is not necessarily an active backend, and a list of IPs alone is not a guarantee of health checking or failover.
- Check the real website through the proxy, including an important application path, and keep the previous origin available during the transition where possible.
Check: Protection remains enabled, no backend is unexpectedly pending, and requests reach the new server. Never point a protected backend back to its own proxy addresses; that can create a routing loop.
7. Configure SSL and HTTPS
Purpose: Choose the visitor-facing certificate and how the proxy connects to your origin.
- Find a proxied A record and select its gear / Configure icon.
- Open SSL. These settings apply to the selected hostname, not automatically to every record in the zone.
- Set Flexible SSL according to the origin: enabled uses HTTP from proxy to origin; disabled selects HTTPS to the origin. HTTPS to the origin requires a correctly working origin TLS setup. Do not assume this control represents a separately documented strict certificate-verification policy.
- Set Force SSL if visitors using HTTP should be redirected to HTTPS. Prepare and test HTTPS before enabling the redirect.
- Select and apply the required certificate option as described below. Toggle changes are saved through their own controls; certificate selection must also be applied.
Check: Test HTTP redirects and HTTPS without bypassing certificate validation. An encrypted visitor-to-proxy connection does not mean that the proxy-to-origin connection is encrypted when Flexible SSL is enabled. Incorrect origin redirects or scheme settings can cause redirect loops.
Use the automatic ECC certificate option
- In SSL, select BlazingFast Free SSL (the automatic ECC option) in Certificate and select Apply.
- Ensure that the hostname routes as required for certificate validation and that relevant CAA records allow the issuer. Automatic issuance is not guaranteed to finish immediately.
- Open the actual hostname over HTTPS and check the certificate name, chain and expiry date.
- Repeat verification for www or other hostnames. Do not assume an automatic single-host certificate covers a wildcard.
Upload and activate a custom or wildcard certificate
Purpose: Use a certificate and private key supplied by you instead of the automatic certificate option.
- Prepare a current certificate covering the selected hostname, its matching unencrypted PEM private key, and any required intermediate CA bundle. A wildcard certificate must actually cover the names you plan to serve; selecting Wildcard does not create one.
- Open Configure → SSL and choose Custom or Wildcard under Certificate.
- Paste the leaf certificate into Certificate, the intermediate chain into Bundle, and the matching key into Private key. Keep PEM BEGIN/END boundaries intact and on separate lines; do not join certificate blocks without a newline.
- Select Upload and apply. Wait for success, then reopen the settings and confirm the intended certificate mode. Uploading stored material without selecting/applying that mode is not enough to make it the served certificate.
- Verify HTTPS on the exact hostname, without ignoring certificate errors. Check the served certificate, hostname coverage, expiry and chain. Test every affected hostname separately.
Check: Browsers receive the intended certificate without a trust or name error. A self-signed certificate can be useful for a controlled test but is not normally trusted by public browsers. Keep a secure original copy of the key; Load existing may show available certificate details but must not be treated as a private-key recovery service. Never put a private key in DNS records, screenshots, tickets, chat messages or a public repository.
To return to the automatic option, select BlazingFast Free SSL, select Apply, and verify the served certificate again. Do not remove the working certificate until its replacement is confirmed.
8. Restrict access by IP address
Purpose: Use Whitelist as an access allowlist for a private website or an administration endpoint. This is not the same thing as blocking one attacking IP or bypassing every security check.
- Open the selected proxied record's Configure → Whitelist tab. Have the required public client IPs ready and keep the portal open.
- Enable Whitelist access only when you intend to restrict visitors. An empty or incomplete allowlist can block legitimate access; perform this change in a controlled window.
- Enter an IP / range / CIDR, for example 203.0.113.10, 203.0.113.0/24 or 203.0.113.10-203.0.113.20, and an optional Label.
- Select Add IP, then Refresh and confirm the entry appears. Repeat for every required client network.
- Test from an allowed address and from an address that should be denied. Use the row's remove action to delete obsolete entries, or turn Whitelist access off to remove this access restriction.
Check: Only the intended clients can reach the hostname under this policy. Mobile connections, VPNs and changing office IPs can affect access. Use the separate country-policy bypass control if you specifically want listed IPs to bypass a country rule; do not assume the allowlist overrides all other rules.
9. Configure country restrictions
Purpose: Allow or deny website access based on the visitor IP's detected country, for one proxied hostname.
- Open Configure → Country restrictions and wait for the saved rule to load.
- Select Disabled, Block selected countries, or Allow only selected countries.
- For either active mode, select at least one country under Countries.
- Choose When the visitor's country is unknown. If needed, enable Allow whitelisted IP addresses to bypass this country rule.
- Select Save country restrictions and wait for confirmed synchronization. Use Reload saved rule if the result is uncertain before submitting another change.
- Test the intended access and check your own access path. To remove the restriction, choose Disabled and save again.
Check: The saved rule is confirmed for the selected hostname. Allow-only mode denies visitors outside the selected countries and can block your own website access. Geolocation is not a person's verified identity; VPNs and proxies can affect it. Other security checks remain active.
10. Customize the loading page
Purpose: Change the page shown during supported protection/loading flows. It does not replace your website's homepage, application or origin error pages.
- Open the proxied record's Configure → Loading Page tab.
- Choose Custom Loading Page and enter your HTML in HTML. Keep the original version so you can roll back.
- Use the displayed preview where available and check that the content is readable. Do not include private credentials or use the page to replace required protection logic.
- Select Apply. Saving the HTML and enabling the custom-page mode are parts of the apply workflow.
- To revert, select Default Loading Page and select Apply again.
Check: The intended page is used when that loading flow is actually triggered. It may not appear on every ordinary website visit. If validation rejects the HTML, correct the reported issue rather than disabling protection to conceal it.
11. Review traffic and protection statistics
Purpose: Understand the recorded website traffic and compare behavior before and after a change.
- Open the domain's Stats tab.
- Select Last hour, Last 24 hours, or Last 7 days and use Refresh when needed.
- Review requests, bandwidth, blocked requests, average response time, cache-hit rate and server errors.
- Use the request/bandwidth charts and the WAF-decision, device/automation, country and HTTP-response breakdowns to locate the time and type of a problem.
- Read the coverage and freshness information before drawing conclusions or sharing a screenshot with support.
Check: Compare the same time window and relevant hostnames. HTTP 5xx errors are not automatically WAF blocks, and average response time is not backend-only latency. Empty or unavailable statistics do not prove that there was no traffic, that the website is down, or that protection is disabled. This panel is not a general cache-purge or arbitrary WAF-rule editor.
12. Enable or manage DNSSEC
Purpose: Sign DNS answers so validating resolvers can detect tampering. DNSSEC does not encrypt website traffic and does not replace SSL.
Domain registered elsewhere, DNS hosted here
- Confirm that the domain uses the managed authoritative nameservers, then open DNSSEC.
- Read the external-registrar notice and acknowledge that registrar setup is required.
- If available, select Enable zone signing. If activation is unavailable or no usable DS record appears, contact support rather than guessing a record.
- Copy the displayed public DS record into the DNSSEC/DS settings at your registrar, not into this same DNS zone's record list.
- Verify the parent delegation and DNSSEC validation after propagation. Zone signing enabled alone does not confirm that the registrar has published the matching DS.
To disable, first remove the DS at the external registrar and wait for cached DS records to expire before asking support to stop zone signing. Never stop signing while a live parent DS still requires it.
Domain registration managed through BlazingFast
- Open DNSSEC and select Check status to confirm support and the current state.
- Select Enable, read the dialog and confirm. For managed DNS, no manual private-key entry is required.
- If using external DNS, enable signing at that provider first and supply only its current public DNSKEY information requested by the dialog. Do not paste a private key or a DS digest into the public-key field.
- Wait for the background operation to complete and use Check status if the response is interrupted. Do not repeatedly submit an uncertain change or replace signing keys while reconciliation is pending.
- For disabling, use Disable and confirm the DS-removal operation. Keep DNS signing and keys active until parent DS records and cached copies have expired.
Check: Verify both signing and the parent delegation. A registrar status or an accepted request alone does not prove end-to-end DNSSEC validation or propagation.
13. Review history and restore a previous DNS state
Purpose: Understand a recorded change and recover the zone state that existed before it.
- Open DNS records → DNS change history and refresh or use Load more to find the relevant change.
- Review its time, status, changed records and available protection/backend details.
- Select Restore previous state on the intended entry and read the confirmation carefully.
- Confirm only when you intend to restore the entire zone to the state before that change. This can replace later unrelated edits, not just one selected record.
- Wait for the result, review the new history entry, and verify DNS, protection, backend IPs and website/email behavior.
Check: Current protection eligibility is rechecked. Older history without complete protection details may require manual recovery. History is not a backup of your website files, database, registrar settings or every SSL/access-policy change.
14. Remove a domain's DNS zone
Purpose: Remove DNS hosting for a domain you no longer manage here.
- Export or securely record anything you must retain, and prepare another DNS service if the domain is still in use.
- Move and verify registrar delegation before deleting a zone that still serves live traffic. Coordinate DNSSEC DS records as part of the move.
- In DNS → Zones, use the domain's Remove domain / trash action. Cancel with Undo if a countdown is displayed and you selected the wrong domain.
- Verify the final state and the replacement DNS service.
Check: Removing DNS hosting does not unregister the domain, delete a hosting account or automatically cancel a paid protection subscription. It can interrupt any service that still depends on the removed records.
After any change: verify and troubleshoot
- Refresh the portal and confirm the saved state. Do not rely solely on a success notification.
- Check authoritative DNS and then public DNS, allowing for TTL/delegation caching.
- Test the actual hostname over HTTP and HTTPS, plus an important application path. A 200 response at the homepage does not prove that every path works.
- For proxy changes, confirm that the real origin is correct and no protection/backend synchronization remains pending. Check IPv6 and other DNS records for unintended direct routes.
- For SSL, check the served certificate's hostname, chain and expiry without ignoring browser warnings.
If a page remains Creating, a protection change reports incomplete synchronization, or a request times out, refresh/check status before retrying: part of the operation may already have been saved. Do not repeatedly delete and recreate the domain, weaken SSL verification or switch off protection as a diagnostic shortcut.
For support, provide the domain/record, approximate time and timezone, action attempted, exact visible error and a redacted screenshot. Never include a private key, password, API key or unredacted request body. For automation and advanced raw-zone/rrset or service-origin-sync operations, use the current DNS/WAF API reference and a suitably scoped API key; those API features are not additional buttons in the DNS record editor.
On this page