Allow creation of DNS record when adding a client #1764

Open
opened 2026-03-04 01:31:35 -05:00 by deekerman · 4 comments
Owner

Originally created by @timcappalli on GitHub (Jul 18, 2020).

Problem Description

When not using AGH as the DHCP server, if you want your hosts to display in the UI instead of an IP, you have to manually define client name to IP mappings. Now if you want to be able to also resolve those clients across the network, you now have to go over and create a rewrite rule entry.

Proposed Solution

I'm proposing that tab area of the Client settings be extended to include a new section that allows creation of a DNS record.

image

  • checkbox to enable
  • a new field for the FQDN (since the client name may be just the host for readability).

The result would be a new DNS rewrite rule that is created and kept in sync with any changes made to the client entry. The API should also be extended to support these new config options.

Alternatives Considered

The alternative is to manually create both and risk them being "out of sync" after changes.

Additional Information

Originally created by @timcappalli on GitHub (Jul 18, 2020). <!-- As an open-source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can. --> ### Problem Description When not using AGH as the DHCP server, if you want your hosts to display in the UI instead of an IP, you have to manually define client name to IP mappings. Now if you want to be able to also resolve those clients across the network, you now have to go over and create a rewrite rule entry. ### Proposed Solution I'm proposing that tab area of the Client settings be extended to include a new section that allows creation of a DNS record. ![image](https://user-images.githubusercontent.com/6476604/87862337-e109bb00-c91c-11ea-92ce-c478ad986274.png) * checkbox to enable * a new field for the FQDN (since the client name may be just the host for readability). The result would be a new DNS rewrite rule that is created and kept in sync with any changes made to the client entry. The API should also be extended to support these new config options. ### Alternatives Considered The alternative is to manually create both and risk them being "out of sync" after changes. ### Additional Information
Author
Owner

@iceman73 commented on GitHub (Jul 20, 2020):

Would be nice as well if DNSMASQ could share the lease information with Adguard home to ensure easy automated entry here.

@iceman73 commented on GitHub (Jul 20, 2020): Would be nice as well if DNSMASQ could share the lease information with Adguard home to ensure easy automated entry here.
Author
Owner

@timcappalli commented on GitHub (Jul 20, 2020):

Would be nice as well if DNSMASQ could share the lease information with Adguard home to ensure easy automated entry here.

Please create a separate request for that.

@timcappalli commented on GitHub (Jul 20, 2020): > Would be nice as well if DNSMASQ could share the lease information with Adguard home to ensure easy automated entry here. Please create a separate request for that.
Author
Owner

@Aikatsui commented on GitHub (Aug 1, 2020):

Mentioned in #997 (for add to client settings)

@Aikatsui commented on GitHub (Aug 1, 2020): Mentioned in #997 (for add to client settings)
Author
Owner

@mdehaas commented on GitHub (Nov 9, 2020):

Would this include the ability to configure a domain suffix which is appended to all leases? If so this has my vote!

@mdehaas commented on GitHub (Nov 9, 2020): Would this include the ability to configure a domain suffix which is appended to all leases? If so this has my vote!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/AdGuardHome#1764
No description provided.