Topics

Hi guys, I have read many threads and I am not getting this to work.

Could someone please tell me the current best practices for enabling Chromecast with multiple VLANs?

- I have static IP's for my Chromecasts defined in an Alias.
- Chromecasts are on my IOT VLAN.
- Phones/PC's are on my LAN VLAN.
- I have tried mDNS and UDP Broadcast Relay plugins.

I would sincerely appreciate someone spending a few minutes to give me a step-by-step on which plugin is needed, and which firewall rules are needed.

If you wish, you can use my real subnets:
- LAN VLAN 192.168.2.0/24
- IOT VLAN 192.168.64.0/24

Greatly appreciated!

I am having the same issue as this 3 year old post:

https://forum.opnsense.org/index.php?topic=7983.0

I have multiple VLANs.  Each VLAN running its own interface DHCP on OPN.  The domain name is different for each VLAN.

The problem is that the dhcpleases.conf generated by Unbound has only the "main" domain name picked up from System > Settings > General > Domain name.

This ends up creating a resolution problem.

Help :)

HELP!

Code Select Expand

2021-07-26T10:19:43 unbound[41692] [41692:0] fatal error: Could not set up local zones
2021-07-26T10:19:43 unbound[41692] [41692:0] error: local-data in redirect zone must reside at top of zone, not at OPNsense.localhost A 192.168.2.2

I cannot start Unbound due to this.  I tried removing the host_entries.conf but it is regenerated.

I have removed custom options but no change.

I did have Register DHCP leases  and Register DHCP static mappings both checked/enabled, but I have sense unchecked and applied, even rebooted, and the host_entries.conf is still regenerated incorrectly.

Code Select Expand

# cat host_entries.conf
local-zone: "localdomain" transparent
local-data-ptr: "127.0.0.1 localhost"
local-data: "localhost A 127.0.0.1"
local-data: "localhost.localdomain A 127.0.0.1"
local-data-ptr: "::1 localhost"
local-data: "localhost AAAA ::1"
local-data: "localhost.localdomain AAAA ::1"
local-data-ptr: "192.168.2.2 OPNsense.localhost"
local-data: "OPNsense.localhost A 192.168.2.2"
local-data: "OPNsense A 192.168.2.2"
local-data-ptr: "192.168.100.2 OPNsense.localdomain"
local-data: "OPNsense.localdomain A 192.168.100.2"
local-data: "OPNsense A 192.168.100.2"
local-data-ptr: "192.168.0.5 OPNsense.localdomain"
local-data: "OPNsense.localdomain A 192.168.0.5"
local-data: "OPNsense A 192.168.0.5"
local-data-ptr: "192.168.5.1 OPNsense.localdomain"
local-data: "OPNsense.localdomain A 192.168.5.1"
local-data: "OPNsense A 192.168.5.1"
local-data-ptr: "192.168.64.1 OPNsense.streaming"
local-data: "OPNsense.streaming A 192.168.64.1"
local-data: "OPNsense A 192.168.64.1"
local-data-ptr: "172.16.254.1 OPNsense.colibri"
local-data: "OPNsense.colibri A 172.16.254.1"
local-data: "OPNsense A 172.16.254.1"
local-data-ptr: "192.168.2.5 nexus.localdomain"
local-data: "nexus.localdomain IN A 192.168.2.5"
local-data-ptr: "192.168.5.102 USG-WAN2.localdomain"
local-data: "USG-WAN2.localdomain IN A 192.168.5.102"


This is causing a major headache for me.