dyn_record creation returns "404 Not Found"

[anero]

When attempting to create a DNS A record on a non-root zone we get a dyn_record.sentry: Failed to create Dyn record: Bad response, got "404 Not Found"

Our template file looks like this:

provider "dyn" {
    customer_name = "${var.dyn_customer_name}"
    username = "${var.dyn_username}"
    password = "${var.dyn_password}"
}

...

resource "dyn_record" "sentry" {
    zone = "whatever.example.com"
    name = "server"
    value = "${aws_instance.server.public_ip}"
    type = "A"
    ttl = 600
}

We've verified using Dynect's ruby SDK that the credentials set on the provider work on the REST API.

[kevinlondon]

@anero: I hit the same thing just now but there's a workaround. I think Dyn wants to use the TLDs as the primary Zones, so you have to arrange it like this:

resource "dyn_record" "sentry" {
    zone = "example.com"
    name = "server.whatever"
    value = "${aws_instance.server.public_ip}"
    type = "A"
    ttl = 600
}

[anero]

@kevinlondon That did the trick, thanks for the workaround!

[kevinlondon]

One unfortunate side-effect of this is that you can't limit a user to a certain zone. E.g. if you create a user that can only modify whatever.example.com and subnodes, they'll get a 400 if they try to use the workaround I suggested. Instead, you have to give them permissions to modify the example.com zone and subnodes.

[stack72]

Hi @anero / @kevinlondon

I am going to close this. It seems to be an error with Dyn rather than terraform. Please comment if you feel otherwise

Thanks

Paul

[ghost]

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.