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

Azure provider: Resource to manage DNS #3147

Closed
mtekel opened this issue Sep 2, 2015 · 6 comments
Closed

Azure provider: Resource to manage DNS #3147

mtekel opened this issue Sep 2, 2015 · 6 comments

Comments

@mtekel
Copy link

mtekel commented Sep 2, 2015

Azure APIs support creation, deletion and general manipulation of DNS records and zones. We would like to do this using terraform. Azure SDK should support DNS operations soon: Azure/azure-sdk-for-go#184

@thecodeassassin
Copy link

+1

@aznashwan
Copy link
Contributor

@mtekel: with the release of the new ARM API bindings in the go sdk; DNS records and zones (which are only definable using ARM) are on their way.

For the status of ARM support, please refer here: #3212

@mtekel
Copy link
Author

mtekel commented Nov 2, 2015

great, looking forward to it

@mtekel
Copy link
Author

mtekel commented Mar 2, 2016

I see TF 0.6.12 adds a lot of Azure resources for DNS:

New resource: azurerm_dns_a_record (#5013)
New resource: azurerm_dns_aaaa_record (#5013)
New resource: azurerm_dns_cname_record (#5013)
New resource: azurerm_dns_mx_record (#5041)
New resource: azurerm_dns_ns_record (#5041)
New resource: azurerm_dns_srv_record (#5041)
New resource: azurerm_dns_txt_record (#5041)
New resource: azurerm_dns_zone (#4979)

I am not sure if that might cover this feature request, as I'm hands-off Azure now and have no way to test...

@stack72
Copy link
Contributor

stack72 commented Jul 27, 2016

Hi @mtekel

The azurerm resources you mentioned do indeed cover the DNS functionality you asked for :)

closing this PR

Paul

@stack72 stack72 closed this as completed Jul 27, 2016
@ghost
Copy link

ghost commented Apr 24, 2020

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 Apr 24, 2020
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

6 participants