Domains, DNS and application hosting
Connect Your App to a Custom Domain
Make the address lead to the application customers need.
Your app is hosted and you have a domain. The next step is connecting the address, host and HTTPS configuration, then testing the customer journey at that address.
Your app is hosted and you have a domain. The next step is connecting the address, host and HTTPS configuration, then testing the customer journey at that address.
A domain name, its DNS records and the application host each have a separate role.
Make the address lead to the application customers need.
The domain provides the address. DNS directs requests. The host must recognize that address and serve the right application with a valid HTTPS setup.
Gridfused helps founders connect and verify those parts around the application they already run.
Product and software development for founders connecting an application to a customer-facing domain.
Follow the address
The App Works on Its Hosting URL. Why Not on Your Domain?
Imagine an app opens at the host's temporary address but not at app.example.com. First check which account controls the domain and which DNS service is authoritative. Then confirm that the host has been configured to accept that exact address.
Use the records and ownership verification required by the actual host. Check the returned destination and HTTPS certificate, then try a real sign-in or customer action at the new address.
Preserve existing records used by email or other services. A DNS change should have a clear owner and a recovery plan.
Recognise the issue
What Can Prevent a Custom Domain From Working?
The wrong DNS account was edited.
The registrar and the authoritative DNS provider may be different services.
The host does not recognize the name.
The destination may need the exact domain configured and verified before it serves the app.
The record points elsewhere.
Compare the current DNS response with the instructions for the selected host and address.
HTTPS is not ready.
Check certificate issuance and the host's validation requirements for the exact name.
Sign-in returns to the old address.
Authentication callbacks and other integrations may still refer to the previous domain.
Choose the right change
Which Domain Setup Does Your App Need?
The answer depends on whether the app uses the root domain, a subdomain or an existing address.
1. Connect a new subdomain
Use a dedicated address such as app.example.com while preserving the rest of the domain setup.
2. Connect the root domain
Use the main business domain if it is meant to serve the application.
3. Move an existing app address
Plan a cutover when the domain already serves an application or other customer-facing service.
How to choose
Identify which address customers should use and what currently depends on it.
1. Connect a new subdomain
Follow the destination host's record and verification instructions for that exact name.
2. Connect the root domain
Root-domain support and record requirements vary by DNS and hosting provider. Check existing services before changing records.
3. Move an existing app address
Record the current configuration, dependencies, verification steps and conditions for returning to the previous destination.
Follow the selected host's documented setup and verify the result without disturbing unrelated records.
A domain connection map
What Should Be Checked Before the Address Goes Live?
Trace the name from its owner through DNS and the host to the customer-facing application.
1. Domain and DNS Accounts
Find the authorized owner and the DNS service in use.
How the work unfolds
How Gridfused Helps Connect Your App Domain
Step 1 — Understand the Current Address
We identify the app host, domain owner, DNS service and any existing use of the name.
Step 2 — Plan the Configuration
We map provider requirements, affected records and customer-facing dependencies.
Step 3 — Configure the Agreed Change
When implementation is included, we apply the authorized host and DNS changes within the agreed scope.
Step 4 — Verify the Customer Journey
We check the destination, HTTPS and selected application actions, then document the configuration and ownership.
A defined scope
What Can the Engagement Produce?
Domain assessment
A review may include:
- An inventory of the domain, DNS and hosting accounts.
- Current and intended routing for the application.
- Dependencies and risks for the proposed change.
- A verification and recovery plan.
Implementation
Agreed work may include:
- Host and DNS configuration for the intended address.
- HTTPS and domain verification checks.
- Review of relevant sign-in or integration addresses.
- Documentation and an operating handover.
Understand the roles
Who Controls the Domain and the App?
These services may be managed in different accounts.
Knowing which one is authoritative prevents changes in the wrong place.
Identify:
Domain registrar
The account responsible for the domain registration and its name server settings.
DNS provider
The service that answers DNS queries for the domain and holds the relevant records.
Application host
The service that receives requests for the configured name and serves the application.
When to get help
When Is Domain Support Useful?
Consider a focused engagement when:
The app works at the host address but not on your domain.
You are unsure which DNS account controls the records.
HTTPS or domain verification is failing.
A sign-in or email link still points to the previous address.
The domain already supports other business services that must remain reachable.
Before changing DNS
Frequently Asked Questions
Have a question about your domain?
How do I connect my app to a custom domain?
Identify the authoritative DNS provider, configure the name on your app host, and add the records the host requires. Verify the destination, HTTPS and the customer journey.
Does buying a domain host my app?
No. A domain is an address. The application still needs a hosting environment that can run or serve it.
Should I use a root domain or a subdomain?
Choose the address that fits the product and existing domain use. Provider support and record requirements differ, particularly for root domains.
Why does HTTPS show a warning?
The certificate may not yet be issued or may not match the name. Check the hosting provider's domain verification and certificate configuration; do not bypass the browser warning.
Will the change affect my email?
Email can depend on DNS records for the same domain. Identify and preserve those records when planning the application change.
What happens to sign-in?
Authentication providers may require the new address in their redirect or allowed URL settings. Test the full sign-in journey after configuration.
Have a question about your domain?
Your next step
Give Your App an Address Customers Can Use.
Start with the host, domain and the result you see today.
We can help map the configuration, connect the intended address and verify the application journey.
Gridfused helps founders make the technical connections that support a working product.
A few sentences are enough to begin.
Tell us where the app is hosted and which domain you want to connect.
Check the address all the way through to the app.