Corrupted network stack

I needed to change the DNS server of my HA instance so, after googling, went to the console and issued a

network update enp0s3 --ipv4-nameserver <new address>

The setting didn’t stick, so I assumed it needed a reboot. The IP stack never came back after the reboot. After much messing about, I recovered it by changing it to a dynamic address, and was able to access the GUI. When trying to set it back to static, I get the following message in the logs:

21-06-25 23:23:58 ERROR (MainThread) [supervisor.host.network] Can't update config on enp0s3: Error parsing parameter 1 of type “a{sa{sv}}”: expected value:
              'dns': <[uint32 ]>,

The same error is issued when I try to configure any manual settings on the interface.

Which I assume means there’s an underlying corruption somewhere.

Does anyone know how to resolve this? I’m happy to roll up the sleeves with CLI, or manually mounting the filesystem to change config files.

TIA.

Probably best to roll back to the snapshot you made before messing with the DNS settings.

You can manage DNS settings from the GUI now:

1 Like

Ahh! Great news – I didn’t know it was possible to do that in the GUI.

Thanks for the advice.

I can’t think why you would not use the router as the DNS since it is the default.

Really? I can think of many but lets start with two

  1. To use pihole or similar
  2. To get local dns resolution (which many routers don’t do)

I musr be too used to my OPNsense bc it does everything. :joy:

@nickrout covered some good examples.

In my case, I need local split-horizon DNS, I use DNS-over-TLS, and I require flexibility I simply can’t get out of my router.

I imagine opnsense would do those things too.

But you can’t compare opnsense to a consumer grade router