Nameserver/Cache Help

SpaceshipSpaceship
Watch

chris_reilly

Established Member
Impact
2
Hello,

I purchased http://www.thelifeofreillymovie.com/ and the domain is showing up just fine for everyone else but for me, i still see the 1and1 parking page.

I have cleared my cache in both browsers and also done a DNS flush.

How can i get it so i can see the site (should just say 'test') like it does for others and via my mobile.

Also, my FTP wont connect unless i use the IP instead as the domain

Please help

ta!
 
0
•••
The views expressed on this page by users and staff are their own, not those of NamePros.
Unstoppable Domains — AI StorefrontUnstoppable Domains — AI Storefront
Hi Chris,

This depends on in wich IP net you are, where you are located...the domain needs to proper "propagate"(word for the resolution) through the whole net of root servers(thousands all over the world) and takes between 24-72 hours(also depending on your registrar and other circumstances) so just be patient and give it another day or two...

If you still cannot see it, clear your cache a couple times since one or 2 times it's not cutting it sometimes......

If this still is a no go, try to install a different browser like chrome or opera, maybe this helps....

Keep us updated :)

Cheers

Liquid
 
0
•••
the problem isn't propagation, the problem is his computer has cached the dns reply already.

clear your dns cache.
 
0
•••
Most likely his ISP has cached the old name servers. Flushing his computer's dns cache will make no difference in such an instance.

In regards to the comment about root servers and propagation time ...

Firstly, the root servers have nothing to do with name servers within a TLD.

Secondly, TLD servers, at least in the major gTLDs (.com, .net, and .org) update in near real-time, so that's generally not an issue.

Most likely the OP will simply need to wait it out until their ISP cache refreshes (easiest). Or alternatively, if the OP still has access to 1and1 name server settings and can add host records, setup an A record(s) for the website's IP address (do so for both www and non-www versions of the domain; CNAME may not work as well due to the caching issue).

This is getting technical ... so again, it's likely easiest to just wait it out until your ISP's cache refreshes, which could be upto two days.

Ron
 
Last edited:
0
•••
Wait ~70 hours after domain name change and then start worring if everything is not working properly.
 
0
•••
You can as well try to access a given host from a proxy server hosted on another network (just search for a public web proxy). You can also ping or look at the trace route from a third party network to see if the right IP is associated with the domain. A large list of public trace route tools can be found here: traceroute.org

In general you should give a DNS update roughly 48 hours to go through.
 
0
•••
Dynadot — .com TransferDynadot — .com Transfer
Appraise.net

We're social

Escrow.com
Spaceship
Rexus Domain
CryptoExchange.com
Domain Recover
CatchDoms
DomainEasy — Zero Commission
DomDB
  • The sidebar remains visible by scrolling at a speed relative to the page’s height.
Back