3

I guess you are referring to this shopify DNS setup. Point the A record to the Shopify IP address 23.227.38.65. Point the CNAME record with the name www to shops.myshopify.com root domain (@) Well as you are aware, you cannot have a CNAME on the root (@) domain, so root domain needs to be handled with a A and AAAA records pointing at fixed IP addresses. ...


3

After testing, cloud-init is the root cause. According to this comment, disable_network_activation: true should be set to avoid conflict with the google-guest-agent service. The solution is adding the setting in cloud-init config. cat > /etc/cloud/cloud.cfg.d/99-disable-network-activation.cfg <<EOF # Disable network activation to prevent \`cloud-...


2

No, DNS is not the only way to switch between load balancers. Consider this multi-tier load balancer design. Scalable and resilient. Layer 7 tier has many instances that provide application aware proxy to backends. Terminates TCP connection, and possibly TLS. HAProxy, for example. Layer 4 tier in front of that, which routes packets consistently. keepalived ...


2

My understanding is that DNS was designed for name resolution, not load balancing. For both, because (almost) all records can be sets, hence for a given question a client can get multiple answers and then is free to choose whatever item it prefers. Which is why a frequent pattern is round-robin among replies, so that the client picks the "first" ...


2

You will have downtime. You can follow these tips to minimize downtime. With proper planning the downtime will be very short and in some cases automatic retries will make this invisible to clients. However, I do not know the design of your site, the usage of cookies, authentication, session management, etc. There might be disruptions that are unavoidable. If ...


1

In addition to the previous suggestions keep in mind that Google-managed SSL certificates aren't supported for regional external HTTP(S) load balancers and internal HTTP(S) load balancers. For these load balancers you will need to use self-managed SSL certificates. I have not seen what type of load balancer you are using, however before trying to set this ...


1

I hope you have set the service type as loadbalancer. Additionally please check the following link. https://github.com/openfaas/faas-netes/tree/master/chart/openfaas#endpoint-load-balancing


1

The most basic solution in DNS is indeed simply setting multiple records of the same type with different values and having your name server return all of them to clients when they request that resource record. The effect of that is usually called round robin DNS and although it comes with several drawbacks, it is well supported by DNS servers and clients ...


1

Well, recently I also did the test... just like @alberto-mendoza: upstream a { least_conn; server main_server:8080 max_fails=2 fail_timeout=5; server backup1:8080 backup max_fails=1 fail_timeout=30; server backup2:8080 backup max_fails=1 fail_timeout=60; } And nginx did the right load balance betwen the backup servers when the main goes down ...


1

If you are using metalb, I think you don't need to have an external vm with haproxy, you could install an ingress controller in kubernetes and change the service type of the ingress controller to LoadBalancer. Now You will have an external ip in your lan to access your local service through the ingress controller ip. (Internet) -> (Router) -> Nat -> ...


1

The answer that @mattpr gave is really detailed, and very thoughtful. It has a lot of useful information that is very accurate. I don't want to take away from that answer, and how amazing it is. My approach would be much more simplistic. I would setup a proxy host in [insert cloud vendor of choice], and use something like nginx proxy manager (https://...


Only top voted, non community-wiki answers of a minimum length are eligible