Question 268583 in Amazon Web Sevices Question posted in
The official Amazon Web Services documentation can be found here.

Amazon web services – Discrepancy in Response Times Between Two Domains on AWS Route53 Pointing to the Same EC2 Instance

I have two domain names registered on AWS Route53, both are configured to point to the same IP address (i.e., they are associated with the same EC2 instance) and are located in the same AWS region. However, I am experiencing a significant difference in response times between the two domains.

Here are the domain names:

I have verified that the DNS resolution time is negligible and the server configurations are identical for both domains. There are no apparent blockages or misconfigurations on either domain that could explain this disparity in response times.

I would greatly appreciate any insights or suggestions to resolve this issue. It’s becoming quite frustrating. Thank you in advance for your assistance.

Tags:

2

Answers


  1. 0

    It runs perfectly fine for me (I am in Australia):

    % time nslookup laafisoft.bf
Server:     192.168.0.1
Address:    192.168.0.1#53

Non-authoritative answer:
Name:   laafisoft.bf
Address: 18.130.71.104

nslookup laafisoft.bf  0.00s user 0.01s system 2% cpu 0.323 total



% time nslookup laafisoft.org
Server:     192.168.0.1
Address:    192.168.0.1#53

Non-authoritative answer:
Name:   laafisoft.org
Address: 18.130.71.104

nslookup laafisoft.org  0.00s user 0.01s system 11% cpu 0.132 total

    You might want to try it by specifying a DNS server, such as Google:

    nslookup laafisoft.bf 8.8.8.8

    That way, you can determine whether the slowness is caused by your chain of DNS servers.

    Login or Signup to reply.
  2. 0

    Your problem is due to Google Analytics cookies.

    Both websites return quickly when used with curl, but the first site is slow when accessed a second time. Removing the _ga cookies makes it go fast again.

    Google Analytics was recently changed to GA4, so your site is probably using code that connects to the "old" Google Analytics and that is causing problems.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search