Appears the issue is not related to Nostr.land

Are you using a NIP-05?

Reply to this note

Please Login to reply.

Discussion

I am. I have a very strict browser setup (Firefox)

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.nostr.land/user/036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58.

Please give me the request logs from the requests tab. It works in my browser (Firefox) and returns the correct CORS headers

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?

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.

*in front of blocky*

Try resolving with dig and send me the output. Usually some things like errors are listed in EDNS.