Name.com now manages NS records by itself. (#92)

This commit is contained in:
Pat Moroney 2017-04-19 15:20:26 -06:00 committed by Craig Peterson
parent 7d8ba06740
commit e9f6749c0f

View file

@ -2,14 +2,12 @@ package namedotcom
import (
"fmt"
"log"
"strings"
"strconv"
"github.com/miekg/dns/dnsutil"
"github.com/StackExchange/dnscontrol/models"
"github.com/StackExchange/dnscontrol/providers/diff"
"strconv"
)
var defaultNameservers = []*models.Nameserver{
@ -83,11 +81,7 @@ func checkNSModifications(dc *models.DomainConfig) {
newList := make([]*models.RecordConfig, 0, len(dc.Records))
for _, rec := range dc.Records {
if rec.Type == "NS" && rec.NameFQDN == dc.Name {
// name.com does change base domain NS records. dnscontrol will print warnings if you try to set them to anything besides the name.com defaults.
if !strings.HasSuffix(rec.Target, ".name.com.") {
log.Printf("Warning: name.com does not allow NS records on base domain to be modified. %s will not be added.", rec.Target)
}
continue
continue // Apex NS records are automatically created for the domain's nameservers and cannot be managed otherwise via the name.com API.
}
newList = append(newList, rec)
}