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

chicken and egg Problem for forwardurl resolve while h2dns (forwarder) used As System resolver #27

Closed
Opensourcecommunitydevelopment opened this issue Jun 10, 2017 · 1 comment

Comments

@Opensourcecommunitydevelopment
Copy link
Contributor

it tries to resolve dns.google.com and fails, because it can't itself As it is a forwarder only.

suggested solution step:

  1. Put a hardcoded fallback IP for both ipv6 and Internet Protocol Version 4, bad because it is Not anycasted like 8.8.8.8. should be used for very earliest first Connection Agent only If No other Connection could be made. because you Want the nearset dns.google.com Server near you for latency reasons.
  2. while we ping it already, use the result! Cache at least the Response of dns.google.com between restarts.
  3. use fallback only, if No previous Cached ip is PresenIP

for spdy, comman Name is required for certificate Validation. simply use Ip only As Host Not work here As wanted.

@yyfrankyy
Copy link
Owner

I prefer to do nothing about it, let the parent DNS resolvedns.google.com. anybody using DNS over HTTP should aware of this.

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

2 participants