Messages

We all make mistakes.

Glad you got it resolved.

...me then many :)

We all make mistakes.

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

very cool feature

anyway thanks for the help!

reading your answer I realized that the assigned IP was not in the dhcp range (since in other configurations I kept it outside the dhcp range) while in the opnsnese guide/manual it says "The reservation can also be outside the dynamic range, but it is not recommended for simple setups as the dynamic dns registration with dhcp-fqdn will not work correctly."

Modified accordingly (dhcp range include ip in host reservation) , everything works perfectly.
My mistake of superficiality.
Thanks for the support and attention!

already done, and it's not working as i intended.



I think that putting it in the range is still valid for leases that are assigned via dhcp and not via host reservation (what i'm triyng to achieve).

thanks for your quick reply.
However, what I would like to achieve is to leave only the device name blank, setting a domain with a nomenclature such as vlan.internal (in this case iot.internal).
I know it is complicating life, that there is a way to make the name resolution work, as you suggest.
However, mine is an exercise in style and I can't understand why it can't work in this way.
Perhaps I might lack the cultural basis to understand it.

I followed the guide on how to set dnsmasq correctly to resolve local addresses ( dns unbound -->> dnsmasq ).

However I encounter this problem:
if I set dhcp reservation, in dnsmasq, leaving the host field empty but filling in the domain field:




I can't resolve the addresses correctly, (nslookup 192.168.34.15) :


The name "OTGW" is obtained from the device.

if I set dhcp reservation, in dnsmasq, filling either the host field and the domain field:


in this case everything is as I expect


the name "otgw" is given by me.


what I would like to achieve is to give custom domain names to the various subnets (VLAN) leaving the hostname field free, so that the device can provide its own hostname, however, providing domain name but not explicitly stating the hostname, something doesn't work to me.

Everything works without giving custom domains and without giving device hostname (using only "internal") or filling in both custom domain and hostname;
Am I wrong in using these settings?
Could someone give me an hint.
Thanks for your attention

Hi, I also experienced this difference: virtualized OPNsense consumes about 6w, bare metal OPN consumes about 8w.
The hardware system to virtualize OPNsense or use it bare metal was the same fanless mini pc (i5-5200u, 8GB ram).
The greatest efficiency I currently found using powerD "Minimum", the frequency is almost always "fixed" at 500mhz and the temperatures at 39°C (vs 44°C with other settings, 55°C under load); however, this system decreases the system performance by halving the speeds (from 1000Mbps symmetric to about 500Mbps symmetric).

This CPU is very power efficient as it has Configurable TDP-down Base Frequency 600 MHz and Configurable TDP-down 7.5 W (from intel spec).

i have an i5-5200u CPU, this cpu has only speedstep tecnology available.
Without turning ON powerD, the cpu didn't scale its frequency.