Hey @cmdntd987,
On your DNS or Reverse proxy you would need to set a new A record that points the hostname to the internal host and that should take care of it.
Exact instructions are a bit tricky as there are hundreds of way this could be done depending on what you are using for routing and how your DNS is managed.
n8n itself doesn’t really listen for connections on a specific host it is more what it displays in the front end and what it reports to the outside world.
Looking at your env example from an n8n side all you would need to do is something like the below then just make sure you are pointing the dns records to the correct location and you should be all good.
N8N_HOST = n8neditor.mydomain.com
N8N_PROTOCOL = https
VUE_APP_URL_BASE_API = https://n8neditor.mydomain.com/
WEBHOOK_TUNNEL_URL = https://n8n.mydomain.com/
N8N_EDITOR_BASE_URL = https://n8neditor.mydomain.com/
This won’t fully restrict the admin interface to just n8neditor.mydomain.com though to do that you would need to look at implementing network rules to prevent some of the URI paths from being loaded.