I bought the domain from GoDaddy and hosting from Hostgator. I am using that domain as the add-on domain in the Hostgator. I have updated the nameserver of HostGator in GoDaddy 30 hours before. It got propagated. But on some devices, it is showing the website content in Hostgator, but on other devices, it shows the GoDaddy page. I do not know what is the issue. i have cleared the cache, restarted the device, did everything but nothing solved the issue
sorry to say that i do not know what is mean by SOA serial number.If you give the right link i will learn that. My problem got solved by the following way. when i ping the website, i did not get the IP address of my hosting. Then i flushed the DNS through cmd. Then the website loaded. Thanks for the reply.
Could anyone say what is the IP address that i got before the flush. Is that belongs to domain registrars (GoDaddy)?
Related
I have a dns confusion problem in my domain, there are more than 2 months that I changed the nameservers of my domain to cloud housting vps but sometimes I find that the domain displays the page of my previous host namecheap as shown in the picture how can I always force the domain to give the google server and not the namecheap server?
enter image description here
Usually, I check the status of my domain propagation using this tool:
whatsmydns.net
Checking yours, I see that all servers are pointing to the right NS, as well as the A records are always responding with the same two IP addresses from cloudflare, which seems correct. I would recommend doing a full cache clear on the device you are testing and try again.
My website suddenly stopped working.
When I search for the domain name in WHOIS websites it is showing the correct server ip address and correct DNS IP address.
I can reach the website by its IP address but somehow when I am trying the domain name in browser its not working and its showing "This site can’t be reached"!
There is no error in my server log.
I tried different browsers and different systems and it is same issue.
I am really confused. Even when I am sending GET requests with Postman to my domain, it not reachable but sending request to IP is working!
whois and DNS resolution are two separate things and one does not imply anything for the other, so in short, except in very specific cases, if you have a DNS resolution problem you should use DNS troubleshooting tools, not the whois and especially not web-based whois (the only relevant whois is the registry one).
Now you are giving so few details that noone can really help.
Among the possible ideas to check and probable problems:
you forgot to renew the domain, your registrar put it on hold or worse deleted it (that you can see in whois)
you did a change in the DNS resolution and now it does not work anymore, use online troubleshooting tools like Zonemaster or DNSViz; alternatively your registrar and/or webhosting company should be able to help (since you are neither giving here the domain name nor details about the troubleshooting you do: for DNS problems, the browser is not the first tool to use, look instead at dig).
in appear that the problem was DNS on our local system. we changed it to 8.8.8.8 and then we could access to our domain!
it's usually because you use an addon domain, not the main domain for hosting orders that are set up on cpanel whm
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!