Configure a domain
Route a web application through Caddy, check DNS against its server, and understand automatic HTTPS prerequisites.
Domains are for Web applications. Bundar routes web traffic through Caddy on the selected server; application containers do not publish their own ports on the host. The server must be online with both Podman and the Caddy proxy running.
Set the port and domain
During application creation, the web application's Container Port is the port the application listens on inside its container (the default is 8080). Set it to the port your image or application actually uses. Add one or more domain names if you want Caddy to route those hostnames to the application. Auto SSL/HTTPS is enabled by default for each domain.
To change these settings later, open the application and its Domain tab. Edit the container port or domains. Changes remain pending until you choose Apply & deploy; Bundar applies them with a deployment. When there are no pending changes, Recheck domains queues a separate DNS and proxy-configuration check for saved domains with Auto SSL/HTTPS enabled.
Point DNS at the selected server
At your DNS provider, configure the domain so its public A/AAAA resolution points to the selected server's public address(es). If the server's configured host is a hostname, that hostname must itself resolve to A or AAAA addresses. Keep any extra address records consistent: Bundar reports a direct-DNS error if the domain's resolved addresses do not match the selected server.
Bundar recognizes domains whose resolved addresses are all in Cloudflare's published proxy ranges as being behind Cloudflare. A mixture of Cloudflare and direct addresses is reported as an error. The live DNS indicator shows whether records were found or the domain appears proxied; it does not by itself confirm that a direct record points to the selected server. The domain check and its result are asynchronous and appear in Bundar's notifications.
Automatic HTTPS and network access
With Auto SSL/HTTPS enabled, Caddy manages automatic HTTPS when the domain, DNS and network allow certificate issuance. Ensure inbound web traffic can reach the server on port 80 and 443. Bundar's Caddy setup publishes 80/TCP, 443/TCP and 443/UDP; the optional Firewalld setup is separate, and your provider firewall may need its own rules. Bundar cannot promise issuance until DNS and network routing are correct.
Turning off Auto SSL/HTTPS excludes that domain from Bundar's automatic HTTPS policy; it does not configure a certificate for you. For how to add a web application and its server, see Add an application and Add a server.