Showing results for 
Search instead for 
Did you mean: 

Virgin default DNS blocking domain with certain keyword

Tuning in

I'm building a new website for a client:

Their website is completely unaccessible from Virgin broadband when using Virgin's DNS. It works immediately if you switch to Google's DNS or a mobile network.

It feels like there is a keyword blacklist on Virgin's DNS resolvers because any combination of those works in other TLDs/hostnames also fail to resolve:

Anything that has "pawpaddock" in the hostname fails to resolve to a server. Switching to Google or Cloudflare's DNS ( or or any mobile network, it works fine. All of our Virgin Media customers are experiencing this. It's not local to my network or setup.

Who do I contact to resolve this?



The odd thing above is I'm using as my DNS server during the above tests. Chrome can load the site but nslookup times out. Chrome and my terminal be using different methods of resolving DNS

Some DNS timeouts have been seen where Hub 5s have intercepted the DNS request.

Using Chrome try a dns leak test to see what it is up to.   A Standard Test will be fine.
Chrome has security settings that allow use of an encrypted DNS of your choice. that is Cloudflare's public DNS
Retry that lookup here :   and   it resolves for Cloudflare.

Here using a terminal :



Useful site. Here is the local DNS server I'm using with VM default DNS. Maybe you could try a lookup against that DNS server from your end see if you can replicate?



For me the VM DNS cache is

All DNS requests timed out using or its xxx xxx xxx 246 public IP.

nslookup    ( times out )

nslookup    ( times out )




nslookup    ( this does not look to be a valid DNS for nslookup )

From a leak test our DNS cache is shown as  I can not use that as a DNS it always times out.





Ah OK that's a red herring then

The dev subdomain is a problem.



Unable to resolve target system name


Tracing route to []
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms
  2     *        *        *     Request timed out.
  3    18 ms    10 ms     8 ms []
  4     *        *        *     Request timed out.
  5    10 ms    10 ms    24 ms []
  6    10 ms    10 ms     9 ms
  7    10 ms    10 ms     9 ms []
  8    25 ms    17 ms    16 ms []
  9    25 ms    25 ms    33 ms []
 10    23 ms    25 ms    24 ms []
 11    41 ms    32 ms    33 ms []
 12    34 ms    32 ms    32 ms []
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19    34 ms    36 ms    41 ms []

Trace complete.
Hub 5, TP-Link TL-SG108S 8-port gigabit switch, 360
My Broadband Ping - Roger's VM hub 5 broadband connection

It's (note the lack of .co)

The 3 to try are:


The AWS S3 one is the most suprising one to be blocked for me, which is why I suspect some form of keyword blacklisting. 

@alexcroox wrote:


The AWS S3 one is the most surprising one to be blocked for me, which is why I suspect some form of keyword blacklisting. 

That one's not blocked here either so looking increasingly like a local issue