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

Currently we are incompatible with major DNS providers (no records returned) #20

Open
gits7r opened this issue May 27, 2023 · 0 comments

Comments

@gits7r
Copy link

gits7r commented May 27, 2023

At least Google's Public DNS servers and tor-resolve (Tor SOCKS5 implementation) is incompatible with servers running this dnsseeder.

Google's Public DNS servers used to work fine, but recently stopped doing so - users get a no records found message, like inexistent name, when in fact a local unbound daemon will get the records just fine.

Maybe blocked by: #18
It must be a particularity of this software, because the dnsseeds that run different software work with Google public DNS just fine, so the length / size of the response (many AAAA and A records) are NOT the issue.

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

1 participant