benburkert / dns

DNS client & server package for Go

dns

DNS client and server package. See godoc for details & examples.

dns's Issues

NS records failing and producing incorrect values

The text records seems to be failing and not produce correct values.

I am trying to use TXT record to automate with letsencrypt and it says TXT records doesn't gets resolved.

How are timeouts handled?

I would like to use this library for a local DNS client cache, but I don't see anything for setting timeouts for the handler. It's possible to use context.Context to define a timeout with a custom net.Resolver.

    const timeout = 10 * time.Millisecond
    ctx, cancel := context.WithTimeout(context.TODO(), timeout)
    defer cancel() // important to avoid a resource leak
    var r net.Resolver
    names, err := r.LookupMX(ctx, "127.0.0.1")

https://play.golang.org/p/HTW6-2o0qeT

Any way to cascade dns.Cache with dns.ResolveMux

I like to use dns.ResolveMux to route different domain to different nameserver and with dns.Cache enabled, but i can not find an ideal way to integrate both of them. Any idea to help? Thanks for wonderful library!

Panic in compression when a name lacks a trailing dot

If the fqdn passed to MessageWriter.Reply lacks a trailing dot then compressor.Pack will panic at line 79 due to slice bound being out of range.

A simple way to replicate it is to change TestQuestionPackUnpack to include a question like this:

			question: Question{
				Name:  "google.com",
				Type:  TypeAAAA,
				Class: ClassIN,
			},

I'm not sure whether the right fix is to return an error due to the malformed name, or to silently append a dot, but it seems like something a typical user is going to run across a lot.