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

IPv6-only support #88

Closed
ghost opened this issue Jan 30, 2016 · 4 comments · Fixed by #89
Closed

IPv6-only support #88

ghost opened this issue Jan 30, 2016 · 4 comments · Fixed by #89

Comments

@ghost
Copy link

ghost commented Jan 30, 2016

Pending Let's Encrypts's IPv6 support (IPv6-only hosts), I guess bootstrapping off a magic IPv4 DNS forwarder is going to be a problem...

/*  .../lego/acme/dns_challenge.go */
func checkDNS(domain, fqdn string) bool {
    // check if the expected DNS entry was created. If not wait for some time and try again.
    m := new(dns.Msg)
    m.SetQuestion(domain+".", dns.TypeSOA)
    c := new(dns.Client)
    in, _, err := c.Exchange(m, "8.8.8.8:53")  // <= ouch
    if err != nil {
        return false
    }
    // ...

There are systems out there that let only certain DNS forwarders through their firewalls (to mitigate cache poison attacks etc), so maybe it would be an idea to provide a configurable forwarder?

@xenolf
Copy link
Member

xenolf commented Jan 30, 2016

Yes, I agree that this may be a problem. My initial thought was to get the standard DNS resolver for the system and use that, but it didn't work out.

Making it configurable may be the best option.

@ghost
Copy link
Author

ghost commented Jan 30, 2016

Well, it can be that easy! I did not test it with an actual staging / live challenge, though. (It does not fix the fascist firewall problem, but that is an edge case.)

@xenolf xenolf reopened this Jan 30, 2016
@xenolf
Copy link
Member

xenolf commented Jan 30, 2016

I will leave this open to track the "fascist firewall" issue :P

@xenolf
Copy link
Member

xenolf commented May 12, 2016

There is not really something we can do in a broad sense. We will handle the issues if any in relation to this on a case-by-case basis.

@xenolf xenolf closed this as completed May 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

1 participant