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

google_dns_record_set NS create fails on apex #836

Closed
matti opened this issue Dec 9, 2017 · 3 comments
Closed

google_dns_record_set NS create fails on apex #836

matti opened this issue Dec 9, 2017 · 3 comments
Assignees

Comments

@matti
Copy link

matti commented Dec 9, 2017

with

resource "google_dns_managed_zone" "apex" {
  name     = "mydomain-com"
  dns_name = "mydomain.com."
}

resource "google_dns_managed_zone" "sub" {
  name     = "sub-mydomain-com"
  dns_name = "sub.mydomain.com."
}

resource "google_dns_record_set" "apex_sub_ns" {
  name = "sub.mydomain.com."
  type = "NS"
  ttl  = 300

  managed_zone = "${google_dns_managed_zone.apex.name}"

  rrdatas = ["${google_dns_managed_zone.sub.name_servers}"]
}

I get

* google_dns_record_set.apex_sub_ns: Error creating DNS RecordSet: googleapi: Error 400: The resource record set 'entity.change.deletions[0]' is invalid because a zone must contain exactly one resource record set of type 'NS' at the apex., invalidZoneApex

but if I change the "NS" type to "TXT", apply and then change it back to "NS" it works.

@rosbo rosbo assigned paddycarver and rosbo and unassigned paddycarver Dec 11, 2017
@rosbo
Copy link
Contributor

rosbo commented Dec 11, 2017

Hi Matti,

@paddycarver fixed this bug in #807.

The next release will include a fix for this bug.

Thanks.

@paddycarver
Copy link
Contributor

That release just went out! terraform init -upgrade should fix this. If it doesn't, feel free to reply to this issue and we can take a look.

modular-magician added a commit to modular-magician/terraform-provider-google that referenced this issue Sep 27, 2019
Signed-off-by: Modular Magician <magic-modules@google.com>
@ghost
Copy link

ghost commented Mar 30, 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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 30, 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

3 participants