# Multiple bind a.com:443 b.com:443 lines Yes/No?

**URL:** <https://discourse.haproxy.org/t/multiple-bind-a-com-443-b-com-443-lines-yes-no/4914>\
**Category:** Help!\
**Created:** [February 29, 2020, 1:35pm UTC](https://discourse.haproxy.org/t/multiple-bind-a-com-443-b-com-443-lines-yes-no/4914 "2020-02-29T13:35:59Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [March 3, 2020, 6:00pm UTC](https://discourse.haproxy.org/t/multiple-bind-a-com-443-b-com-443-lines-yes-no/4914/2 "2020-03-03T18:00:45Z")

</div>

No, you cannot use `ssl_fc_sni`, you need to use `req_ssl_sni` instead, and no, you don’t have to break your ssl terminating frontend to multiple ones.

Take a look at the following post for an example (which uses abns sockets but you can just replace them with loopback ports if you want):

> [@How to set ssl verify client for specific domain name](https://discourse.haproxy.org/t/how-to-set-ssl-verify-client-for-specific-domain-name/1489/3):
>
> There is no simple way to do this, unfortunately. Use a TCP frontend withouth SSL termination, SNI route to different backends that recirculate to traffic to dedicated SSL frontends with different configurations. Something like: frontend port443 bind :443 tcp-request inspect-delay 5s tcp-request content accept if { req\_ssl\_hello\_type 1 } use\_backend recir\_clientcertenabled if { req\_ssl\_sni -i test1.demo.com } default\_backend recir\_default backend recir\_clientcertenabled …

---

_[View the full topic](https://discourse.haproxy.org/t/multiple-bind-a-com-443-b-com-443-lines-yes-no/4914)._