GoDaddy Registry Replaces Its Amazon EC2 SFTP Server With Self-Service Zone File Distribution on Files.com

GoDaddy Registry is the domain-registry division of GoDaddy Inc. and one of the largest registry operators in the world. It is the Registry Operator behind .co, .us, .biz, and .nyc, and it runs backend registry services for hundreds more top-level domains on behalf of sovereign nations, city governments, and global brands.

Operating a TLD carries an obligation that has nothing to do with selling domains. The registry must make its zone files, the daily data files describing each TLD's DNS, available to vetted outside parties: researchers, university teams, security vendors, registrars, and companies investigating spam and domain abuse. Those parties are not GoDaddy customers and not GoDaddy employees. They are vetted members of the general public, and hundreds of them are entitled to pull the data every day.

Serving that audience meant solving an identity and entitlement problem, not simply hosting two files. GoDaddy Registry replaced its failed Amazon EC2 SFTP service with a branded Files.com portal that lets vetted outsiders create their own accounts and retrieve the right zone files without helpdesk provisioning.

Two Zip Files a Day, and a Server That Stayed Down

The distribution ran on a self-hosted SFTP service on a small Linux instance in EC2, with an Apache web server alongside it publishing the files. By the time the registry went looking for a replacement, that service had been offline for roughly three months. A daily publication obligation sat unserved while a box waited for someone to bring it back.

Even when the server ran, it made work. It had no self-service path, so every new user landed on the customer service team: someone connected to the Linux box over SSH and added the account by hand.

An Audience That Could Never Live in GoDaddy's Identity Systems

The arrangement had survived because the problem is structurally awkward. The entitled users are outsiders, so none of them can be provisioned through GoDaddy's internal identity systems. Roughly 300 are entitled to one TLD's zone file and roughly 100 to the other.

Meanwhile the workload itself looks tiny on paper. Two zip files, tens of megabytes each, updated daily. Building self-service signup, an entitlement model, and resilient hosting in-house is a real engineering project, and it was never going to be justified for two zip files a day. So the small box and the manual routine persisted until the box died.

The replacement had to let vetted outsiders create their own accounts, gate each of the two files by entitlement, serve automated daily pulls over the protocols those users' scripts already spoke, carry GoDaddy Registry's own branding, and run with no server for anyone to keep alive. GoDaddy Registry selected Files.com to be that distribution portal.

“The management interface and self-sign-up all look good, and will make our customer service's team happy, as an alternative to making them SSH into a linux box and manually add accounts.”

A Portal Whose Users Provision Themselves

Durrant built the site himself, and what he built is a standing public endpoint whose user lifecycle is part of the design.

The front door carries the registry's identity. The site runs under a custom domain with GoDaddy Registry's own branding.

Entitlement is two Files.com groups, one per zone file. Vetting stays with GoDaddy Registry; once a requester is approved, placing them in the right group is the entire setup. The group grants exactly the file they are entitled to and nothing else.

Existing users were invited in bulk to sign up through an email link. New requesters onboard the same way after approval, with no account created by hand.

Downloads run over whatever client the user already has. Most script a daily SFTP pull, while some call the REST API. Once the portal was live, Durrant handed day-to-day ownership to the registry operations team. Running it stopped being a systems engineering job.

Hundreds of External Users, Without SSH Provisioning

With the portal in production, GoDaddy Registry replaced a server-and-helpdesk routine with a managed distribution channel.

• Hundreds of external users have been invited onto the platform, and most active users pull the updated zone file every day over SFTP or the API, with almost no human interaction on either side.
• Approval and entitlement remain with registry operations: staff vet each requester and assign the right group. Account creation then happens through a signup link; nobody SSHes into anything.
• The publication obligation sits on a managed platform instead of a single EC2 instance, so there is no server to patch, size, or bring back from the dead.

The Obligation Runs Whether Anyone Touches It or Not

Today, serving zone data to the outside world is not a system GoDaddy Registry operates. It is a standing Files.com portal under the registry's own domain. Registry operations still vets requesters and assigns entitlements, while approved outsiders create their own accounts and retrieve the files without helpdesk or systems engineering work.

It used to be that every new researcher ended in an SSH session, and the whole channel depended on one small server staying up. The lesson travels: a user base that can never live in your internal identity systems does not have to route through IT. Self-signup and group-based entitlement turned a daily publication duty into a managed distribution channel, and Files.com is what it runs on.