Closed Kneelawk closed 1 year ago
I have to think a bit more about adding DNS resolution inside quinnet.
I am not sure that I understand the alternative you mention. Do you mean: the user resolves DNS on its own, but still provides the library with IP and Domain name (if any) ? (this is what might come out of #9)
Do you mean: the user resolves DNS on its own, but still provides the library with IP and Domain name (if any) ?
Yes, this is what I meant.
I will leave DNS resolution out of Quinnet scope for now. Since #14 was implemented, I will close this.
The Issue
Currently, client connections can only be specified as IP address strings. It would be handy if applications could also specify a domain name to connect to.
As an alternative, this library could let applications specify separate connection IP addresses and certificate domains, allowing them to do their own DNS resolution.