I’ve found that if it type se23.rocks into a browser without the www in-front, I can’t get on here.
Which is the exact error message on the browser, and which browser and platform?
thanks for pointing this out
I have to admit that I registered the domain with a particular hosting site and only later realised they did not support the ‘proper’ use of a ‘naked domain’ like se23.rocks
I have tried to get around this, and it works on many browsers but maybe not all. If you can share any details I can look into this further as I would dearly love to avoid having to force the www.
There’s no issues using SE23 Rocks without the www on my mobile using Chrome on EE. It doesn’t work for me on BT using Edge, Chrome or Firefox without the www on Windows 11.
There must be technical folk out there that can correct this if this is wrong, but here goes. Please go ahead and correct this if necessary.
Apparently Windows 11 uses a ‘strict’ approach to name resolution. The browser looks for the exact domain and where it points to.
It doesn’t find what it is looking for at se23.rocks alone.
Other platforms know this is a common thing so automatically look for www.se23.rocks instead and find the ip address needed to serve up the correct location. (where the site is hosted)
Hence se23.rocks works for most people who are apparently browsing from an operating system that does not use the strict approach to name resolution, which would seem to be the majority.
1 Like
Am not aware of any such issue with name resolution on Windows 11 like this. Am using Windows 11 right now and have never had to use www on this site (on any platform).
I think this is more likely to be a DNS or local cache issue. Try clearing the local browser cache to see if that resolves it?
in addition to the comments already made, it is less likely to be Windows 11 causing the issue, it is more likely the BT connection. They are also well known for issues with email filtering so I would assume they might also create ‘bespoke’ DNS issues.
Having said that, I’m on OpenReach and there are no problems with this here.
Not sure how it could work in some instances if so, but is this relevant?
2 Likes
Well something’s happened here. I can now type the domain without www and it now redirects to www.se23.rocks