We have an Essentials 2016 set up with Exchange and Essentials on the same IP address. Now I have an extra address which will allow reverse dns for both if I give each it's address. I am looking to see if I understand what needs to be done to make that happen. And someone suggested it is a bad idea.
Kal
If you want to use two public IP addresses there is no need for two Nics in the Exchange server. The trick is to create two public hosts, like exchange.domain.com with pub IP address xxx.xxx.xxx.1 and essentials.domain.com with pub IP address xxx.xxx.xxx.2. You need a router that can handle this and forward traffic for 443 and 25 exchange.domain.com with xxx.xxx.xxx.2 to the internal IP address of your Exchange server.
Do the same for essentials.domain.com with xxx.xxx.xxx.2 and forward 443 to the internal IP address of the DC.
Thanks.
I have not tried to enter 2 public addresses into the router, did not even think of that idea. Is this a common router attribute?
The Exchange server has 2 NICs, but only one is active. I do not see an obvious difference between putting the second address into the exchange server or into the router and having it forwarded to the exchange server.
I consulted Google and apparently a Ubiquiti Edgerouter X SFP - Router - Desktop - Black (ER-X-SFP) can be configured to do what you recommend and it is only $80, so I may well do that. Or do you have a different recommendation?
I remain curious as to why it is better though?
That second public IP address does that run on the same internet connection as the other one? I am trying to understand why you want a second network adapter for that other public IP address.
Yes, there is only one ISP (Comcast) with one subnet.
I don't "want a second network adapter", it seemed like the way to accomplish my goal. You have pointed out another, possibly better, way to do that. Now I am trying to understand what makes one method better than the other?
I am also looking for information on possible routers that can handle 2 public ip addresses. Has anyone here used the Ubiquity products? They appear capable of handling the 2 addresses OK, mapping them looks a bit more complicated. I didn't look closely enough to know if getting a windows VPN to work through this router is easy?
Is there a better brand for this purpose that is still easily affordable?
But the first question is, is it really necessary to go through this learning curve, why not just go directly to the Exchange Server?
Loren,
Can we have a Skype call sometime tomorrow?
Sure, although the time difference may be an issue. I can probably be available by 11:00 Pacific Time, 11:30 is safer, then I am available till 2:00.
I can see a difference if the router is performing a firewall function, it will be interesting to hear your ideas.
Loren and I worked on his system years ago and I decided to do a Skype call. I did not fully understand what the issue was but after the Skype meeting, we got it fixed. It is going to be a router that can handle multiple public IP addresses.
Good talking to you after all these years :)