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

DDNS Resolver for Initialise Client #56

Merged
merged 1 commit into from
Jun 17, 2019
Merged

DDNS Resolver for Initialise Client #56

merged 1 commit into from
Jun 17, 2019

Conversation

MrDevBot
Copy link
Contributor

Client now checks for Alphanumeric strings in connection settings using Regex and treats them as a DNS and attempts to connect to every IP attached to that DNS (Makes DDNS such as NoIP compatible with the Client)

Client now checks for Alphanumeric strings in connection settings using Regex and treats them as a DNS and attempts to connect to every IP attached to that DNS (Makes DDNS such as NoIP compatible with the Client)
@NYAN-x-CAT
Copy link
Owner

Dynamic DNS will always give you 1 IP, or am I wrong? can you explain in what situation this method will be helpful, please?

@MrDevBot
Copy link
Contributor Author

@NYAN-x-CAT This would be useful for situations where a Domain name leads to multiple Potential hosts in which the client will attempt every one after the host before it has failed

@NYAN-x-CAT NYAN-x-CAT merged commit 7d988be into NYAN-x-CAT:master Jun 17, 2019
@enkianu
Copy link

enkianu commented Jun 17, 2019

Great work guys. Does this make it compatible with {.}bit domains hosted with a dnshost (that supports blockchain domains) like cloudns.net ?

@NYAN-x-CAT
Copy link
Owner

@enkianu Yes, it should be compatible. Feel free to post your feedback.

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

Successfully merging this pull request may close these issues.

3 participants