Name solution with Local HAproxy+services?
-
This feels like a Very Dumb Question -- just my style ;)
Context: local LAN. Nothing visible externally.
I have multiple local LAN servers with three available interaction methods:
- SSH access (xyz.example.com)
- Web server (https://xyz.example.com)
- SMB (Samba) shares (\xyz in Windows etc)
SSH doesn't matter much for naming, as the name is stored in PuTTy. I am using xyz_server.example.com to go directly to the servers.
HAproxy should take care of SSL certs. For that, I need xyz.example.com to point to the pfSense gateway. My current solution: for each server, configure custom static DNS aiming xyz at 192.168.1.1
But that leaves me in a pickle for Samba. Windows Really Wants to find xyz aimed at the real server, not at pfSense.
Suggestions MOST welcome!
(I could use www.xyz.example.com aimed at HAproxy... it works, but is very painful: no more wildcard certs. :(
To use www, create custom dns for host "www" and subdomain "xyz.example.com. ) -
we decided to go with:
xyz-web -- for all internal web interfaces
