Pointing a subdomain to Lumenario
Use this guide to create the DNS A record that connects a branded address such as <chosen_subdomain_name>.example.com to the IPv4 address supplied by Lumenario.
Have these details ready
Confirm these four items before opening the DNS control panel.
Exact hostname
Confirm the full address with Lumenario, for example
<chosen_subdomain_name>.example.com. The part before your domain—<chosen_subdomain_name>in this example—is the host label.Assigned IPv4 address
Copy the exact IPv4 address supplied by the Lumenario team. An A record accepts only the address: do not include
https://, a port, or a page path.Authoritative DNS provider
Edit records wherever the domain's active nameservers are hosted. That may differ from the company where the domain was purchased.
Access and approval
Use an account allowed to edit DNS. If another team owns the zone, send them this guide together with the exact hostname and IP.
DOMAIN PORTFOLIO · DNS
GoDaddy
Open the domain.
Sign in to the GoDaddy Domain Portfolio, then select the domain you want to use. This opens its Domain Settings page.
Open its DNS records.
Select DNS. Check that the page shows the correct parent domain before changing anything.
Check the exact host.
Search for the agreed prefix, such as
<chosen_subdomain_name>. If the hostname already has the intended A record, edit it. If it has a CNAME or redirect, confirm before replacing it.Add the A record.
Select Add New Record, then choose A from the Type menu.
Enter Lumenario's values.
For Name, enter only the prefix—
<chosen_subdomain_name>, not<chosen_subdomain_name>.example.com. Paste the assigned IPv4 address into Value. Leave TTL at its default unless told otherwise.Save and verify your identity.
Select Save. If Domain Protection is active, complete GoDaddy's identity-verification prompt.
DOMAIN LIST · ADVANCED DNS
Namecheap
Open Domain List.
Sign in to Namecheap, choose Domain List in the left sidebar, and select Manage beside the correct domain.
Confirm the nameserver mode.
On the Domain tab, check Nameservers. Continue here only for BasicDNS, FreeDNS, or PremiumDNS. If Host Records cannot be edited, the active zone is elsewhere.
Open Advanced DNS.
Select the Advanced DNS tab and find the Host Records section.
Add a host record.
Select Add New Record and choose A Record.
Enter the host and IP.
In Host, enter only
<chosen_subdomain_name>; Namecheap appends the parent domain. Paste the assigned IPv4 address into Value and leave TTL as Automatic.Commit the change.
Save the record row, then select Save All Changes if that control appears.
HPANEL · DNS / NAMESERVERS
Hostinger
Open the DNS zone.
In hPanel, go to Domains → Domain portfolio, select Manage for the domain, then choose DNS / Nameservers → DNS records.
Use the hosting-plan route if needed.
For a domain managed inside a hosting plan, the equivalent path can be Websites → select the site → Advanced → DNS Zone Editor.
Audit the hostname.
Use the DNS-record search to find
<chosen_subdomain_name>. Check for outdated A or AAAA values. If this iswww, an existing CNAME must be removed before an A record can use that same name.Select A.
In Manage DNS Records, choose A as the record type.
Enter the record.
Set Name to the prefix only, set Points to to Lumenario's IPv4 address, and leave TTL at the default
14400seconds unless instructed otherwise.Add the record.
Select Add Record. Hostinger's separate “create a subdomain” hosting workflow is for content hosted by Hostinger; an externally hosted Lumenario address requires this DNS record plus Lumenario's server setup.
ORDERS · DNS RECORDS
BigRock
Open the customer portal.
Sign in at myorders.bigrock.in.
Select the domain order.
Open Orders, then select the domain whose subdomain will point to Lumenario.
Open DNS Records.
Choose DNS Records. Confirm that the domain uses BigRock's standard nameservers; otherwise use the matching panel below.
Add an A record.
Select Add Record and choose A or IPv4 A as the record type.
Enter the Lumenario destination.
Set Name / Host to the prefix only, such as
<chosen_subdomain_name>, and set Value / Destination to the assigned IPv4 address. Leave TTL at its default unless instructed otherwise.Save the record.
Select Save, then re-open the record list and confirm the new entry shows the intended hostname and IP.
Using a different BigRock DNS panel?
Premium DNS — for nameservers ns1.nudns.com through ns4.nudns.com, use Premium DNS → Manage → Add Record.
Linux shared hosting — use cPanel → Zone Editor, then add or edit the A record there.
Windows shared hosting — use Plesk → Hosting & DNS → DNS.
ROUTE 53 · PUBLIC HOSTED ZONE
AWS Route 53
Open Route 53.
Sign in to the AWS Management Console, open Route 53, and select Hosted zones.
Select the public parent zone.
Choose the public hosted zone for the parent domain, such as
example.com. A separate hosted zone for<chosen_subdomain_name>.example.comis not needed for this ordinary A record.Create a record.
Select Create record. For Record name, enter the prefix
<chosen_subdomain_name>; the console shows the parent-zone suffix beside it.Choose a standard A record.
Set Record type to A – Routes traffic to an IPv4 address. Keep Alias turned off because the destination is a literal IP address.
Enter routing values.
Paste Lumenario's IPv4 address into Value, select Simple routing, and use a TTL of
300seconds during setup unless your DNS policy requires another value.Create and confirm.
Select Create records. Confirm that Route 53 lists the new A record in the correct public hosted zone.
Match the symptom to the likely cause.
DNS caches do not update everywhere at once. Diagnose the record first; then separate DNS issues from Lumenario server or certificate setup.
| What you see | Likely cause | What to check |
|---|---|---|
| NXDOMAIN / host not found | The record is missing, unsaved, or was added in a non-authoritative DNS panel. | Confirm active nameservers and check the exact host label in the correct zone. |
| The A record cannot be added | A CNAME or redirect already uses the same hostname. | Confirm with Lumenario which existing record is safe to replace; do not delete unrelated records. |
| The old IP still appears | A resolver has cached the previous answer, or another A record remains. | Wait for the previous TTL and inspect all A values for the exact hostname. |
| Some visitors reach another server | An old AAAA record may still route IPv6 users elsewhere. | Inspect the exact hostname's AAAA record and ask Lumenario whether it should remain. |
| DNS is correct, but HTTPS fails | The hostname or certificate is not yet active on Lumenario's server. | Send Lumenario the hostname and public A-record result; do not keep changing DNS. |
The details that prevent accidental changes.
Do I need to register or purchase the subdomain?
No. You already control subdomains beneath your registered domain. Creating the A record creates the DNS hostname.
Will this affect the main website or company email?
Not when you change only the agreed subdomain record. Leave the root-domain record, MX records, and nameservers unchanged.
Should the IP field include https:// or a URL path?
No. An A-record value contains only an IPv4 address, such as four dot-separated numbers. Use the exact address supplied by Lumenario.
Why does the browser show a certificate warning after DNS resolves?
DNS routing and HTTPS provisioning are separate. Once the A record resolves correctly, Lumenario must finish configuring the hostname and its certificate.
How long should I wait?
Provider updates can appear within minutes, but cached answers may take up to 24–48 hours to clear. The old record's TTL—not only the new TTL—affects the cutover window.
Ask the Lumenario team to review the record
Send the full hostname and a public DNS result. The team can confirm routing, provision HTTPS, and validate the destination.