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, [email protected] 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. > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
