How Long Does Porkbun DNS Take to Propagate?

Porkbun sets a short default TTL, so record edits tend to propagate quickly — often within roughly ten minutes rather than hours.

Default TTL
600 seconds (10 minutes) by default
Record edit
around 10 minutes for a typical record edit
Nameserver change
up to 24–48 hours for a nameserver change

Porkbun's DNS defaults to a 600-second TTL, which is shorter than the one-hour default some larger registrars use. That means a resolver will only hold a cached answer for about ten minutes before checking again, so editing an A record or adding a TXT string on Porkbun usually becomes visible fairly quickly across most locations. You can shorten the TTL further for a planned change, or raise it once things are stable to reduce load.

The exception, as everywhere, is changing your domain's nameservers — moving DNS management to or from Porkbun's default nameservers. That delegation is cached by the TLD registry and can take up to a day or two to propagate fully, regardless of how short your record TTLs are. If you are pointing the domain at an external host's nameservers, plan for that longer window and keep records consistent during the transition.

Porkbun also offers a straightforward interface with sensible defaults, so most propagation questions come down to the TTL you can see next to each record. If a change is not showing after well past the TTL, check that the domain is still using Porkbun's nameservers and that you edited the record under the correct domain, rather than assuming the delay is normal.

Porkbun-specific notes

Check if your Porkbun change has propagated

Rather than guessing, query your record from many locations at once and watch propagation in progress.

Check DNS propagation

Frequently asked questions

How long does Porkbun DNS take to propagate?
With Porkbun's default 600-second TTL, most record edits are visible within about ten minutes. Nameserver changes can take up to 48 hours.
Can I make Porkbun changes propagate even faster?
Yes. Lower the record's TTL below 600 seconds a little before you make the change, then raise it again once the new value is stable.