Bluecat IPAM: Proteus: Dynamische Records – was ist es?

Nach dem Import von einer Zone aus einem externem BIND Server erscheinen etliche Records als Dynamic.

Proteus (Network Manager) markiert alle solchen als Dynamic, wenn es für diese Records kein angelegtes Netz gibt. Für das IPAM sind sie quasi „fremd“:

I have tested this in the lab and was able to replicate this scenario. The reason why the imported Host Record shows as a dynamic record was because the network of the IP address assigned to the record was not defined in Proteus. Meaning, it was dynamically created as a generic record in Proteus (see snippets attached taken during my test for your reference). To make sure that the record will not show as a dynamic record, please make sure to define the network.