How do domains, DNS, GitHub, and hosting fit together?
The registrar manages the domain, authoritative DNS supplies records, hosting serves the site, and Git stores code.
On this page
Direct answer
The registrar manages the domain, authoritative DNS supplies records, hosting serves the site, and Git stores code. Identify the current owners and use the hosting console’s current values rather than old IPs or an unplanned nameserver switch.
When to use
You are connecting a domain or diagnosing why a deployment is not reachable through it.
Step by step
Inventory the domain and records
Check registrar, renewal, authoritative nameservers, DNSSEC, and existing services. Export the complete DNS zone before changes, preserving mail and verification records. Public queries cannot enumerate the whole zone.
Validate hosting before binding
Use the intended repository, configure server-side environment variables, and produce a reversible deployment. Follow its current domain and DNS instructions. Prepare mail and DNSSEC migration before changing nameservers.
Verify HTTPS and redirects
Check the primary host, www, HTTP-to-HTTPS, representative paths, and query preservation. Confirm the certificate and content, and retest mail services. Diagnose redirect loops rather than weakening TLS validation.
Worked example
Hypothetical exercise, not a real performance claim.
The deployment is ready but the root domain still points elsewhere. Identify the authoritative DNS provider before changing its records; edits in a nonauthoritative dashboard do not change public resolution.
Action checklist
Reusable templates
Domain and DNS change record
Domain / registrar / renewal:
Authoritative DNS, old NS, DNSSEC:
Complete zone snapshot location:
Mail and service records to preserve:
Hosting project and current console instructions:
Exact change, rollback criteria, and owner:
Release verification
Deployment version and status:
Primary host / www / HTTP redirects:
Path and query preservation:
Certificate and page content:
Authoritative DNS check:
Mail test and unverified items:
Pitfalls
Either www or the bare domain can be primary; consistency matters. A keyword domain does not guarantee ranking. Do not delete unknown DNS records or assume nameserver migration is always required.
Related guides
-
How do you launch a useful minimal site quickly after finding demand?
-
What hosting, 404, bandwidth, and caching problems should you check?