Unable to create PTR Record for MS DNS (dnscmd) foreman proxy

Support
1

I am trying to call the foreman smartproxy api to add an A record and ptr
record.

I am able to add an A record with the following API POST call:
http://server.example.com:8000/dns/?fqdn=miq-ss71.example.com&value=10.1.1.114&type=A

But I get two different outputs when trying to add a PTR record:
http://server.example.com:8000/dns/?fqdn=miq-ss71.example.com&value=10.1.1.114&type=PTR

On SmartProxy 1.9 I get a 200 OK return code, but no entry is created.

On 1.12 or 1.13 I get a 400 Bad Request and in the Debug logs I get:
Invalid reverse DNS 10.1.1.114

The smartproxy is installed on a 2008r2 domain server and I've tried
running the smart proxy manually as my account which is a domain admin.

2

I should add that yes the reverse zone exists 1.1.10.in-addr.arpa
I can add an entry manually, etc.

··· On Friday, October 28, 2016 at 9:46:59 AM UTC-4, jonath...@bluemedora.com wrote: > > I am trying to call the foreman smartproxy api to add an A record and ptr > record. > > I am able to add an A record with the following API POST call: > > http://server.example.com:8000/dns/?fqdn=miq-ss71.example.com&value=10.1.1.114&type=A > > > But I get two different outputs when trying to add a PTR record: > > http://server.example.com:8000/dns/?fqdn=miq-ss71.example.com&value=10.1.1.114&type=PTR > > On SmartProxy 1.9 I get a 200 OK return code, but no entry is created. > > On 1.12 or 1.13 I get a 400 Bad Request and in the Debug logs I get: > Invalid reverse DNS 10.1.1.114 > > The smartproxy is installed on a 2008r2 domain server and I've tried > running the smart proxy manually as my account which is a domain admin. >
3

I switched to attempting GSS-TSIG on a linux smart proxy wondering if it
was an issue with the dnscmd method. I am still able to create an A record,
but not a PTR record using a smart proxy. I continue to get a 400 return
code.

I am able to add a PTR manually with nsupdate on the linux host.

··· On Friday, October 28, 2016 at 9:46:59 AM UTC-4, jonath...@bluemedora.com wrote: > > I am trying to call the foreman smartproxy api to add an A record and ptr > record. > > I am able to add an A record with the following API POST call: > > http://server.example.com:8000/dns/?fqdn=miq-ss71.example.com&value=10.1.1.114&type=A > > > But I get two different outputs when trying to add a PTR record: > > http://server.example.com:8000/dns/?fqdn=miq-ss71.example.com&value=10.1.1.114&type=PTR > > On SmartProxy 1.9 I get a 200 OK return code, but no entry is created. > > On 1.12 or 1.13 I get a 400 Bad Request and in the Debug logs I get: > Invalid reverse DNS 10.1.1.114 > > The smartproxy is installed on a 2008r2 domain server and I've tried > running the smart proxy manually as my account which is a domain admin. >
4

not sure if this is still relevant for you. but i just stumbled across the same issue.

the issue is that you have to provide the .in-addr.arpa as a value, not the ip.

so this will work:

http://server.example.com:8000/dns/?fqdn=miq-ss71.example.com&value=114.1.1.10in-addr.arpa&type=PTR