Networking
Publish generated and custom domains, use private endpoints, and diagnose reachability.
Open a service node and select Networking.
Generated domain
A supported public web service can receive an Autodisc-managed hostname. The service must listen on its configured port and return a successful health response before the route becomes useful.
Use the generated domain first when diagnosing an application. It separates runtime health from custom DNS problems.
Custom domains
- Add the exact hostname under Custom domains.
- Copy the DNS target shown by Autodisc.
- Create the requested record at your DNS provider.
- Wait for DNS visibility and ownership verification.
- Confirm route publication, HTTPS, and application response.
The dashboard shows these stages separately. A domain can be DNS-correct while the application is still unhealthy.
Private networking
Services and databases in one project environment should use their private hostnames and ports. Private endpoints avoid exposing internal traffic and should be preferred for API-to-database, worker-to-cache, and service-to-service communication.
Use injected variables or resource bindings rather than hardcoding private hostnames into source.
TCP publication
TCP publication is available only for supported service and placement types. Publishing a TCP port makes a non-HTTP protocol reachable externally; confirm authentication and protocol security before enabling it.
Troubleshooting
| State | What to check |
|---|---|
| DNS not configured | Record name, type, target, and provider proxy mode |
| Ownership pending | DNS propagation and exact hostname |
| Route pending | Service port and deployment health |
| HTTPS pending | Ownership verification and certificate issuance |
| App not responding | Listen address, port, startup logs, and health endpoint |