Find Out What Previous Nameserver Were - ip

Recently we've had a domain that we've been hosting & we've had an issue where the domains nameservers were changed without us knowing.
Is there a way to find out when the nameservers were changed?
FYI, I've already done many ping tests to try & find out if the previous nameservers still show & it doesn't.

These are pretty cool stuff.
http://whoisrequest.org/history/
http://dnscheck.iis.se/

Related

No access to wordpress backend anymore - "Your connection is not private"

hope you can help me because I'm losing my mind here:
A couple of months ago, I started to build my new website (WordPress, hosted on Google Cloud, deployed with "Click to deploy" and I got the domain name on Google Domains).
Everything worked fine back then. But I needed to put this project on hold.
Now I wanted to continue working on the website, and I realized the VM was stopped. I successfully re-started it and wanted to access the WP back end with the link that can be found in the Deployment Manager of Google Clouds ([IP address]/wp-admin) but it doesn't work anymore. It only says the connection is not private, and I can't access the website. I can't even get to the login form.
What I have tried so far:
Changed ephemeral IP to static external IP & connected the VM to the IP
Pointed Domain toward static external IP - as shown in any tutorial
Updated NS on Google Domains
Created DNS Zones (A, CNAME)
Installed SSL for my domain successfull
Still not working, neither the IP nor the domain (server not found).
My guess - the Domain (mk-studios.net) is not live yet, and therefore, the SSL certification doesn't work yet. If not, I messed something up, and I don't know where to look. I don't get why it worked well months ago and has stopped working now.
Does anyone have a guess? Do you need any further details?
Thank you so much in advance,
Best,
Mario
This problem may have many causes but the most common is that your SSL has NOT installed properly. I suggest you the following steps:
Make sure that your SSL works fine and reinstall your SSL.
If you have access to DB, go to *_options table and in the first two rows siteurl && home you will find your URL. In this point remove the "S" from the https:// and make it http://.
If you have other server take the DB locally an connect with WP files from fresh installation.
Also when you remove the -s from https:// visit your url with incognito mode/private mode.
I will stay here to help you.
George

Difficult situation with domain under VestaCP

Let's say I have domain sxz.me.
Hostname is sxz.me, server is up and running. Unfortunately when I was typing in address sxz.me, it automatically redirected me to IP address 141.xxx.xx.xxx.
My point was to make it as domain name, not IP address. So I changed something in VestaCP that didn't work.
As a next idea, I have installed a plugin, which was redirecting IP address into sxz.me .. It worked! It started redirecting 141.xxx.xx.xxx into sxz.me. The problem was that sxz.me still didn't work e.g. didn't read files uploaded through ftp.
Then I've got genius idea of resetting the server from hosting support. I did it and then for whatever reason WordPress admin panel from 141.xxx.xx.xxx stopped working. I couldn't access it.
I've changed everything in VestaCP in the way described in this video.
Before it was also changed similar, but some parts were missing. We were waiting for DNS propagation and unexpectedly sxz.me started working! Almost there, but problem was that I still couldn't copy files from 141.xxx.xx.xxx by plugin, because of no access to WP admin.
I know there are also different ways, but that was my first idea. In the meantime I've started installing WordPress according to config.php from zero on 141.xxx.xx.xxx and website gone again! It just crashed somehow and started redirecting me once again to 141.xxx.xx.xxx so I'm completely confused and don't know what to do.
Domain doesn't work at all.

Subdomain install no longer working after domain switch

I have about five different subdomains on my host that are all working fine with wordpress installed.
I recently switched from Godaddy to Namecheap and bought a new domain name.
I changed the domain on my WHM Server which was all fine with my current sites.
The problem I have is when adding a new subdomain and installing Wordpress the site breaks because of DNS issues.
The Wordpress auto install is also weird as it doesn't detect the root like it used to, it puts the sub domain name into a folder above public_html.
So old subdomains are working fine but adding a new subdomain brings dns errors with wordpress installed.
Any ideas please, I've spent a solid five hours on this already.
Thanks.
If I'm following you correctly, you...
Created an account and bought a new domain on Namecheap
In Namecheap's WHM (Webhost Manager), you changed the domain to the one you had with GoDaddy.
When you create a new subdomain in Namecheap's WHM, it's not resolving the subdomain
So based on the above assumptions, it sounds like your domain is still with GoDaddy, and it's still pointing to GoDaddy's name servers. So if you add a new subdomain in Namecheap, it won't do anything, because Namecheap doesn't have control of the DNS. And for that matter, I think your subdomains would still be pointing to GoDaddy's servers.
Again, assuming I followed your description correctly, I'd recommend you migrate your old domain to Namecheap since, I'd assume, you're going to close your GoDaddy account at some point. If you need to urgently create a subdomain, you would need to do that on GoDaddy's end.
Hope this helps.
Fixed the problem myself, for anyone with a similar issue. I even went through Hostgator support who couldn't figure out the problem.
Logged into WHM > DNS Functions > Edit DNS Zone
The sub domain in question was not named correctly, it was named as the directory name instead of the full url.

Site not appearing with prefix www

I installed a wordpress site. The visitors can only see the site without the prefix WWW. If someone types the website name with www, there is a "site not installed page". I am with OVH hosting and they are blaming the wordpress but I am sure that someone without good knowledge answered as the problem was the same even before the wp installation took place. If I change wp url location in the backend to www.mysite.com there is a backend lockout till I edit the database directly with the url without www.
My questions:
1> How to make my website accessible with both versions of the url (www+no www)? I want the www to appear in the address bar.
2> I do not want SEO rank loss due to duplicate content.
Please help as the customer care sucks and for 2 weeks they cant solve this problem. I am sure someone out here can please provide a few steps which I can follow and implement what I want. Thanks a lot in advance.
You may want to check with your hosting provider. I think technically, they are different URLs. Your host should be able to link both I would imagine.

How to forward domain to meteor deployed website (using GoDaddy)?

This seems simple enough, but its not quite working.
I have a website deployed at website.meteor.com and it seems to work just fine.
I have a domain name, website.com with GoDaddy. There's some weird business with the www that I'm unclear about, but it seems I'm "forwarding" website.com to www.website.com. I had no idea there's a difference. Anyways, I think (hope) this is unrelated.
In my Domain, DNS Zone Files, I set the CNAME (alias) to point to website.meteor.com. This didn't work. I get that the meteor website is down. But when I go to website.meteor.com, it seems to be just fine.
I realized that www.website.meteor.com doenst work, so I suspect maybe thats the issue?
In my CNAME (alias), I realized that HOST is www so maybe thats the issue. I deleted that, but then I couldn't save with no host. It says the host is the "subdomain in which the record applies", whatever that means. So I tried putting website there, "Points to" meteor.com. Well that didn't work either.
Hopefully there something very minor I'm messing up here.
OK, I figured it out.
Host: "website"
CNAME: "origin.meteor.com"
Thats not enough though. I've already deployed to website.meteor.com but it doesn't show up.
You then have to mrt deploy www.website.com.

Resources