Hotsammysliz
Members
-
Joined
-
Last visited
Solutions
-
Hotsammysliz's post in Cannot reach SWAG subdomains on new domain name with dns cert was marked as the answerSo I spoke with some friends about this for help and there were two things happening at once here.
first thing was that my dns records were having an issue. On my old domain host of Hover the dns records were setup as such and were working:
TYPE
HOST
VALUE
A
arecord.domain.old
PUBLIC.IP.IS.HERE
CNAME
cname.domain.old
arecord
So with that I set them up the same on my new domain host over at porkbun but like stated in my original post arecord.domain.new worked but cname.domain.new did not work. I learned that Hover was basically using shorthand in the DNS records CNAME value so although I entered 'arecord' and that worked what it was actually doing was using 'arecord.domain.old' as the value. After learning this I updated my DNS records on Porkbun accordingly and everything began working again. Just for more detail this is what they look like on Porkbun
TYPE
HOST
VALUE
A
arecord.domain.new
PUBLIC.IP.IS.HERE
CNAME
cname.domain.new
arecord.domain.new
As for the issue with port 80 I did indeed confirm with my ISP that port 80 is now blocked which explained why I could no longer use http validation and had to switch to dns.
It was essentially a very simple fix but I hope this can help someone who may end up in a similar situation as mine!