maybe switching the local domains from .local to .test removes the need of a proxy anyway, since .test is actually a standardized dev/local TLD 🙂 cc @colossal-hair-13755

cc @plain-barista-64036

Was just proposing the proxy since the gateway is doing the routing to the containers at the moment, dinghy would just be a replacement for convenience, making the setup of different projects und different domains a lot easier, ... but yes *.test would be the lowest hanging fruit at the moment 🙂

I ended up placing all the domains needed into the Linux host /etc/hosts file (which is kinda 1990 technology ;)), because at least modern Ubuntu distributions use avahi and scrue up any clean attempt to configure .local nicely without /etc/hosts hacking. But in general, with debian/Ubuntu or RedHat like systems, the "recommended" way to masquerade domains to local addresses is simply... well - masquerading it! As a proxy is a little bit heavy-weight just for this purpose: • install dnsmasq package • Make NetworkManager to use it (usually found in a typical LSB configuration somewhere under /etc/NetworkManager/<>.conf or /etc/NetworkManager/conf.d/<>.conf

dns=dnsmasq

• Add the local addresses you want to masquerade to your own dnsmasq plugin configuration file

# New file, for instance: /etc/NetworkManager/dnsmasq.d/devbox

local=/test/
local=/localhost/
local=/local/

address=/test/127.0.0.1
address=/localhost/127.0.0.1
address=/local/127.0.0.1

This is it. Everything mentioned there will go to localhost, everything else will fallback to dns / mdns or other internal configuration of name lookups. However, on modern Ubuntu distributions, and I guess also on other Linux derivates, .local is not allowed anymore and usually used by avahi daemon or "forbidden" in some default mdns configurations, so you will experience special defects only with this TLD like I did. And because browsers like Chrome will still complain an simply not work with this "special" domain (just try setting up self-signed certificates for a .local domain and accessing it with Chrome, good luck! ;-)), IMHO the easiest and most elegant way would be to simply follow the IETF recommendations and avoid any other problems from the beginning. Which is: use .test for local domains instead. "The first is using a generic top-level domain. Generic TLDs like 

.local

, 

.lan

, 

.corp

, etc, are now being sold by ICANN, so the domain you’re using internally today – 

company.local

 could potentially become another company’s property tomorrow. If you’re still not convinced, here are some more reasons why you shouldn’t use 

.local

 in your Active Directory domain name"

@victorious-account-76850 You can set any domain names in your deploy.yml as you fully control it on your side. Anyway thanks for the hint.