Server cannot find address: NXDOMAIN error

[yyellapragada]

Hello Everyone!

I have a domain betora.vip on cloudflare. I made a CNAME record within this domain and pointed the record to an internet-facing load balancer situated in AWS. I’ve waited for the DNS to propagate and when I check the records via nslookup, I get the NXDOMAIN error as mentioned in the title of this post.

However, when I test an already existing CNAME record pointing to another loadbalancer, nslookup works.

Failing record: dev1-trade.betora.vip.

• Checked the DNS propagation on - www[dot]whatsmydns[dot]net/#CNAME/dev1-trade.betora.vip

Working record: newtrade.betora.vip

Can anyone please point me in the right direction in order for me to fix this problem?

[Laudian]

@yyellapragada

Failing record: dev1-trade.betora.vip

The record is not failing. It shows correctly as a CNAME to k8s-applicat-peatiope-ab33660e2f-2098681463.eu-central-1.elb.amazonaws.com.

dig dev1-trade.betora.vip +short
k8s-applicat-peatiope-ab33660e2f-2098681463.eu-central-1.elb.amazonaws.com

k8s-applicat-peatiope-ab33660e2f-2098681463.eu-central-1.elb.amazonaws.com however, is failing. You should check if this is the correct name supplied to you by amazon, because it is not resolving.

[yyellapragada]

Thank you for pointing that out. Your answer lead me to the root problem. The loadbalancer DNS was different. The DNS entry on cloudflare and the load balancer DNS was almost identical. The trailing part of the DNS was different.