mercury:~ raymond$ sudo killall -HUP mDNSRespondermercury:~ raymond$ nslookup opnsenseServer: 192.168.130.129Address: 192.168.130.129#53Name: opnsense.myradon.netAddress: 192.168.132.1Name: opnsense.myradon.netAddress: 192.168.130.129Name: opnsense.myradon.netAddress: 192.168.133.129Name: opnsense.myradon.netAddress: 192.168.131.129
#Access control for remote IP Rangeaccess-control-view: 192.168.130.128/25 bridgelanaccess-control-view: 192.168.131.128/29 wirelessguestaccess-control-view: 192.168.132.1/24 bridgeiotaccess-control-view: 192.168.133.128/29 dmz#View to return for external range only defined ip for firewall, assumed 192.168.100.254 is the IP of opnsenseview: name: "bridgelan" local-zone: "myradon.net" transparent local-data: "opnsense.myradon.net A 192.168.130.129" local-data: "opnsense A 192.168.130.129" #view-first Unbound will try to use the view’s local-zone tree, and if there is no match it will search the global tree. view-first: yesview: name: "wirelessguest" local-zone: "myradon.net" transparent local-data: "opnsense.myradon.net A 192.168.131.129" local-data: "opnsense A 192.168.131.129" #view-first Unbound will try to use the view’s local-zone tree, and if there is no match it will search the global tree. view-first: yesview: name: "bridgeiot" local-zone: "myradon.net" transparent local-data: "opnsense.myradon.net A 192.168.132.1" local-data: "opnsense A 192.168.132.1" #view-first Unbound will try to use the view’s local-zone tree, and if there is no match it will search the global tree. view-first: yesview: name: "dmz" local-zone: "myradon.net" transparent local-data: "opnsense.myradon.net A 192.168.133.129" local-data: "opnsense A 192.168.133.129" #view-first Unbound will try to use the view’s local-zone tree, and if there is no match it will search the global tree. view-first: yes
@stefanpf Thanks a lot! It works great Maybe for someone else comes in handy; Add to field "Custom options";Code: [Select]#Access control for remote IP Rangeaccess-control-view: 192.168.130.128/25 bridgelanaccess-control-view: 192.168.131.128/29 wirelessguestaccess-control-view: 192.168.132.1/24 bridgeiotaccess-control-view: 192.168.133.128/29 dmz#View to return for external range only defined ip for firewall, assumed 192.168.100.254 is the IP of opnsenseview: name: "bridgelan" local-zone: "myradon.net" transparent local-data: "opnsense.myradon.net A 192.168.130.129" local-data: "opnsense A 192.168.130.129" #view-first Unbound will try to use the view’s local-zone tree, and if there is no match it will search the global tree. view-first: yesview: name: "wirelessguest" local-zone: "myradon.net" transparent local-data: "opnsense.myradon.net A 192.168.131.129" local-data: "opnsense A 192.168.131.129" #view-first Unbound will try to use the view’s local-zone tree, and if there is no match it will search the global tree. view-first: yesview: name: "bridgeiot" local-zone: "myradon.net" transparent local-data: "opnsense.myradon.net A 192.168.132.1" local-data: "opnsense A 192.168.132.1" #view-first Unbound will try to use the view’s local-zone tree, and if there is no match it will search the global tree. view-first: yesview: name: "dmz" local-zone: "myradon.net" transparent local-data: "opnsense.myradon.net A 192.168.133.129" local-data: "opnsense A 192.168.133.129" #view-first Unbound will try to use the view’s local-zone tree, and if there is no match it will search the global tree. view-first: yes