Route53 weighted policy not working with cloud-front distributions.

Amazon Route 53 weighted routing lets you associate multiple resources with a single domain name (example.com) or subdomain name (acme.example.com) and choose how much traffic is routed to each resource. This can be useful for a variety of purposes, including load balancing and testing new versions of a website or web application.

In your case, you have two CloudFront distributions (A and B) and you've set up weighted routing in Route 53 with weights of 255 for B and 0 for A. This should, in theory, direct all traffic to B and none to A.

However, you're seeing content from A instead of B. Here are a few things you could check:

• Propagation Time: DNS changes can take some time to propagate. It can take up to 72 hours for DNS changes to propagate worldwide, although it usually happens much faster. If you've recently made the changes, you might just need to wait a bit longer.

• DNS Cache: Your local system or network might be caching the old DNS records. You can try clearing your DNS cache or using a different device/network to see if the issue persists.

• Record Settings: Double-check your Route 53 record settings to make sure they're correct. Make sure you've associated the correct CloudFront distribution with each record and that the weights are set as intended.

• Health Checks: If you're using health checks in Route 53, make sure that both of your CloudFront distributions are passing their health checks. If a resource fails a health check, Route 53 will not route traffic to it, regardless of the weights you've set.

• Browser Cache: Your browser might be caching the old version of the site. Try clearing your browser cache or using a different browser to see if the issue persists.