Changed nameservers at BPServ three days ago, WHOIS still shows the old ones

Sorry if this is the wrong board, the domains threads all seem to be about which registrar to pick rather than problems with one, and this is a problem with one.

Some background. I moved one name to BPServ about a month ago because I wanted the domain and the box at the same shop and their VPS side has been fine for me. Registration went through with just an email, paid in Litecoin, thirty dollars for the .com, all straightforward and honestly easier than the mainstream registrar I came from.

On Monday I changed the nameservers in their panel because I moved the site. Panel shows the new ones. Public WHOIS still shows the old ones three days later, and the site is still resolving to the old box. I have raised a ticket and had nothing back.

Is three days normal for them? Or have I done something wrong in the panel that it is not telling me about? Thank you to anyone who takes a look.

Two different things and you are watching the wrong one.

The registrar's WHOIS output and the actual delegation at the TLD registry are separate systems and they update on separate schedules. WHOIS lag of a day or two means nothing. What matters is which nameservers the gTLD servers hand out, because that is what the world resolves against.

# ask the registry, not the registrar's web page
dig +trace NS example.com | tail -n 6
dig @a.gtld-servers.net NS example.com +norecurse +short

If the registry is already handing out the new pair, your change is live and you are looking at cached records plus a stale WHOIS page. If the registry still has the old pair after three days, the change never left their panel and the ticket is the only route.

Sorry, what is the difference between those two exactly?

WHOIS is a description of the record. Delegation is the record doing its job.

Think of WHOIS as the registrar's printout of what it believes, updated whenever it feels like it, and the gTLD nameservers as the thing every resolver on earth actually asks. The printout can be wrong for days without anything being broken. If the second command comes back with your new nameservers, you are fine and it is only cache.

Thirty dollars for a .com from an operator whose HQ is not published anywhere. Bold.

Update, and not a good one. The registry command still shows the old nameservers, so the change genuinely did not leave their panel. Ticket is now on day six with no reply at all.

I did read the warnings about pre-testing this operator with a low-value name before putting anything real there and I now understand why people write that. This was a low-value name, at least. Leaving it unsolved because it is not solved.