Problem with DNS resolver

[Unoptanio]

@fireodo
So is it a bug in 2.7.2 that doesn't update unbound DNS?

[fireodo]

@Unoptanio said in Problem with DNS resolver:

So is it a bug in 2.7.2 that doesn't update unbound DNS?

No thats not a bug - if some changes where needed in unbound that occure AFTER release of 2.7.2 thats the only way to handle it - as far as I know!

PS.: Is unbound still restarting?

[Unoptanio]

@fireodo

during my lunch break in about two hours I will reboot the system

[fireodo]

@Unoptanio said in Problem with DNS resolver:

during my lunch break in about two hours I will reboot the system

[fireodo]

@darcey said in Problem with DNS resolver:

When might it pull in the updated package, other than explicit upgrade via the cmdline?

See my answer with the script inside - this kind of upgrade you have to do manually.

[darcey]

@fireodo Thanks, I'd completely forgotten about this. It seems on my system, unbound and curl have updates available.
Still I think I am going to leave it as is as things are running very smoothly for me of late.

[fireodo]

@darcey said in Problem with DNS resolver:

Still I think I am going to leave it as is as things are running very smoothly for me of late.

Never change a running system ... old wisdom
(curl has a security issue so I recommend to upgrade)

[Unoptanio]

@fireodo

After restart system

[Gertjan]

@Unoptanio

That's unbound in permanent restart mode !
You can stop that now, as the test succeeded.

To stop the testing :
Uncheck :

Save, and Apply.

( I'm trying a new solution to a 10+ year old question )

[fireodo]

@Unoptanio said in Problem with DNS resolver:

After restart system

Do you have the register dhcp-leases in dns resolver (as gertjan indicates) on?

[Unoptanio]

@Gertjan

Done now at 2.18pm

Now I try to disable DHCP Registration

[stephenw10]

Run pkg upgrade to check if there are any updated system packages available.

We build newer versions of packages if they are available with fixes for specific issues that users may be hitting. They are then available to upgrade to but these are not expected or required upgrades.

In the instance that upgrades are required for security issues we would usually either issues an announcement or a point release of pfSense depending on the severity.

I would not expect the Unbound version to be the issue here. But it also doesn't hurt to update it and it's an easy test.

Steve

[Unoptanio]

@stephenw10 said in Problem with DNS resolver:

pkg upgrade

[2.7.2-RELEASE][admin@xxxxx]/root: pkg upgrade
Updating pfSense-core repository catalogue...
Fetching meta.conf:   0%
Fetching packagesite.pkg:   0%
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
Fetching meta.conf:   0%
Fetching packagesite.pkg:   0%
pfSense repository is up to date.
All repositories are up to date.
Checking for upgrades (3 candidates): 100%      3 B   0.0kB/s    00:01
Processing candidates (3 candidates): 100%      3 B   0.0kB/s    00:01
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
        curl: 8.4.0 -> 8.6.0 [pfSense]

Number of packages to be upgraded: 1

1 MiB to be downloaded.

Proceed with this action? [y/N]:

[stephenw10]

Yup, you can upgrade curl. But not upgrading it should not be an issue.

[Unoptanio]

@stephenw10

disabled DHCP Registration

Rebooted the system and the problem recurred. unbound DNS Does not resolve

[stephenw10]

And it's still just continually restarting?

Is there anything in the main system log that's looping? Something else could be restarting Unbound.

[Unoptanio]

@stephenw10

I stopped the service and restarted it and it worked right away.

But in the service list it always showed it running green even when it's not working

[stephenw10]

And in the main system log?

[johnpoz]

@Unoptanio why/how can you have both unbound 1.18 and 1.19.1 on the same system both starting?

Did you upgrade pfsense? That is a pretty fast upgrade

LIke 1 minute?

[stephenw10]

Huh, nice catch! Well that seems suspicious!