FBQ: New Website Launched, Client Seeing Old Website

image

Facebook Questions

When I see a Facebook post that I think deserves a write up or I respond with a huge paragraph. I usually end up putting it up somewhere because I think the content is useful for all.

Launched new site. Client see's old site!

Todays Facebook post talks about a unique situation we've all experienced. You launched a new website, and the client is still seeing the previous old website.

Granted, this really isn't a unique situation, it' happens frequently. But in this specific Facebook post, it's a unique situation.

Why do clients see the old website when I can see the new website?

There's a couple of reasons for this, but majority of the time it's either a caching issues or DNS issue.

Client Side Cache

DNS Issues

Split DNS Implemented by IT

Avoiding Cache and DNS Issues

The key here is getting a remote session going. The easiest I've found is a screen share, Google Hangouts or Zoom (you can take control).

Glad you got it figured out. Seen this situation more than I can count on my hands and feet.

The key here is getting a remote session going. The easiest I've found is a screen share, Google Hangouts or Zoom (you can take control).

Have them ipconfig /all and then nslookup the domain. Then do a nslookup domain.com 8.8.8.8

From there you get to see what DNS servers their client is using, what the domain is resolving to and what google is resolving the domain to.

For some reason there looks to be a split DNS situation here. Where they're using the main company domain for some internal services for Active Directory or similar. It's 2021, definitely move to a non-routable domain or routable domain but only use it for Active Directory. At the same time, a domain rename or migration is a huge undertaking in larger environments so this may never change until it's a real issue.