Skip to main content
New insight available. View changelog →
Start Tier 1

Web & APIs · SupportRoadmap Docs

DNS and networking basics for software support

DNS turns a hostname into an address; TLS encrypts the connection; network path issues sit between the customer and the product. In software support you rarely fix infrastructure, but you often need to tell whether a failure looks like DNS, certificate, connectivity, or the application itself.

By Tom Ulman · Published · Last reviewed

What support owns vs what infrastructure owns

You rarely change DNS records or TLS certificates as a Tier 1 or Tier 2 agent. You do need a working mental model so you can say whether a failure looks like “name does not resolve,” “certificate mistrusted,” “path blocked,” or “application error after a successful connection.”

DNS

DNS maps a hostname (app.example.com) to an address. Support-relevant failures include wrong subdomain, stale CNAME after a migration, split DNS (works in office VPN, fails at home), and brand-new domains still propagating. If the browser never reaches your product, DevTools may show DNS or connection errors rather than HTTP status codes.

TLS and certificates

TLS encrypts the session. Customers see certificate warnings when names do not match, certificates expire, or corporate proxies intercept HTTPS. Ask what exact URL they open, whether other networks work, and whether the warning mentions name mismatch or expiry—then route to the team that owns certificates.

Path vs application

  • Path issues — cannot connect, timeouts before any HTTP response, works on mobile data but not office Wi‑Fi.
  • Application issues — TCP/TLS succeed, HTTP returns 4xx/5xx or bad JSON (status codes, DevTools).

Keep it support-specific

This is not a networking certification track. If the product loads and APIs return application errors, stay in product investigation. Escalate infrastructure only with clear evidence that the request never reached the app.

Common mistakes

  • Blaming “DNS” for every outage when APIs are returning 500s.
  • Ignoring corporate proxy or firewall differences between environments.
  • Asking customers to flush DNS before confirming the hostname and error text.

Related concepts

Primary sources

Prefer an ordered path? Open the related roadmap skill and work through it with the curated resources.

Learn this in order