- General Support
- Re: Can not get to my new e-voice site re problem with domain
- One Message
General Support: Re: Can not get to my new e-voice site re problem with domain
You ideally have an A record (not a redirect) for rbclub.uk and for www.rbclub.uk which goes to 184.108.40.206.
I can see that the one for www.rbclub.uk is in place, and is working fine.
HOWEVER, voice has been unable to create an https certificate for your site, becuase you also have an AAAA record pointing to somewhere else. So the site is only available on http, not https. (An AAAA record is like an A record, but uses an IPv6 address)
If you remove the AAAA records from www.rbclub.uk and rbclub.uk then voice will automatically install an https certificate for you.
Joe - Voice Admin
Hope you and family are all keeping well in these difficult times.
Many thanks for your above reply.
This has worked although for a while earlier this morning Microssoft Edge browser took to the correct page and showed the header/banner but contents underneath were shown as page not found. However this now looks okay.
But in MS Edge if I type just rbclub.uk in the address bar (no www,) then it has a problem and shows in addressar as "Not secure rbclub.uk/defaultsite and displays a page of links to advertised websites. Whereas in Google chrome on my PC just rbclub.uk works fine, but not in chrome on my mobile phone, the Silk browser on my Kindle Fire tablet and also in iPad bowser. These all work fine with full www.rbclub.uk address.
I do not understand what the difference is between www.rbclub.uk and just rbclub.uk and address bar. Could you kindly clarify for me?
This is because you correctly have an A record at www.rbclub.uk pointing to 220.127.116.11, but the A record at rbclub.uk (with no www) is pointing to a different address which is providing the web forwarding.
If you change the A record on the root domain to point to 18.104.22.168 instead of the web forwarding then it'll work properly.
Different DNS management systems represent the root domain differently. Sometimes they use an @ sign as the subdomain to indicate "no subdomain". So maybe look for that.
There are some instructions for some common registrars' DNS management pages here. Even if you're using a different system it may be similar!
Thanks Joe, for your help and information.
All seems to be working fine now.
You were spot on regarding the @ symbol for subdomain.