• v0.2.0 744a75b25d

    checker: resolve relative NS labels using the zone origin
    Some checks failed
    continuous-integration/drone/push Build is failing
    continuous-integration/drone/tag Build is failing

    nemunaire released this 2026-05-16 13:37:05 +00:00 | 0 commits to master since this release

    NS hostnames stored in happyDomain's abstract.Origin service are encoded
    relative to the zone apex (e.g. "ns0" instead of "ns0.example.com.").
    normalizeNSList was calling dns.Fqdn() directly, turning "ns0" into the
    useless single-label "ns0." rather than the correct FQDN.

    Expose domain_name in ServiceOpts so happyDomain auto-fills the zone
    apex at service scope, then use sdk.JoinRelative in normalizeNSList to
    absolutize relative labels. Absolute FQDNs (trailing dot) are kept
    as-is so external nameservers round-trip safely.

    Downloads