Many resellers sell under their own brand. They want their customers to see tv.example.com, not your domain or the IP of your server. And you may want each reseller to stay inside their own brand, so that their customers cannot use your main domain or another reseller's domain.

With Reseller DNS you give a reseller one or more domains. With the Reseller DNS lock, the clients of that reseller can only connect through those domains.

Several domains per reseller and the DNS lock need engine 2.2.1 or later on your main server. With an older engine, Reseller DNS accepts a single domain and there is no lock. See Update the Engine.

Before you start

Each domain must point to your servers in your DNS provider. The panel stores the name, but it does not create the DNS record for you.

Step 1: Add the domains of a reseller

  1. Open Resellers Network > Overview and click Edit on the reseller. You can also do it when you create the reseller in Add Reseller/Admin.
  2. In Reseller DNS, type a hostname without http:// or https://, for example tv.example.com, and press Enter. Repeat for each domain.
  3. Click Save Changes.

The first domain in the list is the one used in the playlist links that the reseller sees in their panel.

Resellers can do the same for their own sub-resellers in Resellers Network (Add Subreseller, or Edit on a sub-reseller), with the same Reseller DNS field. Each sub-reseller has their own list. They do not inherit the domains of the reseller above them.

If you type https://tv.example.com:8080, the panel keeps only tv.example.com. Only the hostname is stored, without scheme, port or path.

Step 2: Turn on the lock

  1. Open Settings > Resellers.
  2. Turn on Reseller DNS lock. It saves at once, and the line below the option changes to Enabled.

From then on, the clients of every reseller that has domains can only connect through those domains. Any other host is blocked, including your main domain and the IP of the server. Resellers without domains are not affected. The change applies in about 1 minute.

Before you turn on the lock, tell each reseller with domains. Their customers must have the apps set up with the reseller's domain. Clients that use the server IP or your domain stop working at once, with the same answer as a wrong password.

Step 3: See who was blocked

Every blocked attempt is listed in the DNS Blocks tab of Logs:

  • Administrators: open Servers > Logs > DNS Blocks. Your group needs access to servers.
  • Resellers: open Logs > DNS Blocks. You see your own clients and the clients of your direct sub-resellers.

The columns are Date, Line, Reseller, Host used, Endpoint, IP and User-Agent. Use Search by host, line or IP... and the date range to filter.

Host used is the key column. If it shows your domain or the server IP, that customer's app still points to the old address, and the reseller must give them their own domain.

Administrators can empty the tab with Clear Logs.

Common problems

  • The clients of a reseller stopped working after you turned on the lock: they still use the server IP or your domain. Check Host used in DNS Blocks and ask the reseller to update the apps.
  • A reseller without domains is affected: check that no old domain is left in their Reseller DNS.
  • The DNS Blocks tab is missing: your main server runs an engine older than 2.2.1, or your group has no access to servers.
  • A sub-reseller's clients are blocked on the domain of the reseller above: this is expected when the sub-reseller has their own domains. Their clients can only use the domains in the sub-reseller's own Reseller DNS.