RadioDNS Phase 1 - FCCdata

REC support of RadioDNS on

FCCdata now supports RadioDNS.  RadioDNS is an open source system that provides metadata and logos for radio stations intended to be used with connected cars and other compatible devices.  For clients using RadioDNS, such as FCCdata, this involves having to make domain name server (DNS) calls to retrieve an XML file which includes the station's basic information as well as links to logo graphics. 

REC will support RadioDNS on our presentations for United States (FCC) FM (analog and HD) stations as well as FM stations in the United Kingdom.

When a station is equipped with RadioDNS, it will show a "RadioDNS" indicator in the header and for US stations, with which audio channels RadioDNS was detected on (analog FM, HD1, HD2, HD3 and/or HD4).  

There will also be a new RadioDNS section that will show for RadioDNS stations.  For the US, this will be located in the right panel right above the coverage map.  In the UK presentation, it will be shown on the left panel above the technical parameters.

Mobile is currently not supported but will be very soon.  

We are also currently not supporting 3-letter call sign FM stations (i.e. KMJ-FM).  We are working on an RDS PI code solution to accommodate three letter FM calls and FM translators carrying HD and AM stations.

In the RadioDNS section, FCCdata will include the basic metadata information from the station's Service Identifier XML file including station name, description, websites and the station's logo.  

There will also be links to audio streams where available.  We will support MP3 and AAC streams.  Upon clicking a stream link, the system will open a pop-up player that includes the station's logo and other metadata.  

For stations that are also delivering Program Information (PI), we will display program schedules.  When bringing up a station in FCCdata, if there is a PI file, we will place a "Schedule" indicator on the RadioDNS station details.  Clicking this link will take the user to a new page that displays the program information as well as the station information.  When a stream is launched from FCCdata, the system will check to determine if there is a PI file. If so, the player window will increase in size and display the program schedule on the right side of the player window. 

REC's implementation of RadioDNS is per the following European Broadcasting Union technical standards, which have been accepted worldwide for the delivery of station and program data:

More information about RadioDNS is available at

We note that while we have developed per the standards, not every participant is following the standards to the letter.  We have attempted to include as many "flavors" of the data (Global, iHeart, EMF, Aiir, etc.) as possible.  At times, you may see warning messages.  If you experience these messages, please send an email to REC with the full URL showing on the address bar and the warning message that is being displayed so we can address it. 

REC implements RadioDNS at J1 HD

In conjunction with our friends at Aiir, REC has also initiated RadioDNS service on our J1 HD program service which airs on KBUU-LP HD3, Malibu, CA. 

RadioDNS development for myLPFM in progress

Our other major development we are working on to support RadioDNS will be enhancements to myLPFM, which will allow any LPFM station to provide basic logo and metadata service and for REC clients with a historical spend of $350 or more, the ability to add streaming URLs to utilize the RadioDNS Service Following feature, which permits a connected car to revert to the station's stream in the event they leave the LPFM service area.  This is planned for myLPFM version 3.2.  We are currently at version 3.0 with the release of version 3.1 on hold awaiting approval of our request to FEMA to obtain access to IPAWS-OPEN production data for the version 3.1 emergency and weather alert support.

Updated Ofcom UK Radio Broadcast Parameters

We have also updated the AM, FM and DAB technical parameter data for the United Kingdom with a modification to our internal parsing program due to a slight change in the Ofcom file format of the parameter files.

Developer Observations

As we have noted above, we have found that some implementations of RadioDNS SI data are inconsistent with how the XML code is formatted.  This has led us to write in several "exceptions" to how our software parses the XML code.  We may eventually develop a test tool that permits evaluation of the SI and PI XML code based on the published ETSI standard.  

The data from the UK stations operated by Global are probably the most robust with SI and PI data.  (Capital Radio London, LBC London, Heart 106.2 London, Radio X Manchester)

UK Bauer Media stations have basic SI data (logos and station names) with no stream links and no PI data for program schedules.  (KISS London, Hits Radio Manchester, Cool FM Belfast)

BBC stations are have SI data with no stream links and no PI data. (BBC Radio 1, BBC Radio 4, BBC Radio London)

Please note that FCCdata URLs to UK stations were valid at the time of this development and are subject to change with the next Ofcom update. 


Many of the iHeart stations are listed with SI data and streams, but no PI data. (Z100 - WHTZ, KIIS-FM Los Angeles, KOST 103.5 Los Angeles)

Urban One stations are reading, but very strangely with the city name instead of the station name in the station name field and no logo. (WKYS, WLNK)

Cumulus stations are showing with full SI with logos, no streams, no PI. (KBBY-FM, KIX96 WJCL-FM)

Educational Media Foundation is showing with full SI plus streams but no PI (EPG is resolving to trigger our Schedule link, but there is no PI data).  (KKLQ K-Love).

Cox Media and Audacy have not yet implemented RadioDNS.

Some NPR stations have implemented RadioDNS through PRSS. (KPCC - includes how HD subchannels will be displayed) 

Stations using Aiir are showing with full SI and PI data as long as it is programmed in by their client.  (KJUG, KCRZ, KBUU-LP HD3-J1HD


Saturday, October 29, 2022
Systems affected:
J1 HD audio streaming
Issue type: