DNS: privacy & security

Why changing this DNS is safe

Isolated change. The DNS setting is applied on your media receiver alone. Every other device at home — computers, phones, TVs, banking apps — keeps using your provider’s or router’s normal automatic DNS and never depends on our server.

No sensitive data. An audio receiver stores no passwords, personal data or card numbers. The most our server ever sees is the receiver’s own network requests looking for radio stations.

Your traffic is untouched. We answer only the old, now-defunct vTuner directory addresses (such as radiodenon.com) from our own working database, and forward everything else unchanged. All your other traffic — including any streaming you start — runs exactly as normal.

Which domains does the DNS actually touch?

Only the legacy internet-radio directory domains: vtuner.com, radiodenon.com, radiomarantz.com, radio-pioneer.com, radiosetup.com, my-noxon.net and noxonserver.eu. Those are the addresses old receivers call to fetch their station list. Nothing else is affected.

Are all my DNS lookups redirected, or only the radio ones?

Only the radio-directory domains above resolve to our server. Every other lookup — your bank, e-mail, websites, apps — is forwarded unchanged to public resolvers (Cloudflare 1.1.1.1 and Google 8.8.8.8) and answered normally. We do not sit in the middle of your other traffic.

Do you keep DNS logs? Is my IP stored?

No. DNS query logging is switched off — the resolver does not record which domains are looked up or from which IP. (The website itself keeps ordinary visit logs when you browse these pages; see the privacy policy.)

Can I apply it only to the receiver, not my whole network?

Yes — and that is what we recommend. Enter our address as the DNS server in the receiver’s own network settings. Then only the receiver uses it; every other device on your network is untouched.

Should I set it on the whole router?

We recommend against it. Pointing your router’s DNS entirely at one server makes every device depend on it, so a single mistake can disrupt normal browsing across the house — not just Internet Radio. Set it on the receiver instead. If you already run your own DNS server (Pi-hole, AdGuard Home, OpenWrt, MikroTik or pfSense), you can add an override for just the radio domains — see the setup guides.

Could this expose banking or e-mail?

No. We never redirect banking, e-mail, payment or any other domains, and we cannot read traffic that uses HTTPS to sites we do not host. We only answer for the radio-directory names.

How do I undo it?

Set the receiver’s DNS back to Automatic (DHCP), or remove our address from the router’s DNS field. The change takes effect immediately — nothing is left behind on your device.

Independent security check — verified 13 Oct 2026

We periodically re-run these checks against the live resolver and publish the result:

• No domain hijacking. Sensitive domains we tested — banks, government portals, PayPal, Google — returned exactly the same addresses as public resolvers (Cloudflare 1.1.1.1). Only the radio-directory domains above resolve to our server; nothing else is redirected.
• Abuse protection. The resolver refuses amplification-prone ANY queries and rate-limits each source IP to 30 requests/second, so it cannot be weaponised for attacks on others.
• No query logging. It keeps no record of which domains are looked up or which IP asked.
• Upstream. Anything that is not a dead radio domain is forwarded unchanged to Cloudflare (1.1.1.1) and Google (8.8.8.8).
• Transport. The website uses HTTPS with an auto-renewing certificate; receivers that cannot do TLS use plain HTTP for the directory only.

Spotted something that looks wrong? Tell us and we will investigate and update this page.