Streaming live at 10am (PST)

DNS issues with AWS

Hi guys,

I just want to try and eliminate any issues on my side (Webflow) before asking the client to call their DNS provider!

I’m having an “issue detected” on the A records for our root domain, this is causing a dead end and not redirecting to the default sub domain (www). The sub domain is working fine and randomly the root domain is redirecting on Safari even though we still have an “issue detected”.

We have followed all the advice and videos and just cant seem to get to the bottom of it!!

It’s been about 24hrs could this still fix itself over time?
Is there anything else I may have missed on the Webflow side of things?
Or, is this definitely a DNS host problem not pointing correctly?

Thanks in advance!

Jono

I used dig and found no A records on your primary DNS.

; <<>> DiG 9.10.6 <<>> agileanalog.com@ns-139.awsdns-17.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 33549
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;agileanalog.com\@ns-139.awsdns-17.com. IN A

;; AUTHORITY SECTION:
awsdns-17.com.		900	IN	SOA	g-ns-18.awsdns-17.com. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400

Ok that’s great thank you helping Jeff!!

So it’s definitely a DNS host issue! Is it possible… that if they didn’t delete the old A records first, but added the new A records then deleted the old A records it may have caused a problem?

They deleted both the A records and AAAA records…

Thanks again,
Jono

@webdev

Once a save is complete, the changes should be immediately visible on the primary DNS for that zone; which can be checked with the Unix dig command. Contact your DNS administrator for assistance.

Thank you @webdev Jeff!