I'm a CloudFlare user many months ago. I love CDN cappabilities as change some domain name from one IP to a new one inmmediately with no DNS propagation issues. Well, today I tried to change some dns entries as "www" from an old IP to a new one, and change do not take the inmmediate effect as before. For example I changed IP one hour ago and IP is not changing yet. Always taked a few seconds to do it.
Any ideas what is causing this?
Thanks in advance
I am having similar issues. According to their support status they had some issues with DNS resolution earlier today. This could be causing some delays in updates. I set the TTL on the record to 5 minutes to see if this will force an update. As of now the record has not changed.
Related
Very rarely, I see URLs with a host name of "ww8" instead of "www" (e.g. http://ww8.aitsafe.com, https://ww8.welcomeclient.com/). Though rare, this appears to be consistent enough for there to be some sort of logic or history behind this, but I have not been able to figure out what it could be about.
Does anyone know what the host name "ww8" stands for and when it is used? Or is this simply a random peak of arbitrarily chosen non-standard hostnames?
This is a subdomain system to identify subdomains. ww8 means that is the 8th subdomain. This system is used to balance load on the server side
I am learning about apache and its various modules, currently i am confused about mod_expires. What i read so far is that using this module we can set future expiry header for static files so that browser need not to request them each time.
I am confused about the fact that if some one change css/js or any image file in between, how will browser come to know about it since we have already told the browser that this is not going to change say for next 1 year.
Thanks in advance
It may not be possible for all provided content on your HTTP server, but you can simply change the name of the file to update a file on the client side from the server. At that point, the browser will download the new content.
Sometimes, for websites with less traffic it is far more functional to set the cache to a much lower value.
An expiration of 365 days should always be used with caution, and the fact that you can set an expiration of 1 year does not mean you always have to do it. In other words, do not fall prey to premature optimization.
A good example of setting cache expiration to 1 year are countries' flags, which are not likely to change. Also, be aware that with a simple browser refresh of a page, the client can discard the local cache and download the content again from the origin.
A good and easy way of testing all this is to use Firefox with Firebug. With this extension, you can analyze requests and responses.
Here you can find the RFC specifications.
I just changed the location of my blog, and have done the appropriate redirects. Does anyone have knowledge or experience for the delay in updating all the links across Google?
Reason I ask, I wish to change the A record. So this will eliminate the .htaccess file, and thus null and void the redirect.
How long must I wait prior to the undertaking?
Thank you.
As codeka said, it can take many weeks for every page to be updated. And don't forget if you go ahead and remove the redirects by changing the A record, any links still pointing to the old location will now be invalid.
If you haven't done so already, log into Google Webmaster Tools, add your new domain as a site, then go to "Change of address" to let Google know you've moved the site.
It depends on the site. Some sites (e.g. ones that get updated frequently) get reindexed pretty quickly (every day, even). Others may take a month or two. For the best chance of it having picked it up, I would give it around 3 months.
Alternatively, you can just do a search for your site every few days and check which version Google is returning.
The 301 redirect is a "permanent" redirect, so you should be ready to keep it for quite some time :-).
Google mentions other things to look at in the Help Center article at http://www.google.com/support/webmasters/bin/answer.py?answer=83105 -- in particular I'd recommend working to make sure that old links to your site are updated accordingly (take the time to try to contact people linking to your site, you can find the links in Webmaster Tools).
Hey folks. I have a client who's old website was called toastkid.com. I set up a new site, alekskrotoski.com, and had the old www.toastkid.com domain point to the new site. I have a 301 redirect working, so when you go to www.toastkid.com the address bar updates to alekskrotoski.com. So, the 301 is definitely working fine.
However, i also expected that google would update it's search results to say alekskrotoski.com, effectively transferring all the google juice over. But, it still says www.toastkid.com in a search for 'aleks krotoski'. I did the redirect on thursday night (3 days ago at time of writing) and thought it would have taken effect by now. How long would it normally take for google to update its index? Is there anything i can do to speed it up? Could there be anything stopping it? The site is already registered and verified with google webmaster.
Grateful for any advice - max
Easy. A few days are not going to cut it, it can take weeks until a change has arrived in the index.
To gain information about how Google sees your page, you can register with Google Webmaster Tools. Maybe if you register both sites, and add a Sitemap, you can make Google aware of the transition faster.
Otherwise, just wait. The change is going to take effect eventually.
You must wait at least 1 week to see the update of the URLs in SERP.
Much depends on the trust of your old site that determines the frequency of crawling.
However Google will continue to try periodically (monthly, annually) crawl the old URLs, don't consider this
Would you want all your hard earned Google juice to go elsewhere just because your site was misconfigured for a a few days? I don't think so. You shouldn't want this to change quickly.
I have a php web site under apache (at enginehosting.com). I rewrote it in asp.net MVC and installed it at discountasp.net. I am comparing response times with firebug.
Here is the old time profile:
Here is the new one:
Basically, I get longer response times with the new site (not obvious on the pictures I posted here but in average yes with sometimes a big difference like 2s for the old site and 9s for the new one) and images appear more progressively (as opposed to almost instantly with the old site). Moreover, the time profile is completely different. As you can see on the second picture, there is a long time passed in DNS search and this happens for images only (the raw html is even faster on the new site). I thought that once a url has been resolved, then it would be applied for all subsequent requests...
Also note that since I still want to keep my domain pointed on the old location while I'm testing, my new site is under a weird URL like myname.web436.discountasp.net. Could it be the reason? Otherwise, what else?
If this is more a serverfault question, feel free to move it.
Thanks
Unfortunately you're comparing apples and oranges here. The test results shown are of little use because you're trying to compare the performance of an application written using a different technology AND on a different hosting company's shared platform.
We could speculate any number of reasons why there may be a difference:
ASP.NET MVC first hit and lag due to warmup and compilation
The server that you're hosting on at DiscountASP may be under heavy load
The server at EngineHosting may be under utilised
The bandwidth available at DiscountASP may be under contention
You perhaps need to profile and optimise your code
...and so on.
But until you benchmark both applications on the same machine you're not making a proper scientific comparison and are going to be pulling a straws.
Finally, ignore the myname.web436.discountasp.net url, that's just a host name/header DiscountASP and many other hosters add so you can test your site if you're waiting for a domain to be transferred/registered, or for a DNS propagation of the real domain name to complete. You usually can't use the IP addresse of your site because most shared hosters share a single IP address across multiple sites on the same server and use HTTP Host Headers.