d3servelabs/namefi

Search, register, and manage domain names and their DNS through Namefi; use when checking domain availability or pricing, buying/registering a domain, listing owned domains, editing DNS records (A, AAAA, CNAME, MX, TXT, NS, CAA...), configuring parking, forwarding, or auto-renew, or finding outbound leads for a domain.

Use when a user wants something they are developing reachable on a real hostname without a static IP — show off a local app on their domain, reach a home server or NAS or VPS from outside, an IP that keeps changing, set up dynamic DNS, point a Namefi domain at this machine, or check whether an ISP is CGNAT — and it is not yet clear whether they are on a VPS or behind home NAT, or which tool (namefi CLI, ddclient, none) they should use. This is the front door that diagnoses the situation and hands off to the right sub-skill. Takes an optional mode argument — simple (default; pick defaults from detection and present one plan to accept or modify) or advanced (confirm each decision individually).

Use when a user wants to expose a locally-developed service on a real hostname without a static IP — demo a local app publicly, reach a home server or VPS from outside, set up dynamic DNS, keep an A/AAAA record pointed at a changing public address, open router port forwarding (NAT-PMP/PCP/UPnP), or diagnose CGNAT — using the namefi CLI (namefi dyndns run|update|check, namefi dyndns creds set).

Use when a user wants to expose a locally-developed service on a real hostname without a static IP using ddclient — set up dynamic DNS with an existing ddclient install, write or debug a ddclient.conf for Namefi's DynDNS2 endpoint, run ddclient as a daemon/service, read its output, or map a Dyn return code (good/nochg/badauth/nohost/numhost/abuse) to a fix. Covers both a VPS (single public IP) and a homelab behind NAT.

Use when a user wants to expose a locally-developed service on a real hostname without a static IP and without installing a dynamic DNS client — update a Namefi A/AAAA record with a plain curl one-liner driven by cron/systemd-timer/launchd, or have the agent itself push updates via the Namefi MCP tools / /v-next/dns REST API. Covers both a VPS (single public IP) and a homelab behind NAT, plus the Dyn return codes.

Use when putting a reverse proxy in front of locally-developed services so a domain serves real HTTPS - getting a Let's Encrypt or ZeroSSL certificate for a home or VPS service, routing several apps behind one public IP and one port 443 by Host header, choosing between Caddy and Traefik, debugging ACME HTTP-01/TLS-ALPN-01/DNS-01 failures, wildcard certificates, "serve my local app over https on my domain", or "connection refused from outside but works inside".