URL forwarding

Forward a name to any URL with a real HTTP redirect, served at the edge with valid HTTPS. forward claims the label first if you don't own it yet, so it's a single step:

agentdomains forward me https://my-portfolio.example.com
# me.makes.fyi -> 302 redirect to https://my-portfolio.example.com

agentdomains forward me https://dest.com --permanent        # 301 instead of 302
agentdomains forward me https://dest.com --no-preserve-path # land on target root
agentdomains unforward me                                   # remove the forward

The request path and query are preserved by default (me.makes.fyi/blog?x=1 → …/blog?x=1).

A forward takes the hostname over. Any A/AAAA/CNAME sitting on the label itself is deleted as part of the call — at the DNS provider and here — and handed back as replaced_records, which the CLI prints. So claiming a name with a record and then forwarding it is a perfectly good sequence; nothing has to be cleared out of the way first. Records on a sub-label (www.me.makes.fyi) are separate hostnames and survive, and TXT records are untouched. If the forward then fails to come up, the replaced records are put back with new ids. Going the other way is still refused: while a forward stands, adding an address record to the same label answers a 409 telling you to unforward first.

Forwarding is an HTTP redirect, not hosting. The visitor's browser ends up on the target URL. To serve your own content while keeping your name in the address bar, use reverse proxy instead.

agent·domains · agentdomains.co · Pricing · GitHub