It looks like that cors error was actually masking a DNS resolution error. That's on me, my resolver seems to have trouble. Weird how nostr.land resolved but api.nostr.land failed to resolve. Are you hosting them on different nameservers?
Discussion
Yes, the api.nostr.land domain hits another NS.
Got it. Sorry about that confusion. I didn't know dns would appear as a cors error.
It normally shouldn’t. I suspect something is going on with your DNS responses being tampered with, maybe something like a corporate firewall?
I use unbound in recursive mode behind blocky. When an address gets blocked its supposed to return A 0.0.0.0. I don't know what happens on not found. Usually the 2s timeout occurs before unbound can return a not-found result.