Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

24.7.8 - ISC DHCPv4 does not register new leases in Unbound #8075

Open
2 tasks done
gyrex opened this issue Nov 21, 2024 · 9 comments
Open
2 tasks done

24.7.8 - ISC DHCPv4 does not register new leases in Unbound #8075

gyrex opened this issue Nov 21, 2024 · 9 comments
Labels
support Community support

Comments

@gyrex
Copy link

gyrex commented Nov 21, 2024

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Describe the bug

Note: This is a duplicate of Issue #7376 which was closed but it appears that there are other people who are experiencing this issue too. I opened a forum post on this issue here: https://forum.opnsense.org/index.php?topic=43814

New registered DHCP names are not registered inside the DNS (Unbound) even though so "Register ISC DHCP4 Leases" is enabled.

I think the issue is there since 24.1 but not 100%.
At least I can say it since 24.1.3.

To Reproduce

Steps to reproduce the behavior:

  1. Register new hostname through DHCP
  2. Request the IP via hostname from DNS -> no response
  3. Reload Unbound server
  4. Request the IP via hostname from DNS -> working

Expected behavior

Hostname should be registered automatically in the Unbound DNS.

Describe alternatives you considered

Restart of Unbound fixes the issue.

Screenshots

N/A

Relevant log files

Please let me know which logs are required

Additional context

Add any other context about the problem here.

Environment

OPNsense 24.7.8-amd64
Running under Proxmox 8.2.10

@fichtner fichtner added the support Community support label Nov 21, 2024
@fichtner
Copy link
Member

The most common issue here is the unbound DHCP watcher daemon being stopped most likely because of garbage host names given by strange devices in the network. You can check if the watcher is running...

# pgrep -F /var/run/unbound_dhcpd.pid

Cheers,
Franco

@gyrex
Copy link
Author

gyrex commented Nov 21, 2024

Thanks for your response Franco. I don't have an unbound_dhcp.pid process in that directory. I've got an unbound.pid and a unbound_logger.pid and unbound.pid is running.

What would you recommend in terms of logging to diagnose the issue?

@fichtner
Copy link
Member

Just to be sure are we talking about dynamic or static leases from ISC DHCP?

@gyrex
Copy link
Author

gyrex commented Nov 21, 2024

Dynamic

@fichtner
Copy link
Member

Ok, and Services: Unbound DNS: General: Register ISC DHCP4 Leases is enabled?

@gyrex
Copy link
Author

gyrex commented Nov 21, 2024

Sure is. Here's a screenshot of my settings.

1jMO6ie

@fichtner
Copy link
Member

OK, When you hit apply there should be a /var/run/unbound_dhcpd.pid ? If not we can try running it manually...

@gyrex
Copy link
Author

gyrex commented Nov 21, 2024

Sorry mate, I'm a little confused. It's always been selected so shouldn't that process be running already?

Edit: OK, so I pressed apply even though I didn't change anything and the process appears to be running. Is this the process which registers DHCP leases? Is there some way to find out why this process might be terminating?

@fichtner
Copy link
Member

Is there some way to find out why this process might be terminating?

That would be the next question. For now let's see when it stops and try to run it manually when it disappears:

# /usr/local/opnsense/scripts/dhcp/unbound_watcher.py --domain "YOURDOMAIN"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Community support
Development

No branches or pull requests

2 participants