dnsmasq-service: all hostnames resolve to nginx-loadbalancer

[runleveldev]

Issue: Separate DNS for dynamic host resolution instead of mapping all queries to the Nginx server

Description:
Currently, all DNS queries for the opensource.mieweb.org and opensource.mieweb.com domains resolve to the Nginx load balancer’s IP. This includes unqualified hostnames resolved via the DHCP-supplied search domain, which prevents direct hostname-based access to other hosts on the network.

Recommendation:
Introduce a separate domain (e.g., cluster.mieweb.org) where DHCP-leased hosts are dynamically registered and resolved. For example, a host with a DHCP lease should resolve as host.cluster.mieweb.org to its assigned IP.

Benefits:

• Enables per-host addressability without conflicting with proxy domains
• Preserves proper internal DNS resolution
• Simplifies service discovery within the network
• Reduces reliance on static Nginx mappings for non-proxied hosts

[runleveldev]

RFC on whether this is the right design for this. Put more simply:

1. *.opensource.mieweb.org resolves to the load balancer, both internally and externally, for consistent port/ssl handling
2. *.cluster.mieweb.org resolves to the container's internal IP, and only internally allowing the LB to contact containers by hostname rather than needing to store their IP outside of dnsmasq