Actions
Bug #13421
closed[smart-proxy] provider dnscmd: create record in sub domain broken - DNS_ERROR_ZONE_DOES_NOT_EXIST
Difficulty:
Triaged:
Description
The usage of dnscmd is in the provider, it fails when adding a record to a sub domain. Here, always the top domain has to be used.
D, [2016-01-27T22:24:01.492667 #1508] DEBUG -- : executing: c:\windows\system32\cmd.exe /c c:\Windows\System32\dnscmd.exe localhost /RecordAdd sec.domain.com testdns2.domain.com. A 192.168.0.11 E, [2016-01-27T22:24:01.523888 #1508] ERROR -- : Dnscmd failed: Command failed: DNS_ERROR_ZONE_DOES_NOT_EXIST 9601 0x2581 E, [2016-01-27T22:24:01.523888 #1508] ERROR -- : Failed to add DNS entry testdns2.sec.domain.com => 192.168.0.11 D, [2016-01-27T22:24:01.523888 #1508] DEBUG -- : C:/TheForeman/smart-proxy/modules/dns_dnscmd/dns_dnscmd_main.rb:94:in `report' C:/TheForeman/smart-proxy/modules/dns_dnscmd/dns_dnscmd_main.rb:85:in `execute'
while the correct command should be:
c:\windows\system32\cmd.exe /c c:\Windows\System32\dnscmd.exe localhost /RecordAdd doimain.com testdns2.sec.domain.com. A 192.168.0.10
Since we can never determine the top scope domain correctly, I can only think of this as a setting in dns.yaml
Updated by The Foreman Bot over 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/smart-proxy/pull/369 added
Updated by Anonymous over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 310433f729c5743b0c9f489e664470c0959857b8.
Updated by Dominic Cleal over 8 years ago
- Translation missing: en.field_release set to 71
Updated by The Foreman Bot over 8 years ago
- Assignee set to Dominic Cleal
- Pull request https://github.com/theforeman/smart-proxy/pull/381 added
Updated by Dominic Cleal over 8 years ago
- Assignee changed from Dominic Cleal to Daniel Helgenberger
Actions