Replies: 4 comments 1 reply
-
use https://dnschecker.org/#A/apktool.org to check |
Beta Was this translation helpful? Give feedback.
-
Wonderful. Not sure why this happened. Domain still under my control. |
Beta Was this translation helpful? Give feedback.
-
Found some time - setup the A, AAAA and CNAME on www. Unfortunately I'll have to wait for dns propagation to move from Google to Linode. |
Beta Was this translation helpful? Give feedback.
-
Closing as resolved. Many mistakes were made. I transfered Google to Porkbun, unaware my NS records for this domain were on Google. Google killed serving those NS records and they all disappeared, which led to this issue. So I used Porkbun and setup the records using the new ALIAS record. Nothing was resolving after a full day of vacation so I figured that new type wasn't fully supported. I changed to the Github A records, but I couldn't use more than 1 A record. So decided to move NS records again, this time to Linode where I host other DNS. Once I checked the next day, I saw partial success, but mostly failure. I looked and saw it was DNSSEC validation failure. I had failed to disable DNSSEC prior to transfer so I thought I was screwed. Turns out I could just remove the DNSSEC record from Porkbun as Linode didn't support natively generating them. All was resolved shortly after. Lesson learned. Don't do migrations prior to vacation. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
All reactions