1

How can I add wildcards in DNS like www2.*.domain.com and www1.*.domain.com?

view story
linux-howto

http://serverfault.com – I have two servers which are load balanced. When I do the deployment I want to make sure the production users are not affected. Here is what I'm planning: Remove the webservers 2 (www2) from the load balancer. Deploy to the www2. do some quick testing (just over 100 mini sites all under one domain) Bring www2 back in to the load balancer then repeat for www1 Is there any way I can avoid manually adding the DNS entries for all my sub domains? Or, does anyone have a better idea of approaching this problem? (HowTos)

u85500's picture
Submitted by u85500 on 10/01/2012

Stories similar to How can I add wildcards in DNS like www2.*.domain.com and www1.*.domain.com?

could you please advice how to apply SSL certs on web servers behind a load balance server. Do we need to apply SSL certs on all the web servers or apply it to the load balancer only.

scenario: if we have three web servers say www1, www2, www3 behind a load balance server.do we need to apply SSL certs on www1, www2 and www3??

I have transfered my DNS to Route 53 and currently use an alias record to point my www.domain.com and domain.com to my Elastic Load Balancer.

Both work great but my problem is when I try to use an htaccess file to redirect non-www to www. It just fails DNS lookup and errors out when I visit domain.com and get re-routed to www.domain.com, going straight to www.domain.com works still.

When ever I try to load test a site that is load balanced on EC2 I get the following message:

ab -n 20 -c 20 http://www.somesite.com/

Benchmarking www.somesite.com (be patient)...Send request failed! apr_socket_recv: Connection reset by peer (54)

Any sites that are hosted on EC2 without the load balancer can be load tested successfully, so I figure it's not related to the security group I have

We're building a load balanced setup with two load balancers (that also terminate SSL) and several upstream servers. Both the load balancers and the upstream servers run nginx. The network on which requests are forwarded to the upstream servers cannot be trusted, hence we have to re-encrypt it after SSL termination on the load balancer.

there is a blog hosted on one machine (apache) (currently at blog.domain.com) and we'd like to move it to domain.com/blog. dns for domain.com is pointed at an haproxy machine load balancing a few nginx app servers. the machine hosting the blog is not behind that load balancer.

I have heard people say "oh that server is off the load balancer so you can run that expensive script on it".

What implications does a server off the load balancer have? Fundamental to answering this, I understand load balancing, but I don't know what the dynamics of a system with 5 servers (4 on the load balancer) has.

Thanks

If I set up a load balancer on aws that terminates ssl at the load balancer, then the requests being sent to the application server is in plain text. That has definite security implications. How do folks mitigate this implication in practice?

If alternatively, I set up https traffic between load balancer and the application servers also, what are the performance implications?

I have a service where servers upload 20kb xml files to my server.

There is no session, it is a single POST request and that's it.

I am configuring elysia_cron on a Rackspace Managed Cloud Server. We have a loadbalancer in front of two webservers. Am I supposed to use all three (3) IP addresses (Load Balancer, Web01, Web02) in the "Allowed Hosts" field? or just use the IP address of the Load Balancer?