My VPS host had a problem. Luckily, I had backups.
I’ve successfully restored my backups, and am able to log into my MAIB GUI and see all my precious data.
The PTR has been set and can be found with a lookup. I’ve changed my nameservers with my registrar. For some reason, even after days, I am unable to get the nameservers to fully propagate to my server.
I’ve re-ran the installation command again as well. Restarted. I just don’t know what to do.
I just don’t know what else to do to find a reason why this is occuring.
I have created the glue records at namecheap and even was confirmed in writing by Namecheap support that Glue records are indeed correct. They are saying that the A records need to be setup by hosting (in this case MAIB).
MAIB is saying the glue records aren’t correct. This is the situation where all the providers are pointing the blame at each other. I’ve attached a screenshot.
There is a tool called Gwhois that performs lookups on every request, meaning that the site does not cache anything. It is reporting that there is no response from the DNS server failed to resolve.
My provider is NextArray. This is a new Openstack VPS. They moved from OpenVZ, which is where this issue first arose. I had a glorious box with a clean IP address. I was able to get my emails in all my client’s inboxes.
Could there be an issue with their platform? And what should I go to them with to help remediate?
I’m just flabbergasted. I’ve never had this problem when using Digital Ocean or the original OpenVZ VPS.
In the meantime, Namecheap has responded:
Thank you for getting back to us.
Let us clarify that the private nameservers ns1.box.aaronweiss.me and ns2.box.aaronweiss.me have been successfully created and pointed to the 192.109.165.180 IP address.
Also, there is another tool that you can use to check whether the glue records for the private nameservers are registered.
Feel free to use the following link: http://registrar.verisign-grs.com/webwhois-ui/index.jsp -> then go to the Nameservers tab -> enter your nameserver.
Here are the screenshots with the result for
ns1.box.aaronweiss.me - https://img.namecheap.com/xfQfFguaoNwSC8zex4NqXm.png
ns2.box.aaronweiss.me - https://img.namecheap.com/fVK6f85PYcv6x85FeTA41C.png
And here is an example how unregistered nameservers look like in this tool: https://img.namecheap.com/rKgB2AvCaTfHeyHdbMyY6L.png
In other words, nameservers are registered.
Also, there is another public dig tool that you can use to check whether the domain resolves to the needed nameservers and whether the corresponding A records are created on the hosting end. Here is a link to it: https://ip.iiidefix.net/dig?hostnames=aaronweiss.me&type=&ns=resolver&resolver=8.8.8.8&nameservers=&colorize=on&trace=on&ip=
According to this tool, the nameservers are created and the domain resolves to them, however, there are no A records for these nameservers created on the hosting end. Here is the screenshot where this information is marked: https://img.namecheap.com/iBjxT8978nGewRKQWVC42Q.png
Unfortunately, we can't assist you with this issue in any way since we don't have access to the DNS or Zone Management menu of your hosting control panel.
Feel free to provide this information to your hosting provider support and they will be able to investigate the issue further.
Request to be elevated to the next level of support, because that support agent has not demonstrated anything related to the glue record (“personal DNS record”). What is probably the case is the computer system of Namecheap says the glue record is configured, but the computer system of ICANN says the glue record is not configured.
$ whois ns1.box.example.com | grep "NOT FOUND\|IP"
NOT FOUND
$ whois edns1.registrar-servers.com. | grep "NOT FOUND\|IP"
IP Address: 2001:41D0:800:2D2C:0:0:0:2
IP Address: 51.89.217.44
In their own response they have demonstrated that they failed to register the IP address of the glue record, because those screen shots show a) the hostname of the nameserver is registered and b) the nameserver is not responding.
Tell them to use the IP address of your server to perform the dig tests and they will see all of the records responding correctly.
Also tell them if this is not resolved within 48 hours you will be reporting them to ICANN and include the following link:
I’ve had too much downtime, and I just couldn’t wait much longer. I waited 4 days for the nameservers to propagate, nothing. I chose to point the domain to nameservers, which I know are working, to a cpanel instance where I’ll host my email instead.
Except, similarly, these nameservers aren’t propagating fully either. It seems like the nameservers aren’t being recognized in the US. So I’m really starting to think it really is a Namecheap issue. And I’m afraid they will now say that cpanel too doesn’t have an A record set. But I can’t add a domain to cpanel until it seems the nameservers are correct. Catch 22 baby.
I’m going to follow up with Namecheap, again, to explain that now, a different set of nameservers, which work, aren’t fully propagating.
No need to troubleshoot further until I hear back from Namecheap.
I’m so appreciative of your instance that you and the MAIB community can resolve this, and I’m certain that you can. I just need to got back to, even temporarily, what I know works.
So much of my personal brand has been down for nearly a week and I just can’t stomach it any more. I’ve really been F’ed over by the hosting company which is how this mess started, and now I’m just not getting answers from the registrar.
