Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Seeder does not return any NS records #18

Open
JeremyRand opened this issue Apr 24, 2022 · 2 comments
Open

Seeder does not return any NS records #18

JeremyRand opened this issue Apr 24, 2022 · 2 comments

Comments

@JeremyRand
Copy link
Contributor

It would be helpful if the seeder returned an NS record, corresponding to the domain name where the seeder is running. This would enable stuff like dig NS seed.namecoin.libreisp.se to work correctly.

@gits7r
Copy link

gits7r commented May 28, 2022

I think this issue is very relevant at present moment as it causes problems with some resolve queries via SOCKS5.
While we are at it, we might also fix a secondary (but not so crucial) problem, that we also don't return any valid SOA with the query: No valid SOA record came back! -- having these two fixed should help our dnsseeds be resolve-able via Tor.

@ss11s
Copy link

ss11s commented Dec 29, 2022

This fix is important for onion network only new starting nodes, otherwise you must use addnode with a running node in order to be able to join / bootstrap to the namecoin network. Without the NS and SOA return, when the seeders are queried via Tor/Socks5 it does not return any single address of currently running node. Given all NMC dnsseeds use this implementation particularly, it's not possible to get an address, so you must have a running address (pref onion) and use addnode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants