So you have a server with two NICs, and you want Domino and the Nomad server task to only bind to one of the NICs. Here's how you do I do it:
Here is an example:
Domino/Nomad NIC's IP Address is 111.111.111.111
Other Web server NIC's is 222.222.222.222
In the Domino Server's Notes.ini file include:
TCPIP_TCPIPAddress=0,111.111.111.111
In the Domino Server's Data directory, create a file named nomad-config.yml, and in it, include the following:
#
host: '111.111.111.111'
servers:
cn=dominoservername/o=organization: 111.111.111.111
Restart the Domino server, load Nomad, and you should be ready to go.
2 comments:
You should be able to use the same approach (i.e. configure two IP addresses on the server, that runs Domino and Nomad server) to run both Domino http and Nomad http on port 443. This will increase your chance, that users can reach your server as port 9443 might be blocked somewhere between a client and your server.
This is one way to do it. Usually you have a reverse proxy in front of it anyhow.
So for example with NGINX you could then use the SSL pre-read module to dispatch traffic on TCP layer and dispatch the Nomad traffic to port 9443 on the same back-end IP.
That way you can run as many HTTPS traffic on a single IP address.
NGINX can be a separate box. Or run on the same box.
Here is an example from my blog post -> https://blog.nashcom.de/nashcomblog.nsf/dx/nginx-tcp-stream-with-sni-support.-more-than-helpful-for-lab-environments.htm
Post a Comment