Ocerclockers Main Shop Website Issue

TBirdUK

TBirdUK

TBirdUK

Soldato
Joined
9 Jul 2005
Posts
2,673
Location
High Wycombe
Is anyone else having an issue with the overclockers shop webpage?

I cant search in chrome, or sort anything, it just doesnt respond/refresh - I've tried 2 different computers.

Microsoft Edge does work, I just dont like using it..
 
TBirdUK said:
Is anyone else having an issue with the overclockers shop webpage?

I cant search in chrome, or sort anything, it just doesnt respond/refresh - I've tried 2 different computers.

Microsoft Edge does work, I just dont like using it..
Click to expand...

You cleared your cache?
 
TBirdUK said:
Is anyone else having an issue with the overclockers shop webpage?

I cant search in chrome, or sort anything, it just doesnt respond/refresh - I've tried 2 different computers.

Microsoft Edge does work, I just dont like using it..
Click to expand...

Try flushing the dns on your computers.


How to run ipconfig /flushdns

1.Click the Start menu or press the Windows key.

2.Type cmd in the search bar.

3.Right-click "Command Prompt" and select Run as administrator.

4.Click "Yes" if prompted to allow the app to make changes to your device.

5.In the Command Prompt window, type ipconfig /flushdns and press Enter.

6.You will see a confirmation message like "Successfully flushed the DNS Resolver Cache".

If that fails, power down your ISP router and restart it.

If that fails too try this in a command prompt (run as admin) :- tracert www.overclockers.co.uk
once it is done it will say trace complete, if all went well. If it fails maybe an issue with your ISP DNS or cloudflare issue for you, like it thinks your ISP is causing a DDOS (A DDoS, or Distributed Denial of Service, attack is a cyberattack where a target server or network is overwhelmed with a flood of internet traffic from multiple sources.). If that is the case then just wait a couple of hours and try again later.
 
Last edited:
Purgatory said:
If that fails too try this in a command prompt (run as admin) :- tracert www.overclockers.co.uk
Click to expand...
Just for some context: you absolutely do not need to use an elevated command prompt to run trace route. Elevated terminal sessions are for performing tasks that require... elevated permissions. Trace route couldn't be further from that, really. Trace route asks each hop to respond on the route to the destination and then outputs the reponse to the CLI. It doesn't do anything remotely special to warrant an elevated terminal session.

Flushing the DNS cache only removes entries that have been previously looked up and cached. This cache doesn't include any DNS records where their TTL has expired - a fresh lookup would be performed in those instances.

Furthermore, trace route is a poor tool to test DNS name resolution. Trace route is intended for routing purposes - ensure a route from A to B is as expected and reachable. It also relies on ICMP (layer 4) and is only good if each hop will respond to ICMP. A lack of response is denoted by the * responses that you may see in the output. However, it does resolve the DNS name as part of the trace route process itself (as it's not possible to perform a trace route without the IP of the FQDN/destination) and that does test the DNS name resolution, albeit in a crude manner.

That aside, it's also possible to test DNS resolution by using nslookup in command prompt/terminal/PowerShell. And added bonus: nslookup returns all of the responses. For example, if there are multiple A/AAAA records for an FQDN, nslookup will show them all. This is the case for the OcUK website.

Code: 
nslookup overclockers.co.uk

This will use the DNS server configured on the NIC by default. If the name resolution fails for any reason, you can perform a lookup using another DNS server:

Code: 
nslookup - <DNS server address>
nslookup - 1.1.1.1
overclockers.co.uk

Nonetheless, the fact that Edge works suggests this is just a cache issue in Chrome. Ctrl+Shift+Del - bin it all.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom