Messages

Do you have 127.0.0.1 in the /etc/resolv.conf

It should work though.

Maybe you didnt select the correct interface in the filter dropdown to show the rules?

Maybe the rule appeared on a second page due to pagination?

There is this:

https://docs.opnsense.org/manual/how-tos/multiwan.html#failover-and-failback-states

Du könntest Dnsmasq als den zentralen forwarder nutzen. Alle Clients bekommen ihn via DHCP.

In dnsmasq gibt es die option "Add Subnet" in den advanced general options, damit wird beim forwarding die Client IP an die Anfrage mit angehängt.

Adguard sollte das eigendlich auswerten können.

Der Rest wäre dann in dnsmasq die richtigen forwarding Regeln zu setzen.

Lege eine virtuelle IP adresse auf dem WAN interface an. (IP alias)

https://docs.opnsense.org/manual/firewall_vip.html

Danach ein neues internes Netzwerk auf ein zweites interface.

Outbound NAT und Firewall Regeln so anpassen dass alles über die virtuelle IP läuft für das zweite Interface.

You could also try a reinstall with a later version and import the config backup afterwards.

That can be done offline.

You could take the chance and install with ZFS to use the new Snapshot feature.

Thanks for reporting and testing this :)

My mistake the patch is based on current master and not on the stable branch.

Try this one:

Code Select Expand

opnsense-patch https://github.com/opnsense/core/commit/1748dd18c3356099a570b008c707d65659e7241f

If you think there is a bug please open an issue on github and the steps how to reproduce it.

Thank you.

We all make mistakes.

Glad you got it resolved.

Its mostly because the domain gets a range assigned.

In a future update you will be able to set the domain to the interface of a range as well, e.g. thats needed for partial IPv6 dns registration.

https://github.com/opnsense/core/pull/8814

I dont understand. Are they not appearing in the dnsmasq host tab anymore, but the file they generated in var/etc/dnsmasq-hosts is still getting populated?

The Client has to get a lease issued before its name can be resolved.

A reservation just writes it statically into a separate file so the host can be resolved before DHCP. But it will still get registered the same way additionally.

Its a bit weird to explain it. Sorry if its unclear.

E.g. your DHCP domain is:

iot.internal
192.168.1.1-192.168.1.100

And your dhcp host reservation is

192.168.1.2
fe:fe:fe:fe:fe:fe

- A dynamic DNS entry is created as soon as the client gets a lease:

192.168.1.2 host.iot.internal

You leave both empty in the reservation and set the domain in the dhcp range. Each range can have its own domain.

As soon as the DHCP server gives out a lease, the DNS name will be registered.

You can leave hostname and domain empty in a reservation.

If a dhcp-range has a domain set, and the reservations IP address is inside the range, and the client offers its hostname, it will register as otgw.example.com as soon as it gets a lease.

I think we found it.

Can you try this from the SSH shell:

Code Select Expand

opnsense-patch https://github.com/opnsense/core/commit/b5e0b0b7dcb603d4464f1a3eb6a5491d79b70b0d