When changing the nameservers for a domain, will there ever be a time in which it points to neither the old nameservers nor the new nameservers? If so, why does this occur?
For a little context, the reason I ask is because I just did this, the A-record and nameservers are coming up correctly when I get the DNS info, I verified the site on the new server AND the old server was running by adding them to my local machine's hosts file, but I got a "site not found" error in Chrome for about an hour before it came up correctly. (meaning, SOMETHING changed, but why didn't it just change immediately to the new nameservers?)
Related
Problem:
I have svilab.com and www.svilab.com pointing to the managed DNS servers from Netlify.
I would like crm.netlify.com to point to a Godaddy IP address 160.153.33.96
Here is what I have done so far:
Migrated my DNS from Godaddy to Netlify by changing the nameservers to
dns1.p06.nsone.net
dns2.p06.nsone.net
dns3.p06.nsone.net
dns4.p06.nsone.net
Created an A record that goes to crm.svilab.com -> 160.153.33.96 which is a godaddy server.
What I am expecting is to see:
A login page for the suitecrm I setup.
What I am actually seeing is:
Future home of something quite cool. I have verified that the home.html for this default page does not exist in the public_html on godaddy.
I setup the A record correctly. See my dropbox link
The problem was on netlify's side. From their email...
You made the record correctly. There is a known bug (cross-linked to this conversation for tracking) were sometimes, very rarely but sometimes, the DNS record gets created in our UI but not in the actual DNS server.
So, our UI says there is a record, when in reality there isn't one.
To clarify, you did everything correctly and it was a bug on our end. I deleted and recreated that A record in the Netlify UI and it worked the second time around.
You can't point crm.netlify.com to choice of your server, as this is completely owned by netlify.
For pointing crm.{yourdomain.example} you need to create A record in your domains zone file pointing it to specific IP you want.
I am very new to hosting. I have just got VPS with no prior experience (just a little bit working with in a shared hosting with Cpanel)
The VPS came with CentOS and Cpanel installed. So, I just needed to go through initial setup of WHM. I did not change any thing. Apparently, there name severs and an IP were already allocated to my host. I did not change them.
Right after Creating Cpanel for a website I already had somewhere else (and It was working), I went and changed the name servers of domain to names servers of my new host.
I know it can take up to 48 hrs for name servers to propagate through internet but it is close to 48hrs and I still have below situation
https://IP of my host -> new website shows up
http:// IP of my host -> websites doesn't show up(the gray sorry! page ....)
www.mywebsite.com -> websites doesn't show up (nothing at all)
I have already flushed my dns so it has nothing to do with cash
Observations:
I have checked with DNS checker websites. My dns name servers ARE propagated.
IP of name servers and my host IP is also returns positive.
just www.mydomain.com does not return result.
Should I wait more or there is something wrong with server configuration or do I need to reset something on server?
Thanks in advance
Make sure that you have a valid CNAME record set for www.yourdomain.com . If your non-www domain name works fine and the www doesn't , you should set a CNAME record for www.yourdomain.com to resolve to yourdomain.com .
I have a GoDaddy domain www.exmaple.com which points to 255.255.255.255 (fake IP of course). My web server is behind a router that forwards port 80 to the appropriate port. All fine and dandy. However, like 99% of people out there, I have a dynamic IP. So I set up a hostname with noip.com called helloworld.ddns.net, set up their update client on my server (so it can update them whenever the IP changes (hasn't happened yet but i'm hoping it works as advertised), and then went to godaddy.com to change my records. Which is where stuff gets as hairy as harambe.
I started off by removing my A record, and changing my CNAME to point to helloworld.ddns.net.
Didn't work.
Googled around, and found that I need/should use the noip NSs. So I went back to godaddy, and changed my nameservers from theirs to the noip ones... ns[1,2,3,4,5].no-ip.com.
Still doesn't work. Should also point out, that after I made this change I lost the ability to set any records on my domain name. Which I guess makes sense since there's no point in godaddy having a record if I'm not using their NSs.
Tl;dr: How do I point godaddy domain, www.example.com, to a noip hostname, helloworld.ddns.net, which in turn points to my dynamic home ip, x.x.x.x.
Finally managed to solve my own issue, and I feel very silly for not realizing what the issue was before. The problem was that the CNAME was pointing to a subdomain (www) and therefore one couldn't access the site without including this in the URL. Summarised solution:
GoDaddy now has CNAME with a specific host name (ex www) and the noip domain as the value
No A record
Kept the default GoDaddy NSs
Configured forwarding w/o masking, to www.example.com... therefore, when someone tries to access example.com, they are automatically forwarded to the www subdomain.
A little bit of patience for propagation and everything was up and running.
I have setup web-hosting for the domain name, 'www.domainName.com' (forExample) and had it working fine, but when I removed the existing nameservers and placed in my web-hosting nameServers, it broke the 3rd party email hosting, which unbeknown to me was actively being used. To rectify this, my nameServers were removed, and the mail-hosting namerServers were added back:
ab1_mailNameServer_etc
ab2_mailNameServer_etc
Nothing else was changed but I now get a 'ERR_NAME_NOT_RESOLVED' error when i venture to the 'www.domainName.com' through my browser.
I looked up the domain A-Records using MXtoolBox and it tells me that no name servers can be found, although i have an A-Record for, domainName.com & www.domainName.com that point to the correct IP. I also have the correct A-Records in my hosting, and i know this because this all worked before my hosting nameServers were removed.
My question is, can I simply add back in my web-hosting nameServers under the existing email nameServers without breaking email-hosting link?
I am a lil frightened to do so, as I cannot risk breaking the email twice in one week.
Thanks in advance peeps! ;)
After changing back to mail-hosting's nameservers, if your emails have started working, then there's no problem with DNS propagation. In this case, an error "ERR_NAME_NOT_RESOLVED" is more likely a local computer problem and can be fixed by the flushing DNS and clearing the browse cache/cookies.
As long as primarily set nameservers (mail-hosting nameservers) are resolving correctly, adding hosting nameservers under to existing won't create any difference.
So apparently you can only have one set of nameservers (not sure if that's across the board, or just with this registrar) listed, then you need to add the 'MX entry', relevant CNAME, TXT-Records in your web hosting via cPanel and ur mail and web hosting should work in unity. Peace, hope that helps someoene, cause it took me freakn ages to find that out!
When my site goes down, I want to change my registrar DNS settings to
point to (for example):
ns1.this_site_is_down.com
ns2.this_site_is_down.com
ns3.this_site_is_down.com
ns4.this_site_is_down.com
where these nameservers would return a fixed IP with a low TTL for all
queries (or even a CNAME), and a webpage on that IP address would read
something like:
The owner of this website knows it is down and is working to fix
it. Once the site is fixed, you will no longer see this message.
To use this service, set your DNS servers to ... [as above]
Does such a service exist?
I realize this system wouldn't be perfect, but it would be useful.
DNS and "site is offline" messages
discusses creating your own 2nd nameserver to do this, but I'm looking
to do this with an existing service/server.
It doesn't exist for A records or CNAME records (the closest you can get here is using a round robin, but that doesn't solve your issue).
Your looking for a priority tag, which exists in MX only records.
I'm afraid your best option is just on the servers send out a 503 error with a HTML page as the ErrorDocument.