Domino Server controller listening on all IPs
Daniel Nashed 24 January 2023 17:18:39
By default the server controller detects the host name and tries to bind to the host name only.
In most cases there is no need to bind to the host name, if you are just running with one partition (which should be the case for most of use in today's VM deployment scenarios).
Specially inside a Docker/K8s container name resolution can be a challenge.
I have used this parameter before to explicitly bind to the loop back address 127.0.0.1 for security reasons.
But this also works the other way around. The following parameter lets the server controller bind to all IP addresses on your host!
TCPIP_ControllerTcpIpAddress=0.0.0.0:2050
Please note "TCPIP" is the default port name, which might be different in some configurations.
I came up with his in a private discussion where an admin move Domino to a different box, where the server did have a different host-name.
This will be in my deployment best practices from now on and specially interesting for running Windows in side a container.
Special note:
If you specify 0.0.0.0, you can't connect locally any more, because 0.0.0.0 does not match your local IP address you are connecting with.
So if you need a local connection, specify the IP address of the machine that most likely stays permanently.
In case you are using DHCP with changing IPs this is more challenging. You need to make sure the name resolution works with DHCP and use the DNS name instead.
But this tip is still very useful for containers where you have no local connection!
If you only care to have a local console, 127.0.0.1 should be always the safest bet.
It will just always work, because the loopback IP and network interface is always there.
And it is more safe anyhow!
-- Daniel
- Comments [1]
![[HCL Domino]](../lotus-domino.gif){kind=small}
![[Domino on Linux]](../domino-linux.gif){kind=small}
![[Nash!Com]](../nashcom.gif){kind=small}
![[Daniel Nashed]](../daniel-nsh.gif){kind=small}