# Manage DNS and website protection



Source: https://docs.blazingfast.io/howto/services/dns-waf-and-proxy-management



Manage DNS records, proxying, website protection, origins, and SSL settings.



## Know whether you are changing DNS or protection settings

DNS records and protected-record settings are related, but they are different controls. This guide helps you choose the right place to make each change.

[Domains and DNS zones](https://docs.blazingfast.io/howto/services/domains-and-dns-zone-operations)

# DNS, WAF, and proxy management

This area combines DNS zone management with service-level proxy and protection actions. DNS records and protection settings are related, but they are not the same workflow.

## DNS capabilities available now

- Create, view, and delete DNS zones.
- Use DNS templates when you want a repeatable starting point.
- Manage records through simple record helpers or lower-level rrset updates.
- Read or update raw zone content when a full zone-file style workflow is the right fit.

## Service protection capabilities available now

- Check whether a specific service is eligible for DNS proxy or WAF-related actions.
- Read the current protected-record state for a service-scoped record.
- Toggle proxy mode for that record.
- Toggle protection for that record.
- Run origin sync so the protected record follows the service's current origin IP.
- Read and change supported proxy settings such as SSL mode, force SSL, or custom loader behavior.
- View or upload SSL material and custom loader content where that protected-record workflow is enabled.

## What this does not cover

The portal exposes record-level protection and proxy configuration. It is not a general custom WAF rule builder, so incident runbooks should be based on the controls that are actually available here.

## Operating guidance

- Decide whether a change belongs in DNS, in the protected record configuration, or in the origin service itself before you touch production traffic.
- Use templates for repeated DNS layouts.
- Re-run origin sync after service rebuilds, migrations, or IP changes.
- Treat custom SSL or loader uploads as controlled changes with rollback notes.