I don’t use porkbun so I can’t guide you in detail. But look for “glue records”. Some will just call this nameservers, ns record, or some other confusing and ambiguous lingo (like GoDaddy…). Glue records are separate from rest of the auth DNS servers. Even though you are essentially doing an A record.
So if you have example.com on porkbun, and auth nameservers for this same domain is going to be elsewhere, you can set glue records. Like…
I don’t use porkbun so I can’t guide you in detail. But look for “glue records”. Some will just call this nameservers, ns record, or some other confusing and ambiguous lingo (like GoDaddy…). Glue records are separate from rest of the auth DNS servers. Even though you are essentially doing an A record.
So if you have example.com on porkbun, and auth nameservers for this same domain is going to be elsewhere, you can set glue records. Like…
ns1.example.com ns2.example.com
With specific IPs like 123.123.123.123
This will allow you to essentially do the first step and not end up in a cyclic problem of one requiring the other.
I assume this is what you’re referring to as the problem.