2
b2plane
1y

Im trying to attach my ECS Fargate Load Balancer to route53 but the domain is dead.

LB dns name works perfectly fine. Its healthy. Backend is deployed and working fine through ecs fargate

But for some reason my domain doesnt work.

- attached the LB as an A record
- Alias to application and classic load balancer
- region correct
- chose a dualstack... Load balancer

Domain cant open

This site can't be reached
api.domain.com's DNS address could not be found. Diagnosing the problem.
DNS_PROBE_POSSIBLE

There are literally 0 fucking error logs in my ecs, task definition, load balancer target groups security groups vpc etcc.

What the fuck is the problem please how do i fix this?

Comments
  • 1
    the correct place to ask this would be StackOverflow
  • 0
    @SidTheITGuy i did. Also on aws forums. The guy on SO told me it fucking works for him! The domain opens for him just fine and the api works. But domain is dead for me and my phone and laptop and gfs phone and dads phone. Doesnt work but works for him. How the fuck??
  • 0
    @b2plane gonna need a domain to see if it's a local issue or a wider issue?

    Are all these devices connected to the same router? Or same ISP?
  • 0
    @b2plane Are the devices that are failing sharing the same network?

    Are you using something like NordVPN?

    Does it work if you connect to the internet at a public place like a coffee shop or library?

    It is possible your ISP is blocking the port you are using. Try changing the port and see if you can connect.
  • 0
    @C0D4 how can i check that?
  • 0
    @cuddlyogre you just have me a brilliant idea -- a fucking VPN. I turned my VPN now and immediately the domain works just fine along with the API. How the fuck????? Why

    No Why??

    It doesnt work:
    - on my computer
    - on my laptop
    - on my android phone
    - in my dads phone
    - on my gf's phone

    It works:
    - anywhere via VPN

    Ffs this means I've done everything correctly but my networkvis fucking up. How do i fix it for me locally? And it appears its not only for me but for my gf's phone too, how come if shes not even at the same wifi network as i am?
  • 0
    @b2plane Their DNS has not updated yet. It can take 24 hours sometimes.
  • 0
    Maybe a far stretch, but perhaps your country actively filters out several servers where you try to connect to? But yeah, sounds like your ISP is blocking it
  • 0
    @Bibbit ive added the ssl certificate so the load balancer serves on https now. All of this shit built through terraform.

    Right now my dad can open the load balancer api.domain.com on his android phone but i still cant open the same domain on my iphone. We're both on the same network on the same wifi. My gf who is not on the same network and wifi also doesnt work.

    Make this bullshit make any fucking sense???
  • 0
    @b2plane get the IP and have them open the IP. If that works then the DNS they are using has not updated its values yet. You can also test this by having them change their DNS to a google DNS: 8.8.8.8 or 8.8.4.4
  • 1
    dig @8.8.8.8 example.com +short

    That command will validate if the dns is propagating.

    dig example.com +short

    That command will validate that you have access to the DNS records.

    did you migrate your domain zone to route53, or change the NS records to Amazon's name servers at the domain provider?
Add Comment