title: How to activate both public and private connection together for AWS Classic Load Balancer
body: <p>I have three network infras in my hand. Lets say they are A,B and C. There is a VPC Peering between A and B. C is a completely different network which has no mutual connection with A or B whatsoever. I have a internet-faced classic load balancer on network A with an application attached to it. Also, I have route 53 record for this load balancer which lets say example.com. I want to reach this application with this domain from both B and C networks. For network C, it's working with no problem because it's an outside network. But for B, it's a little bit complicated. I did the following steps to be able to reach it via VPC Peering but no success so far.</p>
  <ul>
  <li>I created an instance on network B.</li>
  <li>I add this instance's security group to Classic Load Balancer's security group. Hence there are VPC Peering, it should be working fine.</li>
  <li>I tried to reach the application via Route53 domain with curl,telnet and ping, it always gives the public IPs of the load balancer and I can not reach it.</li>
  <li>When I tried to reach application from this instance via load balancer's private ENI IPs, Its working fine, but as I said, no success via Route 53 record.</li>
  </ul>
  <p>I'm thinking that problem is probably related with the load balancer being internet-facing, but I'm also thinking that every ENI of the load balancer has one private and public IPs of it, So it should be possible that take response both for publicly and privately. I'm a little confused actually.</p>
  <p>Long story short, I have an internet-facing load balancer with a Route53 domain and I want to reach this via both public and vpc-peered private networks.</p>
  <p>Is it possible, am I doing sth wrong? Any help will be highly appreciated.</p>
  <p>Best Regards.</p>