You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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?
dnsr/resolver.go
Lines 124 to 127 in 5293a1c
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 Recordsn.mynetname.net
, but the domain was stored onmynetname.net
, and it received a NXDOMAIN response then return nil, it should try until the servermynetname.net
also response an errorThe text was updated successfully, but these errors were encountered: