You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: