Hi, it's our existing feature request. We typically use additional polling engines because of increase of polling capacity/performance. In case of IPAM we don't have to solve this problem on polling engine side but on database engine. However, in a case you have an environment where you have NPN/SAM and additional polling engines and use a node as a DHCP/DNS server, then it's unfortunately not supported because of IPAM is not compatible.
My guess is that you would be OK if IPAM itself would not have additional polling engine but in a case you are using those from NPM and SAM it should accept DHCP/DNS node maintained by remote pollers.
thanks,
Michal