Actions
Feature #4025
closed
PTR support in dnscmd provider
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
DNS
Target version:
-
Description
The dnscmd DNS provider for Windows doesn't support PTR records as it's hard to determine the appropriate zone. See https://github.com/theforeman/smart-proxy/pull/127/files#r8814653 for a bit more info.
Here's some code I didn't include in the merge as it was commented out:
+ # zone = nil
+ # msg = "Added reverse DNS entry #{@value} => #{@fqdn}"
+ # data = @value.split(".")
+ # if data[3].eql?("10")
+ # zone = "10.in-addr.arpa"
+ # end
+ # return nil if zone.nil?
+ # cmd = "/RecordAdd #{zone} #{@value}. PTR #{@fqdn}."
+ # execute(cmd, msg)
+ return true
Updated by Dominic Cleal almost 12 years ago
- Related to Feature #3991: dnscmd provider for smart-proxy (Windows) added
Updated by Oliver Weinmann almost 11 years ago
Hi,
it seems that this is also a problem when provisioning SLES hosts. We switched from nsupdate to dnscmd since we use scavenging on windows dns server. When deploying a SLES host with dnscmd, the host has no hostname set. Using nsupdate this works fine. I guess it has something to do with the missing PTR record? Deploying CentOS with dnscmd works fine.
Updated by Anonymous almost 10 years ago
- Related to Bug #13536: DNS provider dnscmf: PTR's are currently noop added
Updated by Anonymous almost 10 years ago
- Status changed from New to Resolved
Has been resolved in http://projects.theforeman.org/issues/13536. Closing.
Actions