One DNS Change Let Urban One Retire Four FTP Servers Without Reconfiguring 60+ Affiliates

Urban One is the largest African-American-owned broadcasting company in the United States. It owns and operates radio stations across more than a dozen major markets, syndicates programming nationally through its Reach Media subsidiary, and runs cable television and digital brands that together reach roughly 80 million consumers a month.

Syndication makes radio a file distribution business. A show, a traffic update, or a sports segment gets produced in one market and has to be at every station that carries it before it airs, including more than 60 affiliate stations that Urban One does not own and whose systems it does not control. For years, that distribution ran on four on-premises FTP servers Urban One hosted itself.

Four Hand-Managed FTP Servers Carried the Affiliate Network

The servers at four Urban One locations were the distribution layer for the radio network. Affiliate stations connected over FTP and SFTP to pull down syndicated programming, traffic updates, and sports content, and internal teams used the same servers to move media between markets. Every part of it was built by hand: the folder structure, the permissions deciding which affiliate saw which programming, and the workflows on top, all maintained one account at a time.

That arrangement put the company's broadcast engineers in the hosting business. Four sets of server infrastructure had to be patched and kept available around the clock for an external audience of more than 60 stations whose broadcasts depended on the files showing up. Every affiliate that joined the network meant another hand-built account and another set of hand-set permissions on aging machines. Urban One's national distribution layer was, in practice, self-hosted infrastructure its radio engineers ran on the side.

A Migration 60 Stations Could Not Be Asked to Join

The servers survived as long as they did because everything pointed at them. Each affiliate station had its own FTP client or automation configured against Urban One's hostname, credentials, and folder paths, and Urban One controlled none of those endpoints. Replacing the servers with anything that changed the address, the protocol, or the folder layout meant coordinating a reconfiguration across more than 60 independent stations, each with its own staff and its own schedule. That is the kind of project that keeps a legacy server alive for years.

The estate also had more asked of it over time. It circulated programming to a large affiliate base while carrying file exchange between Urban One's own markets, and four separately maintained servers were the wrong foundation for both. Urban One decided to move the whole layer to the cloud.

The replacement had a short, strict specification. It had to speak FTP and SFTP, because that is what the affiliates' tools already spoke. It had to reproduce the folder and permission structure the affiliates already navigated. It had to answer at Urban One's own domain, so no station would ever be asked to change a hostname. And it had to leave nothing behind for the engineers to host or patch. Urban One selected Files.com to be that endpoint.

Rebuild in Parallel, Mirror the Permissions, Repoint the Domain

Martin ran the cutover himself, with the legacy servers live the entire time. He rebuilt the affiliate folder structure on Files.com and synchronized the data in parallel while the legacy servers remained live. Two full passes completed before cutover, so Files.com held current data at the moment of the switch.

The accounts came next. Using bulk user import, Urban One created the affiliate users in one batch, with credentials and group-based folder permissions mirroring the original FTP structure. Each affiliate group sees exactly the folders that carry its programming and nothing else. Internal staff went a different way: they sign in through Okta single sign-on, so internal access follows the company directory instead of another set of standalone passwords.

The cutover itself was a DNS change. Urban One pointed its own FTP domain at Files.com with a CNAME record, and the address the affiliates had connected to for years started answering from Files.com. Because Files.com natively speaks FTP and SFTP and presented the same folders under the same credentials, no station installed anything, reconfigured anything, or noticed anything.

The Servers Came Out of Service and No Affiliate Noticed

With affiliate traffic answering at Files.com, Urban One retired the on-premises estate. An exchange layer the engineers had to run themselves became a platform they only have to use.

• More than 60 affiliate stations kept pulling programming at the same address, over the same protocols, through the same folders, with nothing changed on their side.
• Self-hosted FTP servers at four locations are gone, and with them the patching, the hosting, and the hand-maintenance of affiliate accounts on aging hardware.
• Affiliate access is governed by groups rather than per-server account work, so adding a station to the network is a user record and a group membership, not administration across four sites.
• Every upload and download now carries full attribution: who moved which file, when, and from which machine. The old servers never produced a record like that.

Martin calls it “full user history on everything.”

The File Layer Urban One's Markets Now Build On

The cutover also changed what the next workload costs. The Files.com site that took over affiliate distribution is now the file layer Urban One's market engineers extend on their own: studio signage assets are served straight from Files.com Public Hosting, and station audio archives sync into the same site through the Files.com Agent. None of that required standing up another server.

The lesson of the cutover is that the affiliates were never the obstacle. What the stations depended on was an address, a protocol, and a folder structure, not the servers behind them. By seeding Files.com in parallel, mirroring the permissions, and repointing one DNS record, Urban One replaced its entire FTP estate underneath a 60-station network that never had to lift a finger.