Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for PowerDNS set-ptr flag on A/AAAA records #18396

Closed
jgeorgeson opened this issue Jul 5, 2018 · 3 comments
Closed

Support for PowerDNS set-ptr flag on A/AAAA records #18396

jgeorgeson opened this issue Jul 5, 2018 · 3 comments

Comments

@jgeorgeson
Copy link

Terraform Version

Terraform v0.11.7

Terraform Configuration Files

resource "powerdns_record" "foobar" {
  zone    = "example.com"
  name    = "www.example.com"
  type    = "A"
  ttl     = 300
  records = ["192.168.0.11"]
}

Additional Context

The PowerDNS REST API includes a boolean to automatically create PTR records when adding an A or AAAA record with an IP that is within an already configured reverse lookup zone. It'd be nice to make use of that in Terraform, so we can define a single resource.

References

https://doc.powerdns.com/authoritative/http-api/zone.html#record

@ghost
Copy link

ghost commented Jul 5, 2018

This issue has been automatically migrated to terraform-providers/terraform-provider-powerdns#13 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to terraform-providers/terraform-provider-powerdns#13.

@ghost ghost closed this as completed Jul 5, 2018
@bcorner13
Copy link

this provider seems to have been merged in with the base code as terraform-providers/terraform-provider-powerdns has been archived

@ghost
Copy link

ghost commented Aug 13, 2019

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Aug 13, 2019
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants