Services and DNS
Publishing a service#
A service is a name, a target, and the connectors that can reach it:
1 2 3 4 | |
| Flag | Notes |
|---|---|
--target |
host:port as seen by the connector, in its own network. May be a DNS name |
--protocol |
tcp or udp. One service, one protocol |
--connector |
One or more. All of them must be able to reach the target |
The service is now named payments.prod.acme and reachable as
payments.prod.acme.prox — but only to identities a rule allows.
How names resolve#
The connector runs a split-horizon resolver for the .prox zone. Clients in
the network point at the connector for that zone and resolve normally:
1 | |
The returned address is local to the connector and exists only to give the client something to connect to; it is not routable anywhere else and is not an address on the remote network. This is what makes overlapping private ranges a non-issue.
Three ways to wire up resolution:
| Method | When |
|---|---|
Point the network's resolver at the connector for prox. |
Cleanest. One change, every client works |
/etc/resolv.conf or systemd-resolved per host |
Small deployments |
| Connect by name through the connector's local listener | When you cannot change DNS at all |
Protocols#
TCP and UDP are carried transparently. The connector does not parse your protocol, terminate your TLS, or rewrite anything — it carries bytes between the client and the target.
Two consequences worth knowing:
- Your own TLS stays end-to-end. Certificate pinning works, mTLS works, and the certificate your client validates is the target's.
- Protocols that embed addresses need care. Anything that advertises its own IP inside the payload — some legacy FTP modes, SIP, certain clustered databases — can hand the client an address that means nothing on its side. Publish those as individual services per endpoint rather than expecting discovery to work.
Listing and removing#
1 2 3 | |
Deleting a service immediately stops resolution and new connections.
Established sessions are closed. Rules that referenced it remain and start
denying with service_unknown, which is deliberate — a dangling rule should be
visible, not silently dropped.