Forum Discussion

penguin42's avatar
penguin42
On our wavelength
2 years ago
Solved

routing problems to Google DNS?

(Manchester, VM broadband wired, everything else is working fine)

It looks like there's some routing problems, only to Google's DNS servers, and I'm failing to resolve any google.com or similar;

traceroute/mtr to the IPs of ns2.google.com ( 216.239.34.10 ) and ns4 ( 216.239.38.10 ) shows it intermittently failing in manc-core-2b-ae93-650.network.virginmedia.net

It's working fine from my none virgin-media connections.

Down-detector is showing a big spike in Google problems centred around Manchester and London, so not just me; not sure if it's only VM or not.

Please forward to someone with a hammer near VMs corp routers.

  • ModTeam's avatar
    ModTeam
    2 years ago

    Hi All, 

    We're very sorry for any issues you may be facing today accessing sites hosted by AWS. We are aware of this issue, affecting some customers, and this is being investigated, We hope to have this resolved as quickly as possible and apologise again for any inconvenience. 

    Modteam

94 Replies

Show More
  • Frustrated2021's avatar
    Frustrated2021
    Joining in
    2 years ago

    Gotten worse for me totally gone in Manchester/Salford area not nothing accessible at all

  • Martyn's avatar
    Martyn
    Superfast
    2 years ago

    didn't notice any issues, is this only affecting HFC network or xgs too?

    • Alex_1991's avatar
      Alex_1991
      On our wavelength
      2 years ago

      Haha knew it was too good to be true. I’m having the issue again as well this morning 

  • eliotcole's avatar
    eliotcole
    Tuning in
    2 years ago

    I am wondering if this is a general Virgin issue, as I'm seeing it without Google, too.

    Almost like there is some kind of DNS jiggery pokery going on from Virgin ... because I'm using a private DNS which has issues ... but when I use a different one (Cloudflare) 1.1.1.1 ... that's absolutely fine. 👍

    Plus, if I use a VPN ... godlike. 😍

    ---

    Also, to the SharePoint advice earlier in this thread ... if you open the file in the application, it's still connecting to SharePoint.

    • PMilne87's avatar
      PMilne87
      On our wavelength
      2 years ago

      Re SharePoint, you are accessing the document library but bypassing the SSO element required to access the web page itself.

    • Sasquatch-Sco's avatar
      Sasquatch-Sco
      Tuning in
      2 years ago

      Clouldlfare is my main one. That stopped working on Tuesday for me and Google and default VM DNS's are the same. Fine as soon as I connect to 4G mobile hotspot or go through a VPN.

      • unisoft's avatar
        unisoft
        Super solver
        2 years ago
        Sasquatch-Sco wrote:

        Clouldlfare is my main one. That stopped working on Tuesday for me and Google and default VM DNS's are the same. Fine as soon as I connect to 4G mobile hotspot or go through a VPN.

        Exactly what I experience on family member's broadband with Virgin but Ok on 4G/5G or though another ISP to same site behind Cloudflare. The silence on this is annoying, but the family member will know how to give VM the boot if this is not fixed soon and another long term customer gone never to return as they have other FTTP providers in their area now and this could be the nudge to have temporary hassle of install of new fibre and ONT instead.

  • saamuel's avatar
    saamuel
    Settling in
    3 days ago

    Sounds like a frustrating issue — definitely looks like a routing problem specific to Virgin Media and their path to Google’s DNS (especially if it works fine on other ISPs).

    If this keeps happening and you're comfortable managing your own setup, you might want to look into how to host your own public nameserver. It’s not for everyone, but it gives you full control over DNS resolution without depending on third-party providers like Google or your ISP.

    There are lightweight DNS server tools you can run on a VPS or home server (like BIND, PowerDNS, or even Pi-hole with unbound for recursive DNS). That way, you're resolving queries directly and can bypass some of these routing issues entirely.

    Might be worth a try if this becomes a regular headache. Otherwise, switching to another public DNS like Cloudflare (1.1.1.1) or OpenDNS might help in the short term.