Skip to content

If you’re still having issues with the site: some steps.

Flushing DNS Cache on Common Operating Systems

Windows

  1. Open Command Prompt:
    • Press Win + R, type cmd, and hit Enter.
    • Or search for “Command Prompt” in the Start menu, then right-click and choose “Run as Administrator.”
  2. Run the DNS Flush Command:
    • Type: ipconfig /flushdns and press Enter.
    • You should see a confirmation message: Successfully flushed the DNS Resolver Cache.
  3. Optional: Clear ARP Cache:
    • Type: arp -d * and press Enter.

macOS

  1. Open Terminal:
    • Press Command + Space, type Terminal, and press Enter.
  2. Run the Flush DNS Command:
    • For macOS Monterey and later:
      bash
      sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
    • For macOS Catalina, Mojave, and earlier versions:
      bash
      sudo killall -HUP mDNSResponder
    • Enter your admin password if prompted (it won’t be displayed).

 

You can also try using ‘incognito’ or private browsing mode on most browsers, this should fix the problem. Also a hard restart of your PC / Mac and a reset  of your modem / router at the point it comes into your house would work too. If you want to reach out to me direct you can get me at richard [at] continentaltelegraph.com

17 thoughts on “If you’re still having issues with the site: some steps.”

  1. While it was the DNS change that caused the initial problem, it persisted because my browser cached the “contact your hosting provider” page as the root page of https://www.timworstall.com That page has a ridiculously long expiry time on it.

    It might be a good idea to advise people to clear their browser cache too.

  2. Another trick is to put a querystring like ?a=1 which won’t be in the local cache, so will do a server retrieval.

    Also, happy to explain expiry to your chap ..

  3. Across all device types, Android is the world’s most popular OS with 45% of the global market, followed by Windows with 27%, then iOS with 18%, macOS with 6%, and desktop Linux with 1.6%…

  4. The Richard (NOT Murphy) did make me LOL

    Rest assured unless you develop an unprecedented capacity for unredeemed evil I doubt I’d confuse the two of you….

  5. Woz “bash” mean?

    It’s the Bourne-again shell.

    (You can file this under “accurate but not helpful in the slightest”!)

  6. The Richard (NOT Murphy) did make me LOL

    Rest assured unless you develop an unprecedented capacity for unredeemed evil I doubt I’d confuse the two of you….

    Hmmm.
    Maybe Tim and Murphy are actually friends and Richard Murphy does the tech stuff for Tim.
    If you ask the Murphster, I’m sure he would claim to have a level of expertise in computing. He has a YouTubes channel and everything dontcha know?!

    This non-Murphy claim could just be a smokescreen and their rivalry a big con to pull us all in.

    Time to come clean?
    *Squints suspiciously at Tim*

  7. @MntM25

    The site has been working fine for me on Feedly the entire time. I wouldn’t have known there was a problem if people hadn’t mentioned it.

  8. Clearing the (Chrome) Browser Cache for four weeks worked for me although I thought I’d done that before…

Leave a Reply

Your email address will not be published. Required fields are marked *