0

I have a domain that is something like mydomain.com and I want to manage the DNS for it myself using my own DNS servers (on a completely different domain - EDIT): ns1.myowndns.com, ns2.myowndns.com, etc... When I try to update the nameserver records with my registrar it rejects these domains. It seems that the .com TLD registrar (and possibly all TLDs?) only accept "well known" DNS servers, possibly from an IP address whitelist.

I happen to be trying to do this in AWS Route53, but it seems like the root problem is more fundamental than the limits of a particular registrar. The actual error reports are obtuse, but this support article seems to be suggest the reason why it might be failing.

I am not trying to implement a "vanity" DNS name using the same domain I want to resolve, so I don't think glue records are relevant. In any case, they only allow you to point at the IP address of an existing DNS server using a different domain name.

I need a custom DNS server because it will be translating domain names into IP addresses dynamically rather than from a static list.

Am I missing something obvious? I feel like this is pretty basic Internet plumbing albeit uncommon in today's service-rich environment.

Improve this question
16
  • Do you want Route 53 name servers to be primary or secondary? GoDaddy for example, allows you to do either/both. godaddy.com/help/what-is-secondary-dns-797
    – Greg Askew
    Aug 30 at 10:47
  • @GregAskew neither - I want to run my own name servers (using bind9)
    – Rupert Rawnsley
    Aug 30 at 10:58
  • 1
    Fair enough. I would presume most Route 53 probably fall into the other categories (all, primary, or secondary).
    – Greg Askew
    Aug 30 at 11:16
  • Ignore my previous comment (if you saw it), I made a mistake. You could try using your IP addresses instead of DNS names of the name servers? I've never seen that limitation before what you describe, so I am wondering if it is some kind of security feature for unknown name servers. Using the IP addresses might bypass that. Worth a shot anyway
    – Mucker
    Aug 30 at 12:16
  • 1
    Ah ok - so it works fine on other tld domains but not .com domains. I didn't spot that initially in the question. My bad
    – Drifter104
    Aug 30 at 13:26

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .