Need a document about DinoDNS about dinodns HOT 4 OPEN

Interesting case and somewhat of an oversight on my part. Technically you can do what you want if you use your own instance of TurnerSoftware.DinoDNS.Connection.TlsResolver. The constructor of it allows setting a custom SslClientAuthenticationOptions where you can specify SslClientAuthenticationOptions.TargetHost which I believe will fix your problem.

You then just create your own instance of NameServer, passing in your IP address and custom TlsResolver instance.

That would be the fastest way to get the functionality you want right now. In the future, I'll likely change what details are passed into resolvers so domain names can be defined or something.

from dinodns.

Hey @SpaceTimee - thanks for raising the issue! Currently the only documentation is the getting started guide on the readme: https://github.com/TurnerSoftware/DinoDNS#-getting-started

I do have plans to write further documentation though they've been on the back burner while I work on a major rewrite of code for another one of my libraries.

Let me know what you're trying to do (what type of query etc) and I should be able to help you out.

from dinodns.

I meet a special trouble. A DOT server tls://dns.rubyfish.cn:853 is using "certificate" to ban ip requests. It means I can only use "tls://dns.rubyfish.cn:853" to resolve DNS. If I use its ip "tls://175.24.154.66:853" (got from command "ping dns.rubyfish.cn"), It will return an error like "Cannot make the DNS request: getting connection to tls://175.24.154.66:853: connecting to 175.24.154.66: x509: cannot validate certificate for 175.24.154.66 because it doesn't contain any IP SANs".

In the getting started guide, DnsClient in DinoDNS could only receive ips as its NameServer. Is it possible to use DNS domains to resolve domains? XD

from dinodns.

Thanks for ur instruction, I look forward to the exciting improvements

from dinodns.