Actions
Feature #8493
open
IP address auto-suggest checks for existing DNS records
Status:
New
Priority:
Normal
Assignee:
-
Category:
DNS
Target version:
-
Description
My production foreman instance does not control DNS but it does manage DHCP for most subnets via ISC DHCP. DNS A and PTR records are always created before the host is added to foreman. It would be a convience if the primary interface/bmc interface performed configuration tab performed any of these lookups:
- attempt to resolve the fqdn and if an A/AAAA/CNAME record exists, suggest that IP address; perhaps this behavior could be dependent on whether or not the selected subnet has DNS management; alternatively, the subnet could be auto selected based on fqdn resolution as soon as the domain is selected
- attempt to resolve the IP address (user entered or auto suggested) and display a warning next to the address text box if an existing PTR record conflicts with the fqdn.
- (not a DNS lookup but related) check that the IP address is in the range of the selected subnet and display a warning next to the address text box or subnet drop down if it is not.
Updated by Joshua Hoblitt over 9 years ago
- Related to Feature #8346: Implement fqdn resolution for DHCP added
Updated by Joshua Hoblitt over 9 years ago
I believe that #8346 is requesting the ability to not set an IP address via foreman at all and that only the fqdn would be configured in the DHCP server (relying on external DNS to resolve the IP address). The feature described in this ticket involves convience/sanity lookups while configuring a hosts networking but modify how the proxy creates a DHCP reservation.
Actions