You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My idea is that when DHCP hands out an address, in addition to the normal A Record for the hostname it will also register the MAC as an A Record. Optionally with the Manufacturer prefix.
This would be enabled per scope.
My use case is for devices that may change VLANs but might need to be accessed via a common FQDN. This way I could create a CNAME that points to the MAC A Record and it wouldn't matter what VLAN the "server" is on.
The text was updated successfully, but these errors were encountered:
Thanks for the request. Wont the MAC based A record entry be in the same zone as that of the current one, or do you want to have to configure another zone for it? Does using the same domain name for both the scopes work for you scenario?
There is a plan to have DHCP Scope restructured to allow customizing options based on client's MAC or Vendor Identifier so I think if such a design is available later, this config can be done with it without need to have MAC based DNS entry.
Here I go thinking faster than I can type lol
Yes, I was thinking of specifying a "global" zone to dump the A Records into such as mac.lan.
I would be curious to see what these changes might entail, is there an issue where you are discussing these changes that I can review?
Another thought is to have a non-compliant record type such as MNAME where instead of linking a hostname to a CNAME we could just put the MAC in there and internally it would query the DHCP leases.
I would like to request a feature.
My idea is that when DHCP hands out an address, in addition to the normal A Record for the hostname it will also register the MAC as an A Record. Optionally with the Manufacturer prefix.
This would be enabled per scope.
My use case is for devices that may change VLANs but might need to be accessed via a common FQDN. This way I could create a CNAME that points to the MAC A Record and it wouldn't matter what VLAN the "server" is on.
The text was updated successfully, but these errors were encountered: