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

Do not only rely NS Record on parent domain #30

Open
Haraguroicha opened this issue Jan 4, 2019 · 2 comments
Open

Do not only rely NS Record on parent domain #30

Haraguroicha opened this issue Jan 4, 2019 · 2 comments

Comments

@Haraguroicha
Copy link

dnsr/resolver.go

Lines 124 to 127 in 5293a1c

nrrs, err := r.resolve(ctx, pname, "NS", depth)
if err == NXDOMAIN || err == ErrTimeout || err == context.DeadlineExceeded {
return nil, err
}

Such as xxxxx.sn.mynetname.net which is used for RouterBoard DDNS function (xxxxx is a random serial number on RouterBoard), the resolver trying to resolve a NS Record sn.mynetname.net, but the domain was stored on mynetname.net, and it received a NXDOMAIN response then return nil, it should try until the server mynetname.net also response an error

@ydnar
Copy link
Member

ydnar commented Jan 5, 2019

Interesting. We’ll take a look. Thanks for filing the report!

@SkYNewZ
Copy link

SkYNewZ commented Apr 27, 2022

Hello. I have the same problem on my side with domains for which each segment does not necessarily have NS records, which prevents any resolution. Would it be possible to manage this case?

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

3 participants