dig +dnssec yourdomain.com @8.8.8.8
Look for a `SERVFAIL` status or `ad` flag missing in the response. To confirm, test against a non-validating resolver:
dig yourdomain.com @1.1.1.1
If the second command works, DNSSEC is the culprit. Log in to your new registrar's control panel and check their DNSSEC management section. You have two solutions: either disable DNSSEC entirely at the new registrar if they don't support it, or properly configure it by generating new keys and submitting the current DS records to your new registrar to publish at the registry level.
This is a public discussion. Create a free account to answer. Takes 20 seconds. No email gates.