![\"\"](\"https:\/\/i0.wp.com\/www.bootedmanblog.com\/wp-content\/uploads\/2017\/05\/WebsiteMay2017blog-300x260.jpg?resize=300%2C260\")
As noted in my previous post, my website<\/a> was temporarily down when the registrar for the website’s domain decided that they had to have a sudden confirmation of ownership. The registrar sent an automated email to an account that I seldom check, and that email account captures auto-generated email as likely spam, so the email went to a spam folder. They sent an email to a back-up account — on the domain that they suspended, so I did not get that, either. What a way to run a railroad.<\/p>\nAnyway, after 48 hours and the website still not working, with some sleuthing, I fixed it myself by…
\n
\n…looking at where the domain was pointed to (called a nameserver) and discovering that the registrar inserted a blank space — literally one ___ darn little blank space in front of the nameserver designation — and that one little blank space made my website not visible to the internet. <\/p>\n
When I chatted with the registrar’s technical support guy (in a remote location with little technical instruction or support himself) upon discovery of my website not being visible, I was informed that they saw my ownership confirmation and they restored the nameserver information. He told me in his pre-scripted chat that I should be patient, because it could take 24 – 48 hours for the website to restore visibility via the Domain Name System. <\/p>\n
Well, he fixed it alright — by restoring my nameserver designation with a leading blank space. When he did that, the DNS couldn’t find my website because computer systems are very very literal. A nameserver that begins with a leading blank space is not the same as a nameserver that does not have a leading blank space.<\/p>\n
Oh fiddlesticks. If I did not have such close attention-to-detail, I never would have found it and my website would still not be working.<\/p>\n
But when I removed that one leading blank space from the primary nameserver name, within minutes, email started appearing and the website began to work.<\/p>\n
Goes to show that sometimes doing your own technical sleuthing is the best solution, rather than depending on a poorly trained tech based outside the U.S. (what I get for going cheap for a domain registrar).<\/p>\n
Life is short: when you own your own website and do your own coding, learn all you can about how it works because sometimes you have to fix things yourself.<\/p>\n","protected":false},"excerpt":{"rendered":"
[Updated\/correctly chastised\/tail behind legs] As noted in my previous post, my website was temporarily down when the registrar for the website’s domain decided that they had to have a sudden confirmation of ownership. The registrar sent an automated email to … Continue reading