Open spreegabe opened 6 months ago
cc: @tlimoncelli, the maintainer of the provider MSDNS
☺️
Hey there!
I have good news and bad news. The good news is that I can reproduce the issue and have a work-around. The bad news is that implementing DNAME could be quite difficult.
As a work-around, you can change this error into a no-op:
$ git diff
diff --git a/providers/msdns/convert.go b/providers/msdns/convert.go
index d27372a1..f5219217 100644
--- a/providers/msdns/convert.go
+++ b/providers/msdns/convert.go
@@ -117,9 +117,7 @@ func nativeToRecords(nr nativeRecord, origin string) (*models.RecordConfig, erro
//rc.SetTargetTXTString(sprops["DescriptiveText"])
rc.SetTargetTXT(sprops["DescriptiveText"])
default:
- return nil, fmt.Errorf(
- "msdns/convert.go:nativeToRecord rtype=%q unknown: props=%+v and %+v",
- rtype, sprops, uprops)
+ return nil, nil
}
return rc, nil
Sadly implementing the DNAME record would be difficult since there doesn't seem to be a powershell command that can create those records. (DNSControl generates PowerShell statements to do most of the work in MSDNS).
NOTE: Have a general question? You'll get a better response on the dnscontrol-discuss email list!
Describe the bug When exporting a zone from active directory dns with DNAME records, dnscontrol crashes.
To Reproduce
DNS Provider
Additional context This works* in v3 with the activedirectory provider. The DNAME records aren't in the pretty dnscontrol output, but are in the dump from the underlying powershell command and marked as unsupported, snippets below.
the following is output from dnscontrol v3 with the
activedir
provider. -- adzonedump.contoso.ai.json-- powershell.log