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

Bug: Registered DHCP leases in DNS have wrong domain name #624

Closed
8191 opened this issue Jan 8, 2016 · 2 comments
Closed

Bug: Registered DHCP leases in DNS have wrong domain name #624

8191 opened this issue Jan 8, 2016 · 2 comments
Assignees
Labels
bug Production bug
Milestone

Comments

@8191
Copy link
Member

8191 commented Jan 8, 2016

The feature "register DHCP leases in DNS" registers the DHCP leases with wrong domain name. The domain name of the OPNsense system is used instead of the configured domain name of the DHCP service.

@AdSchellevis
Copy link
Member

@8191 I don't think we can fix this without glueing too many components together, with our latest changes we collect and monitor all the leases, but I'm not sure how we should determine the dhcp pool they belong too easily. Any suggestions?

@AdSchellevis
Copy link
Member

timeout

fichtner added a commit that referenced this issue Nov 18, 2016
The amount of work required in the past two years for this
original pfSense 2.2 item has been immense.  Still deleteing
unused functionality like the cache, "reload" not being
implemented, DHCPv6 static registration missing in action.

While there, dedup the dnsmasq static DHCP registration.

PR: #1250
PR: #624
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Production bug
Development

No branches or pull requests

3 participants