Lync 2013 reserve proxy DNS load balance

If we plan to do DNS load balance for reserve proxy .

does it same with edge DNS load balance implement or does it need hardware load balance to do?

https://technet.microsoft.com/en-us/library/gg398823%28v=ocs.15%29.aspx?f=255&MSPPError=-2147217396

Thanks.

August 21st, 2015 1:58pm

The reverse proxy is for web services, which should not be DNS load balanced because of the way the HTTP(S) protocol is designed.  You need to implement a hardware load balancer for this role.
Free Windows Admin Tool Kit Click here and download it now
August 21st, 2015 5:51pm

Thanks

edge pool need using Public IP to do HA can't using NAT. reserve proxy using NAT to do is ok right?

August 22nd, 2015 4:10am

Hi

RP using NAT is fine. Also Edge you can NAT you just need to include the public IP of the av service in the topology

thanks

Free Windows Admin Tool Kit Click here and download it now
August 22nd, 2015 9:19am

Agree with Mark. When you say edge HA, if you're using HLB on the edge then you don't want to nat, if you're load balancing with DNS which is my recommendation, then you can nat.
August 22nd, 2015 12:19pm

Yes, we are planing to do Edge DNS load balance with NAT, but we prefer hardware load balance before and it need more public IPs to do hardware load balance.

How about Edge server DNS load balance performance?

Thanks

Free Windows Admin Tool Kit Click here and download it now
August 22nd, 2015 12:27pm

DNS LB performance is fine and the configuration is a bit simpler so I prefer it.
August 22nd, 2015 3:01pm

You can deploy DNS load balancing on Edge Server pools. If you do, you must be aware of some considerations.

Using DNS load balancing on your Edge Servers causes a loss of failover ability in the following scenarios:

  1. Federation with organizations that are running versions of Office Communications Server released prior to Lync Server 2010.
  2. Instant message exchange with users of public instant messaging (IM) services AOLand Yahoo!, in addition to XMPP-based providers and servers, such as Google Talk.

These scenarios will work as long as all Edge Servers in the pool are up and running, but if one Edge Server is unavailable, any requests for these scenarios that are sent to it will fail, instead of routing to another Edge Server.

If you are using Exchange UM, you must use a minimum of Exchange 2013 to get support for Lync Server DNS load balancing on Edge. If you use an earlier version of Exchange, your remote users will not have failover capabilities for these Exchange UM scenarios:

Playing their Enterprise Voice voice mail on their phone

Transferring calls from an Exchange UM Auto Attendant

All other Exchange UM scenarios will work properly.

The internal Edge interface and external Edge interface must use the same type of load balancing. You cannot use DNS load balancing on one Edge interface and hardware load balancing on the other Edge interface.

More details:

https://technet.microsoft.com/en-us/library/Gg398634(v=OCS.15).aspx

Best Regards,

Eason Huang 

Free Windows Admin Tool Kit Click here and download it now
August 24th, 2015 3:20am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics