We run Exchange 2007 at our company. One Exchange Oganization, with each division having at least a Hub/CA Exchange server at thier site. Our site is the primary location with MX records pointing to the A records that resolves to our mail gateway here. At the remote sites, they each route outbound mail through their Exchange server, but internal and received mail is all routed internally through our location here at the hub site.
We are moving to a MPLS WAN from our current VPN / multi IPS based WAN. We have had to work with each ISP to register PTR records to allow for reverse lookup's from those recipients who require this PTR record to be something other than blank or the generic arpa response.
With this migration we also acquired several large blocks of public IP's. We have our new provider advertising these IP's for us. However they say that they cannot create the pointer records because they do not own the IP's. They just advertise them for us.
Here is the question.. because we own the IP's but our MPLS provider advertises them, does this mean we need to set up a public DNS server and create our own PRT records? Or do they STILL NEED to be set up on the ISP's end ???
OR is there any way to do this with Exchange? How does a reverse lookup determine what FQDN is associated to that IP? Does it get this by looking up who owns the IP or by who advertises the IP?