Slashdot Mirror

← Back to Stories (view on slashdot.org)

GoDaddy Proposes New DNS Configuration Standard (programmableweb.com)

Posted by EditorDavid on from the defining-the-domain dept.

GoDaddy has announced "an open set of APIs for DNS providers and web service providers," called Domain Connect. An anonymous Slashdot reader writes: "Once enabled, customers can quickly configure their domain to point to the web service of their choice with push button simplicity," according to the announcement, "streamlining and simplifying the process of connecting websites and domain names registered on different platforms." GoDaddy's submitted it for consideration as an IETF standard, where they have the support of Microsoft and Squarespace, as well as the other two largest registries, eNome and Name.com. But in the meantime, they told ProgrammableWeb, the specificaion is "out there in the public, open for feedback and adjustment."

"GoDaddy is seeking to take all the friction out of the process," the site reports, "by offering service providers like Squarepace, Wix, Google, Microsoft, Wordpress and others a registrar-agnostic API that they can use to programmatically configure all the necessary DNS entries... in lieu of making end users laboriously crawl through a bunch of forms and then praying that they've done it all correctly." Different access levels will be available based on the service being provided, and for GoDaddy's implementation of the API their senior VP of Domains Engineering "said that the program will not be open to public developers and that any service providers wanting access will have to be approved by his team at GoDaddy."

5 of 81 comments (clear)

  1. Re:This is great for devops, automated deployments by Anonymous Coward · · Score: 3, Insightful

    Automated deployments existed before Docker became a fad. I've been able to programmatically configure DNS for years now at AWS Route53 and DNSimple. I'm sure there are others that offer some form of API.

  2. TXT record?? by BringsApples · · Score: 5, Insightful

    "When a customer wishes to connect a domain, the service provider needs to know who the DNS provider is. To do this, Domain Connect specifies a TXT record be added to the DNS for a domain that specifies a URL that can be called for discovery. The service provider queries the domain for this TXT record (called “DOMAIN_CONNECT”) which, if present, indicates that the domain is served by a DNS provider that supports the Domain Connect protocol. Given the URL, a service provider can call a API endpoint for protocol discovery:

    GET v2/{domain}/settings"

    I don't like the idea of a TXT record letting everyone know that my domain allows an API to edit it's configuration.

    --
    Politics; n. : A religion whereby man is god.
  3. clearly they havent heard by nimbius · · Score: 5, Insightful

    customers can quickly configure their domain to point to the web service of their choice with push button simplicity

    which is already available in plesk, openstack, and godaddys own panel. why do we need to reinvent this shit every year?

    "GoDaddy is seeking to take all the friction out of the process,"

    what friction? the DNS RFC has been around since 1987, its not some arcane rune stone of indecipherable glyphs. hell, you managed to get it to work in your panel.

    GoDaddy's implementation of the API their senior VP of Domains Engineering "said that the program will not be open to public developers and that any service providers wanting access will have to be approved by his team at GoDaddy."

    aaaaaand go fuck yourself for trying to make the internet proprietary. you might have swinging dicks backing this idea, but you can expect a shit-storm of legitimate registrars like Dreamhost and register4less to completely ignore this DNS fever-dream you have. Im sure youll support it for 4 years as an option, then quietly shuffle it under the rug of shit that didnt work out like that cloud storage you based entirely off net-app called Nebula.

    --
    Good people go to bed earlier.
    1. Re:clearly they havent heard by mwvdlee · · Score: 4, Insightful

      GoDaddy's implementation of the API their senior VP of Domains Engineering "said that the program will not be open to public developers and that any service providers wanting access will have to be approved by his team at GoDaddy."

      aaaaaand go fuck yourself for trying to make the internet proprietary. you might have swinging dicks backing this idea, but you can expect a shit-storm of legitimate registrars like Dreamhost and register4less to completely ignore this DNS fever-dream you have. Im sure youll support it for 4 years as an option, then quietly shuffle it under the rug of shit that didnt work out like that cloud storage you based entirely off net-app called Nebula.

      Don't worry. If everybody follows GoDaddy's example, then nobody can interoperate and this protocol is dead in the water. They're basically hoping that competitors will let them take "their" domainnames while paying lipservice to supporting the protocol themselves.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
  4. GoDaddy, if you want to streamline... by Opportunist · · Score: 3, Insightful

    Seriously, if GoDaddy was to streamline and simplify a process, they should start at home. Remove all your upselling attempts and "oh look, this is surely some bling you MUST HAVE, you'll be the coolest dude in your school" crap. And, lo and behold, you will probably find out what everyone else already knew: That configuring DNS is actually trivial... provided you don't get it from GoDaddy.

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.