Jump to content
quickjeff

Strange Cache Issue after Migration

Recommended Posts

Hi Guys, 

I wanted to reach to everyone in the community to see if someone has come across this issue. 

We have a client that had a website built in PHP. 

We provided our client with a new website built on ProcessWire.

Our client has their domain name registered  with register.com and their old website was built by another developer who was hosting the website in a virtual server at gandi.net.  

The DNS settings were as follows:

Domain name was pointed to the gandi.net in order to display the website files. 

The MX records were pointed to Google servers for company emails. 

The Name servers were as is which is the stock register.com name servers.

We were not able to speak with the old developer to setup a time to update the files so we were asked by our client to move forward without contacting the old developer.

How we setup the new website:

In order to avoid down time of the email accounts and not having to setup new MX records on another host, we simply setup our clients new website on GoDaddy shared hosting and changed the A record in their register.com DNS settings to point to the new hosting account. Basically, an IP change. Everything else they had stayed the same, meaning we did not change the MX records and we did not change the name servers.

Here is the issue:

Some website visitors are seeing the new website, some are seeing the old website.  We first thought it was due to browser caching or the propagation did not fully complete when they tried to visit the website.  After telling our client to wait until the new DNS settings or try to clear their cache, we thought they were all good to go. 

Now our client is contacting us saying that the issue is still happening. So we contacted register.com and had them resubmit the new DNS settings again, basically the same IP change we did.  

Result:

Some users are still seeing the old website on certain routers. We are also seeing the old website on certain routers we use and the new site on other routers. 

Can anyone provide some guidance? Has anyone seen this issue before?

We even pinged the website and it shows the correct server, we also used whatsmydns.net to see what the site is coming up as across the world and we also see the correct server. Lastly, we sent the url to our partners in Germany and they see the new website and not the old one. 

This is honestly the oddest issue I have seen and unsure as to why this is going on?

Here is our clients site:

medstarlab.com

Share this post


Link to post
Share on other sites

The only thing I would recommend is to flush the DNS cache for that domain.

  • Like 1

Share this post


Link to post
Share on other sites

@cstevensjr - I have flushed my system DNS cache, cleared my browser history etc. I am beginning to think that this is an ISP issue. 

Its very odd, I can see the new website when I connect to a hot spot, I can see the old site when I connect to my home office internet. 

Share this post


Link to post
Share on other sites

Dns is strange. I've seen this before. In the end (after a week) it was solved, but I have no clue why it took so long.

1. When did you change the A record for the first time?

2. When did you change it for the second time? 

3. I've noticed that both www and non-www are loaded separately. Perhaps the www subdomain was changed later on? You can change the .htaccess so traffic is directed to either www or non-www.

I always use http://dns.squish.net/ to determine if the DNS is setup correctly ( medstarlab.com resolves to 192.186.217.98).

  • Like 1

Share this post


Link to post
Share on other sites

Sorry, I wasn't very detailed.  

i actually meant you or the hosting provider (ISP) needs to flush the DNS cache from the cPanel (or it's equivalent).  On some hosting providers, you can do it yourself (i.e. DreamHost).  Normal DNS propagation takes at least 72 hours or longer.  It all depends on where the actual server is located, that's why some see the website where it's been moved to and others still see the old DNS information.  There are times where due to traffic congestion or other router issues, the updated information doesn't make it everywhere (across the world) in a timely manner.

Flushing the DNS cache will restart the process and usually things will start working as required.  You are correct that you need to work with the hosting provider (ISP) to clear this up.  GoDaddy support should have been on top of this, since they are hosting the website now.  Please open a trouble ticket with them and good luck.

  • Like 2

Share this post


Link to post
Share on other sites

@arjen

1.) The first time it was changed was 3 weeks ago.

2.) The second time it was changed 4 days ago.

3.) Correct, it was changed after. I can adjust the htacess. 

In regards to the DNS, medstarlab.com should resolve to 192.186.217.98 which is where its hosted now but sometimes I will see the old website (Only when I connect to the internet on my home router, which is Comcast Xfinity Internet.) I can see the new site when I connect to something else for data.

@cstevenjr

In regards to flushing the DNS, GoDaddy can see the new website, Register.com which is where the domain name is can also see the new website, when we ping the website url, we get the right IP for the right server.  :'(

Share this post


Link to post
Share on other sites

@cstevenjr

In regards to flushing the DNS, GoDaddy can see the new website, Register.com which is where the domain name is can also see the new website, when we ping the website url, we get the right IP for the right server.  :'(

Of course GoDaddy can see the website (it's local to them, they pushed or received the DNS change, they have multiple high capacity links and the affected website is at one of their facilities).  Of course register.com can see the website (they pushed or received the DNS change and have multiple high capacity links).

Other people (your users throughout the world) won't see the new website until the probable DNS propagation issue is resolved.  That's the most likely situation for this issue, however it's still most likely a hosting provider (ISP) problem and there could be other configuration issues.

The propagation of DNS information could be affected by many reasons (for the users who cannot see the new website).

  • Like 1

Share this post


Link to post
Share on other sites

post-756-0-46973400-1443797752_thumb.png

From Southern California (via Time Warner Internet link)

post-756-0-17115100-1443798486_thumb.png

From Southern California (via AT&T Internet Link)

As an aside, hopefully your customers aren't getting your website confused with this one

post-756-0-25677000-1443798523_thumb.png

which is medstarlabs.com versus medstarlab.com

Best Regards,

Charles

  • Like 3

Share this post


Link to post
Share on other sites

@cstevensjr - Thanks for the screen shot. 

This really boggles my mind.

I havent seen something like this, we might resort to finally pointing the Nameservers to our hosting and setting up their MX records. 

Share this post


Link to post
Share on other sites

All, think we figured it out. 

There was one iPv6 Setting pointing to the old domain. We deleted this record, now we see the new site all the time. 

Its good to have an extra set of eyes on something, thanks to all that helped on this. 

  • Like 2

Share this post


Link to post
Share on other sites

Glad to hear you sorted it out. Dns can be frustrating at times.

Share this post


Link to post
Share on other sites

@arjen 

Yes indeed. We are still waiting for it to fully propagate , can you screen shot what you see?

Share this post


Link to post
Share on other sites

@Christophe, thanks for the update! Seems like the solution is working. I don't wan to Jinx it haha. 

I will report back the status after today.

Share this post


Link to post
Share on other sites

I'm seeing the new one too.

also here!

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By modifiedcontent
      I had upgraded my Apache configuration to include PHP7.2 and PHP7.3 for a Laravel-based script on the same server. Somehow it/I messed up a previously fine Processwire site, in a very confusing way.
      The site still looks fine, but editing template files has no effect whatsoever. It is stuck on some kind of cached version. I have already disabled PHP7's OPcache, cleared browser caches, etc, with no effect.
      The pages now apparently come from PW's assets/cache/FileCompiler folder, even though I never enabled template caching for this site.
      I have tried adding "namespace ProcessWire;" to the top of the homepage template file, but then I get this fatal error:
      My functions.php file pulls data in from another Processwire installation on the same VPS with the following line:
      $othersitedata = new ProcessWire('/home/myaccount/public_html/myothersite/site/', 'https://myothersite.com/'); That apparently still works fine; the site still displays data from the other installation, but via the "cached" template that I am now unable to change.
       
      I don't know where to start with this mess. Does any of this sound familiar to anyone? Any pointers in the right direction would be much appreciated. 
       
      Edit:
      Adding "$config->templateCompile = false;" to config.php results in the same fatal error as above. 
    • By Jan235
      Hello,
      I'm started to play around with processwire. And I like it! My local dev system is up and runnig. I'm using the template factory with Twig. Anybody who use Twig and ProCache or is it possible to use both modules?
      Thanks in advance
    • By anttila
      I developed my own web store platform on ProcessWire. Work like a charm. However, I would like to know what is the best way to cache web store? There is a shopping cart, many languages and previously watched products which need to run without cache but everything else could be cached. Is there a way to use PW's own cache or ProCache for everything else except for certain HTML ID? I have used MarkupCache for categories in some cases.
      I'm addicted to speed. Everything has to be loaded as fast as possible or even faster. My next step is developing AMP HTML as part of the platform, but that is not helping normal version.
    • By eangulo
      Hello everyone,
      Usually in many CMS database tables prefixed or suffixed with "cache" can be manually cleared without a problem because the system will populate them on the "next page request". Actually in Processwire I am expecting this behaviour:
      [On PW 3.x]
      Manually clear table "caches" in database Go to "client" side (not in the admin panel) All references to my "/site/modules" in my template files does not work : wire("modules")->get(""), $modules->get("") and modules()->get("") PHP error:  Fatal error: Uncaught TypeError: Return value... My _init.php file are not able to find the references to my /site/modules/  The client side not working because this PHP fatal error. If I go to the admin panel "Admin -> Modules" and I trigger the action "Check for New Modules" in the top-right corner in the page, it populates the caches table with the required information and them the client side works.
      It is normal? Or I am doing something wrong ?
      A solution could be to manually call the script that the button "Check for New Modules" calls, but I want to know if  I am doing something wrong here.
      Thank you in advance guys ! 
    • By rolisx
      Hi Guys,
      Just finished a website locally and wanted to upload it on the webserver of my customer. I got a server 500 error. Now, the guidelines of the hoster (world4you.com) does not allow "Options" in the htaccess-file. So, when I uncomment these:
      Options -Indexes
      Options +FollowSymLinks
      the site is visible, but the content won't show and no links are available. Not sure if I need the Symlinks-part but I guess I need a workaround for the Index-part. Can anybody help here? I need the website up and running asap....
      Thanks!
      Roli
×
×
  • Create New...