A recognizable address
Use a hostname that fits your customer-facing identity.
Strong 8K
Private Domain
Setup.
Your address. Your brand. A clearer connection.
Prepare your custom domain for the Strong 8K reseller workflow, understand the DNS requirements and test the connection before sharing it with customers.
Domain ownership · DNS configuration · Connection checks
connect.example.comIllustrative domainOne familiar address.
A connection you understand.
A private domain gives a supported service endpoint an address under your control.
For an IPTV reseller, this can help keep customer instructions consistent with the brand. The exact setup depends on the destination supported by your account.
First identify what the domain connects to. A customer connection URL and a reseller-panel login are different. Confirm the supported destination before setting DNS.
Control of your domain
Manage registration, renewal and DNS access through your own accounts.
Clearer setup instructions
Keep the chosen hostname, supported protocol and port documented together.
Before you
touch DNS.
Collect these details first. A complete set of instructions makes the next step easier.
- A domain or subdomain you control
- Access to the authoritative DNS provider
- The exact record type, name and target
- Supported protocol, port and HTTPS details
- Any required service-side verification
Domain connectionIllustrative example
CUSTOM HOSTNAME
connect.example.com
- Destination
- Confirm with provider
- DNS target
- Use the supplied value
- Service verification
- Required if instructed
Keep the exact setup instructions beside you. This example does not show a live Strong 8K account.
Turn the details
into a plan.
Choose the type of instruction you received. Your checklist updates to match it.
This planner stays in your browser. It does not check availability, query DNS or change your account.
From domain
to tested connection.
A practical six-step workflow. Follow the current instructions supplied for your account wherever they differ from this general guide.
- 01
Choose the right destination
Confirm whether you are connecting a customer service address or a reseller login address. Record the supported protocol and port.
- 02
Choose your hostname
Use a domain you control. Ask whether a root domain or a dedicated subdomain is supported before changing DNS.
- 03
Get the current instructions
Obtain the exact record type, name, target and any verification requirement from your panel or support.
- 04
Create the DNS record
Edit records at the authoritative DNS provider. Copy the supplied values exactly and preserve unrelated records.
- 05
Complete provider verification
Follow the domain registration or verification step required by the service. DNS resolution alone may not activate the hostname.
- 06
Test before sharing
Check resolution, supported HTTPS, the intended destination and one supported customer device. Then confirm the migration plan.
Read the record.
Then save it.
Each field has a separate job. Choose a record type below to see an educational example.
Examples only: these values are not Strong 8K server details.
DNS record anatomyExample only
- Type
- CNAME
- Name / host
- connect
- Target / value
- target.example.net
- TTL
- Use provider guidance
A CNAME maps one hostname to another hostname.
Check the whole
connection.
A saved DNS record is only one part of a working setup.
- The hostname resolves to the intended target
- The provider has accepted the hostname
- The supported protocol and port work
- HTTPS presents the correct certificate, if supported
- A supported device accepts the connection
DNS cache updates take different amounts of time. HTTPS also needs configuration at the destination; adding a DNS record does not automatically create a certificate.
Something not
connecting?
Start with the hostname and the current instructions. Check one cause at a time before making further changes.
Domain not found
Check the spelling and the authoritative DNS zone. Confirm the record was saved for the exact hostname and allow cached responses to expire.
Wrong destination
Compare the record target against the supplied value. Check for conflicting records at that hostname without changing unrelated website or email records.
Certificate warning
Confirm that HTTPS is supported and the destination has a certificate covering the exact hostname. DNS resolution alone is not an HTTPS test.
Works on one device only
Compare protocol, port, app support and cached settings. Share the precise error with support through a private channel.
Your domain.
Keep control.
Protect the accounts that control your address, and make changes with a clear record of what was there before.
Protect domain access
Use a unique password and enable two-factor authentication at your registrar and DNS provider.
Keep ownership current
Maintain recovery details and domain renewal settings so you retain control of the address.
Review changes carefully
Keep a record of the original DNS values before editing the selected hostname.
Verify the connection
Use the supported protocol and check certificate validity when HTTPS is available.
Share only what is needed
Send customer connection details privately; keep account passwords out of public screenshots.
Private domain
setup, explained.
Answers to the questions that matter before you connect a hostname.
What is a Strong 8K private domain?
A domain or subdomain you control that is connected to a supported service endpoint. Confirm whether your account supports a customer connection address, a panel login address, or both: these are different destinations.
Can I use a subdomain?
Ask which hostnames your provider supports. A dedicated subdomain such as connect.example.com can keep service DNS separate from the records used by your main website.
Do I need an A record or a CNAME?
Use the record type specified for your account. An A record points to an IPv4 address; a CNAME points to another hostname. Neither should be guessed.
Does a private domain include a branded app?
A custom address does not automatically provide a branded app, custom panel design or separate infrastructure. Confirm which branding options are included.
How long do DNS changes take?
Timing depends on cached responses, TTL and any nameserver changes. Repeatedly editing a correct record can complicate troubleshooting. Check the authoritative DNS settings and allow existing caches to expire.
Can I use Cloudflare?
If the service supports your DNS configuration, Cloudflare can host the records. Confirm whether the record must be DNS-only or proxied; do not assume ordinary web proxy settings support every service or port.
Why is HTTPS not working?
DNS alone does not issue a certificate or configure the destination server. The endpoint must support HTTPS and present a valid certificate for your exact hostname.
Will this change existing customer credentials?
Do not assume it will. Confirm the supported URL format, protocol, port and migration procedure with support before updating existing customer devices.
Should I remove old DNS records?
Review records for the exact hostname before changing anything. Keep unrelated website and mail records. Resolve conflicts using your DNS provider’s instructions.
Is a private domain private or anonymous?
Here, private domain means a custom address under your control. It does not mean the address is hidden, the infrastructure is independently owned, or service availability is guaranteed.
Keep your reseller
workflow connected.
Ready for your
own address?
Get the current private-domain instructions for your Strong 8K account before changing DNS.
Get setup details on WhatsApp ↗
Have your intended hostname ready. Keep passwords private.