DNS is the part of your website that nobody looks at until it breaks. It turns a domain name into the servers that run your website, email and customer links. When a record is wrong, a domain lapses or an old agency still controls the account, the website can disappear, email can stop and customers can be sent to a server you do not control.
DNS security is therefore less about one product and more about a short operating routine: who can change records, what is published, how changes are reviewed and how quickly an unwanted change is noticed. This guide sets out that routine for a small or mid-sized business in Bangladesh.
What DNS security covers
- Registrar control: the account that owns the domain, its recovery email and who can transfer it.
- Authoritative DNS: the service that publishes your records and answers queries.
- Record hygiene: only the records you need, pointing where you expect.
- DNSSEC: cryptographic proof that a response came from your zone and was not altered.
- Email authentication: SPF, DKIM and DMARC, which protect your domain from spoofing.
- Monitoring: alerts when records, certificates or resolution change.
- Encrypted DNS: DNS over HTTPS or DNS over TLS for clients that support it.
Prerequisites before you change anything
- Proof that you control the domain, and the legal name of the owner on the registration.
- Access to the registrar account and the current DNS host, with a second administrator who is not the original agency.
- A list of every domain and subdomain the business uses, including campaign domains and old brands.
- An inventory of services that depend on DNS: website, email, payment links, verification records, VPN and internal tools.
- A maintenance window and a rollback plan. DNS changes can take time to propagate, so do not start at the busiest hour.
Step-by-step configuration
1. Build the domain and subdomain inventory
List every domain the business owns, then every hostname under it. Include www, shop, api, mail, vpn, staging hosts and any subdomain created for a campaign or a supplier. Mark which ones are active, which redirect and which are unknown. The unknown ones are the ones to investigate first.
2. Lock down the registrar account
The registrar is the highest point of control. Enable multi-factor authentication, remove shared logins, give each person their own account and use the least privilege available. Turn on registrar lock or transfer lock, keep the recovery email on a monitored company mailbox, and confirm that the billing contact still works. If an agency registered the domain in its own name, fix the ownership before anything else.
3. Choose who hosts DNS deliberately
Decide whether DNS is hosted by the registrar, a cloud provider or a specialist DNS service. What matters is administrative control, reliability, audit logs, API access and support for the record types you need. A free DNS zone tied to an agency account is a business risk, even when the website works.
4. Export and document the zone
Export the current zone file or take a complete screenshot of the record list. Record the type, name, value and TTL for each entry. Note the business purpose beside every record. This document becomes the baseline for reviews and the reference for rollback.
5. Remove stale and dangerous records
Delete records that point to retired servers, old hosting accounts or decommissioned software. Pay particular attention to CNAME records that point at a service the business no longer uses: if the target can be claimed by someone else, the subdomain can be taken over. Avoid wildcard records unless there is a clear reason, because they make every accidental hostname resolve. Add a CAA record if you want to limit which certificate authorities may issue certificates for the domain.
6. Authenticate email properly
Publish one SPF record that lists the services allowed to send mail, and keep it within the lookup limits in the SPF specification. Configure DKIM signing for each sending service and rotate keys on a schedule. Start DMARC with a monitoring policy, read the aggregate reports, then move to quarantine and eventually reject. Email authentication protects the brand even when the website is unaffected.
7. Enable DNSSEC with a rollover plan
DNSSEC adds a chain of trust from the registry to your zone. Enable it at the DNS host, publish the DS record at the registrar, and test validation with a public resolver. Ask how key rollover works before you enable it. DNSSEC without a rollover plan can make the domain unresolvable if a key expires or a provider changes.
8. Control time-to-live values
Use short TTLs before a migration and longer TTLs in steady state. A very low TTL increases query volume; a very high TTL slows recovery from a bad change. Document the standard for each record type rather than letting each administrator choose.
9. Add monitoring, redundancy and change control
Use at least two authoritative name servers, preferably on different networks, and restrict zone transfers to known secondaries. Monitor resolution from outside your network, certificate expiry, record changes and DNSSEC validation. Require a second person to approve changes to the apex, mail and payment-related records, and keep a change log with the ticket, approver and rollback value.
Evidence checklist
- Registrar inventory with owner, MFA status and lock status.
- Exported zone file and a business-purpose note for each record.
- SPF, DKIM and DMARC records with a screenshot of a test message passing.
- DNSSEC validation result from an independent resolver.
- Change log for the last two quarters, including approvals.
- Alert configuration and a test alert that reached the on-call person.
Common mistakes
- Letting the web agency own the domain and the DNS account.
- Using a personal email address as the registrar recovery contact.
- Publishing multiple SPF records or exceeding the lookup limit.
- Pointing a CNAME at the zone apex, which is invalid for standard DNS.
- Enabling DNSSEC and forgetting the DS record or the rollover date.
- Leaving old staging and campaign subdomains online indefinitely.
- Making changes without recording the previous value.
Metrics that show the routine is working
Track the percentage of domains with MFA and registrar lock, the percentage of records with a documented owner, DMARC enforcement coverage, the number of stale records removed, the time from an unauthorised change to detection, and the share of email that passes authentication. Review these monthly; they are more useful than a one-time audit certificate.
Where this fits in our work
DNS sits inside the wider managed technology stack: identity, endpoints, cloud accounts and websites. If you need help with the operating routine, start with Managed Technology & Cybersecurity and review the scope options on our pricing page. For the website side of the same problem, read the website malware cleanup and prevention checklist.
Sources
- NIST SP 800-81 Rev. 3, Secure Domain Name System (DNS) Deployment Guide, accessed 17 November 2026.
- ICANN, "DNSSEC - What Is It and Why Is It Important?", accessed 17 November 2026.
- CISA, "Encrypted DNS Implementation Guidance", accessed 17 November 2026.
- IETF RFC 4033, "DNS Security Introduction and Requirements", accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.