VulCode
A company domain: transfers, DNS and propagation time
Technology

A company domain: transfers, DNS and propagation time

How a .pl domain moves to another registrar, how long a change of DNS servers can take, and why propagation is really just servers caching answers

DualFroz - VulCode CEODualFroz - VulCode CEO·19 November 2026·2 min read

Moving a .pl domain to another registrar takes three steps. The current registrar releases the authinfo code, the new one starts the transfer with it, and NASK, the .pl registry, emails a link to the holder's address in the register; the transfer completes only when the link is clicked. It can start no earlier than 5 days after registration or the last transfer, and an active Registry Lock must be switched off first. If the register holds an ex-employee's or old agency's address, the link goes there.

How long a DNS change can take

ChangeCan take up to
new DNS servers for a .pl domain24 hours, the NS record TTL in the .pl zone
new DNS servers for a .com domain48 hours, the NS record TTL in the .com zone
a new address in an A recordthat record's TTL in your zone

Propagation is caching

DNS does not push changes across the internet. A server that looked up a domain keeps the answer for the record's TTL (RFC 1035) and only then asks again, so some users see the new address at once and others after the TTL runs out. So before moving a site we lower the TTL to a few hours at least a week ahead and move the MX, SPF and DKIM records with the email. When we host, the domain, server, SSL certificate and monitoring are on our side; taking over maintenance from another vendor, we move the domain, server and outside services into your company's name.

Email records are covered in our SPF, DKIM and DMARC post, and hosting with a domain on our maintenance page.