How to Set Up DNS for a .bd Domain: A Practical Guide

DNS is the layer that turns your domain name into an actual destination. Get it right once and you never think about it again; get it wrong and your site is unreachable while everything looks correctly configured.

This guide explains DNS for .bd domains without assuming you already know the jargon — what each record type does, when to use which, and how to tell the difference between a real problem and a cache that hasn't caught up.

The mental model

Three things sit in a chain:

1. The registry (BTCL) knows your domain exists and knows which name servers are authoritative for it.
2. The name servers hold your actual DNS records — the instructions saying "web traffic goes here, email goes there".
3. Resolvers around the world ask the name servers for those records and cache the answers for a while.

So there are two distinct kinds of change. Pointing your domain at a different set of name servers is a registry-level change and is slow. Editing a record inside your existing name servers is fast.

The record types you will actually use

Pointing your domain at a website

The standard setup for example.com.bd hosted on a server with a fixed IP:

@ means the root domain itself. The www CNAME means you only ever have to update the IP in one place.

If you're on a platform that gives you a hostname rather than an IP (Vercel, Netlify, a managed WordPress host), follow their instructions instead — usually a CNAME on www and either an A record or a provider-specific alias on the root. There's a fuller walkthrough in how to point your .bd domain to your hosting.

Setting up email records

Email needs MX records to say where mail is delivered, and TXT records to prove your mail is legitimate:

Lower MX priority numbers are tried first. Your mail provider will give you the exact values — don't guess them. The full email setup is covered in setting up professional email on a .bd domain.

TTL: the number that controls how fast changes apply

TTL (time to live) tells resolvers how many seconds to cache a record. A TTL of 3600 means a resolver may serve the old answer for up to an hour after you change it.

The practical trick:

1. A day before a planned migration, drop the TTL on the records you'll change to 300 (five minutes).
2. Wait for the old, longer TTL to expire so resolvers pick up the short one.
3. Make the change. It now propagates in minutes rather than hours.
4. Afterwards, raise the TTL back to 3600 or higher.

How long does propagation actually take?

• Editing a record inside your existing name servers — minutes to a few hours, bounded by the TTL.
• Changing name servers — allow up to 24–48 hours for full global propagation, though most resolvers update far sooner.

"Propagation" is really just caches expiring at different times in different places. That's why a change can look live on your phone's mobile data and stale on your office Wi-Fi.

Common DNS mistakes on .bd domains

• Changing name servers and forgetting the records. The domain goes dark because the new name servers are empty.
• Trailing dots. Some panels want mail.example.com.bd. with a final dot; others add it for you. Copy the format your panel shows in its existing records.
• Duplicate SPF records. A domain must have exactly one SPF TXT record. Two will fail validation and hurt deliverability.
• Leaving the domain unverified. DNS can be perfect and the site still unreachable if the domain has been suspended for missing documents — see documents required.

Managing DNS at get.bd

DNS management is included free with every .bd domain — A, AAAA, CNAME, MX, TXT and NS records, edited from the client area with no extra charge. If you'd rather run DNS elsewhere, just point the name servers at your provider and manage records there; the registration stays with BTCL either way.

Not registered yet? Search your name or start with how to register a .bd domain.