1
18.7 Legacy Series / multiple internal domain names?
« on: September 15, 2018, 01:37:56 am »
Hi, I'm using the acquisition of new hardware as an opportunity to migrate from pfSense to OpnSense. I have my new box working, but I'm struggling with internal domain names. My box has multiple internal interfaces, and I have totally separate LAN's configured on each: DMZ, guest, development, trusted, etc. Each LAN has totally separate IP addresses: 10.10.0.0/16, 192.168.1.0/24, etc.
The problem is I want a unique internal domain name on each LAN: MyName1.test, MyName2.test, Public_Domain.com (on the DMZ), etc. No matter what I try, DHCP assigns everything with the same domain name. Specifying a unique domain name in DHCP4 on each interface makes no difference. I've tried both DNSmasq and Unbound. While both have the option to override FQDN on specific IP addresses, that's not an acceptable solution. I want to decrease my administrative overhead, not increase it!
I found something on the web where DNSmasq could have a custom configuration like
domain=MyName1.test,10.10.0.0/16
domain=MyName2.test,192.168.0.0/24
but that doesn't seem to work.
Am I trying to do the impossible? Surely, I'm not the first one with this need. What's the trick?
Thank you!
The problem is I want a unique internal domain name on each LAN: MyName1.test, MyName2.test, Public_Domain.com (on the DMZ), etc. No matter what I try, DHCP assigns everything with the same domain name. Specifying a unique domain name in DHCP4 on each interface makes no difference. I've tried both DNSmasq and Unbound. While both have the option to override FQDN on specific IP addresses, that's not an acceptable solution. I want to decrease my administrative overhead, not increase it!
I found something on the web where DNSmasq could have a custom configuration like
domain=MyName1.test,10.10.0.0/16
domain=MyName2.test,192.168.0.0/24
but that doesn't seem to work.
Am I trying to do the impossible? Surely, I'm not the first one with this need. What's the trick?
Thank you!