Open maxkokocom opened 1 year ago
Update, it seems StatusCode: 404 ; Err: 404: The resource could not be found.
Is a result of trying to apply initially. After removing NS records changes it still is raising this error even in the plan stage.
Okey, so I think this is actually some sort of a bug and ticket name should be different, I needed to manually remove this resource:
terraform state rm gandi_nameservers.ns_dns_record
which on the previous run provider failed to create, but it still added it to the state file so the following plans were complaining that a resource could not be found.
I would still appreciate an example how to do nameservers, but this may be something else entriely.
We had the issue which caused us an outage. You should not use the resource gandi_livedns_record
for NS records to point to another DNS provider, but use the gandi_nameservers
resource. Remove the NS entries from the state file under the gandi_livedns_record
.
But be aware of #149 that I just opened as their API / provider does not work well.
Hi, I tried adding NS subdomain record, documentation has two ways of doing so, but both did not worked for me, maybe I am missing obv syntax?
Version I am using is: "2.1.0"
1 way I tried adding subdomain NS:
2nd way I tried was:
the
gandi_livedns_record
typeNS
failed at plan stage with:StatusCode: 404 ; Err: 404: The resource could not be found.
the
gandi_nameservers
failed at apply stage with:I would appreciate anwser which resource type should I use and maybe a basic example to know why it's failing.