Custom nameservers on Route53 complain about nameserver settings

[bmann]

I'm now setting up some company stuff. We use Route53 with custom nameservers.

Trying to use Route53 for a domain complains "Domain nameservers are not set to Route53" ... they are, we just have our own ns1.ourcompanyname.com set for them.

For now, we're just going to set back to default AWS nameservers, but we'd appreciate a way to get past this in the future.

[robi]

Is there sense in using the R53 connector (which expects it's own NS) when you're doing custom NS?

[bmann]

It's "just" a named NS that points to the R53 default ones. Just like you map a domain to a bucket.

[girish]

I think this request is similar to https://forum.cloudron.io/topic/6926/using-cloudron-to-setup-dns-records-in-new-dns-provider-before-switching-nameservers-on-domain-vanity-nameservers-could-also-be-supported-if-changes-made (support for vanity nameservers).

[robi]

@girish so it's more about validating the IPs of the NSs rather than the names.

[girish]

@robi yes, pretty much. However, AFAIK, most DNS providers don't publish their IPs. So, it's not clear how we can protect users from basic errors (which is the common case). Basic mistakes is what we are trying to solve with domain validation. Maybe for the power users (who want vanity domains), we have to put a checkbox for "Skip nameserver validation" .

[robi]

@girish how about simply resolve expected DNS IP and resolve vanity DNS IP and if they match, continue?

[girish]

@robi that would work but it doesn't verify that the domain is hosted on the DNS provider, no?

[robi]

@girish it doesn't need to.

[bmann]

Yeah, the access key is what is going to check if the domain is there. I think "Skip nameserver validation for custom Route53 NS names" would get me there

And all of the DNS and Email stuff...I totally understand how difficult it is to give less technical users the ability to even USE this stuff, as well as support slightly more advanced users. You're doing a great job!