cancel
Showing results for 
Search instead for 
Did you mean: 

Router seems to be blocking a single website

FIXED
Highlighted
Dabbler
Posts: 10
Thanks: 1
Registered: 4 weeks ago

Router seems to be blocking a single website

Hi,

I've been trying to access a certain website (Brazil national statistics). I get a message each time saying that th re site cannot be reached. Yet I know that the site is up because colleagues working elsewhere can see it.

Things I have tried:

Different browser.

Different computer on same home wifi

Phone on same home wifi

Reset the router and then try to access the site.

All the above things fail. However if I use my phone on the 4G network with no wifi then I can access the site.

It all points to the router blocking this website for some reason and the "block" is not removed when resetting the router.

Can anyone see a solution? With thanks.

24 REPLIES 24
Highlighted
Community Veteran
Posts: 4,479
Thanks: 649
Fixes: 11
Registered: ‎05-04-2007

Re: Router seems to be blocking a single website

Sounds like you have tried a lot of things.

Can you post the model of the router you're using. Is it a standard PlusNet Hub One or something else?

Highlighted
Hero
Posts: 4,915
Thanks: 2,117
Fixes: 141
Registered: ‎30-06-2016

Re: Router seems to be blocking a single website

@dwoolv 

It's probably the Plusnet DNS server causing your issue. Depending on what device you are using you should be able to set alternatives in your IPv4 settings. Try the Google ones on 8.8.8.8 and 8.8.4.4. Device DNS settings over ride the Hub ones.

Highlighted
Dabbler
Posts: 10
Thanks: 1
Registered: 4 weeks ago

Re: Router seems to be blocking a single website

Thanks Alex.

It is a Thomson TG585 (v7). Something of an antique.

Highlighted
Community Veteran
Posts: 4,479
Thanks: 649
Fixes: 11
Registered: ‎05-04-2007

Re: Router seems to be blocking a single website

Also just thought of a few other things:

If you can PM me or other people the link you are trying to access. It sounds to me that it may not be the router.

It could be a routing issue between PlusNet and Brazil. It won't be an easy one for PlusNet if there is a fault and it is outside their network I'm afraid.

I am at home and I use Virgin Media, (or as I like to call it Branson Media). I am not at my sisters at the moment, who does use it so can't test our PlusNet connection at the moment. However, I am sure someone here who is currently using PlusNet can try your link. If it doesn't work for them either then it rules out it being your particular router.

Also can you post a traceroute to the site?

I am happy to test it on my Branson Media connection. Just let me know if I can help.

Highlighted
Dabbler
Posts: 10
Thanks: 1
Registered: 4 weeks ago

Re: Router seems to be blocking a single website

Hi Baldrick,

That might be the issue but I am hitting another problem with it.

I have gone to my wireless connection properties for TCP/IPv4 and set a radio button which says:

"Use the following DNS server addresses"

And put the preferred DNS server address as 8.8.8.8

When I then close and reopen the same dialog boxes, the settings are still for 8.8.8.8. All well and good.

Then I try a browser and open the BBC website. That opens ok.

Then I try the problem website. Get same message as before - it is still blocked.

Then if I go back to the TCP/IPv4 properties I find that the 8.8.8.8 has been overwritten with 127.0.0.1 (!)

So it might be a solution - just cannot see how to implement it. Thanks

Highlighted
Dabbler
Posts: 10
Thanks: 1
Registered: 4 weeks ago

Re: Router seems to be blocking a single website

Hi Alex,

Yes the link is:

https://www.ibge.gov.br

Thank you for trying.

Highlighted
Hero
Posts: 4,915
Thanks: 2,117
Fixes: 141
Registered: ‎30-06-2016

Re: Router seems to be blocking a single website

@dwoolv 

It doesn't work for me using OpenDNS and Firefox.

Highlighted
Community Veteran
Posts: 4,479
Thanks: 649
Fixes: 11
Registered: ‎05-04-2007

Re: Router seems to be blocking a single website

Well this is my tracert, or traceroute as the Mac command says. It did load when I tried it on my connection. Just in case it helps, here we go:


@Baldrick1 wrote:

@dwoolv 

It doesn't work for me using OpenDNS and Firefox.

 

Last login: Wed Jul 15 10:04:48 on console
Alexanders-Mac-mini:~ alexanderhunt$ traceroute www.ibge.gov.br
traceroute to www.ibge.gov.br (170.84.40.26), 64 hops max, 52 byte packets
 1  routerlogin.net (192.168.0.1)  0.929 ms  0.620 ms  0.969 ms
 2  * * *
 3  bmly-core-2a-xe-200-0.network.virginmedia.net (80.1.224.225)  11.754 ms  17.469 ms  12.902 ms
 4  bmly-core-2b-ae1-0.network.virginmedia.net (213.105.159.234)  10.842 ms  9.836 ms  10.228 ms
 5  * * *
 6  m686-mp2.cvx1-b.lis.dial.ntli.net (62.254.42.174)  23.980 ms  10.841 ms  10.583 ms
 7  * * *
 8  uk-lon01b-ri1-ae-25-0.aorta.net (84.116.136.102)  11.819 ms
    uk-lon01b-ri1-ae-23-0.aorta.net (84.116.135.30)  13.747 ms  23.875 ms
 9  be8-grtlontlw2.net.telefonicaglobalsolutions.com (213.140.52.60)  11.815 ms  12.144 ms  19.647 ms
10  * * 176.52.248.242 (176.52.248.242)  95.398 ms
11  94.142.97.165 (94.142.97.165)  136.344 ms
    84.16.15.68 (84.16.15.68)  169.381 ms  174.151 ms
12  94.142.98.152 (94.142.98.152)  172.707 ms  181.453 ms
    94.142.98.172 (94.142.98.172)  170.353 ms
13  84.16.6.133 (84.16.6.133)  175.342 ms  175.750 ms
    94.142.98.152 (94.142.98.152)  178.350 ms
14  84.16.6.133 (84.16.6.133)  165.545 ms  175.173 ms  184.249 ms
15  177.14.3.20 (177.14.3.20)  232.657 ms
    177.14.2.81 (177.14.2.81)  230.937 ms
    177.14.3.20 (177.14.3.20)  248.889 ms
16  177.14.2.89 (177.14.2.89)  225.750 ms  229.890 ms
    177.14.2.81 (177.14.2.81)  245.377 ms
17  177.14.2.89 (177.14.2.89)  238.423 ms  223.871 ms  222.747 ms
18  177.14.2.100 (177.14.2.100)  229.856 ms  234.486 ms  222.651 ms
19  177.14.3.119 (177.14.3.119)  216.491 ms
    177.14.2.100 (177.14.2.100)  230.606 ms *
20  * * *
21  * * *
22  * * *

 

Highlighted
Hooked
Posts: 8
Thanks: 4
Fixes: 1
Registered: ‎08-07-2017

Re: Router seems to be blocking a single website

For me it looks like a routing issue AND a Plusnet DNS issue!

 

From my Plusnet connection (31.125.x.y) I can resolve the name using a couple of public servers as a test

$ nslookup www.ibge.gov.br. 1.1.1.1
Server: 1.1.1.1
Address: 1.1.1.1#53

Non-authoritative answer:
Name: www.ibge.gov.br
Address: 170.84.40.26
or

$ nslookup www.ibge.gov.br. 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: www.ibge.gov.br
Address: 170.84.40.26


but normal Plusnet DNS servers do not give an answer for that name

$ nslookup www.ibge.gov.br. ntp.plus.net.
;; Got SERVFAIL reply from 212.159.13.49, trying next server
;; Got SERVFAIL reply from 212.159.6.10, trying next server
;; Got SERVFAIL reply from 212.159.6.9, trying next server
Server: ntp.plus.net.
Address: 212.159.13.50#53

** server can't find www.ibge.gov.br: SERVFAIL


yet the SafeGuard Plusnet servers do:
$ nslookup www.ibge.gov.br. 213.120.234.38
Server: 213.120.234.38
Address: 213.120.234.38#53

Non-authoritative answer:
Name: www.ibge.gov.br
Address: 170.84.40.26

$ nslookup www.ibge.gov.br. 213.120.234.42
Server: 213.120.234.42
Address: 213.120.234.42#53

Non-authoritative answer:
Name: www.ibge.gov.br
Address: 170.84.40.26

so the DNS resolution is one issue.

 


But from my Plusnet connection, I cannot reach that host on https port 443 anyway:

$ telnet 170.84.40.26 443
Trying 170.84.40.26...
telnet: Unable to connect to remote host: Connection timed out

yet trying from a VPS in America (Internet address 199.175.x.y) I can:

# telnet www.ibge.gov.br 443
Trying 170.84.40.26...
Connected to www.ibge.gov.br.
Escape character is '^]'.
^]
telnet> q
Connection closed.


traceroute from my Plusnet (which ultimately cannot https to the server)


$ traceroute 170.84.40.26
traceroute to 170.84.40.26 (170.84.40.26), 30 hops max, 60 byte packets
1 OpenWrtCB.beech (192.168.203.1) 0.637 ms 0.725 ms 0.790 ms
2 253.core.plus.net (195.166.130.253) 12.851 ms 17.289 ms 17.247 ms
3 84.93.253.107 (84.93.253.107) 17.207 ms 84.93.253.111 (84.93.253.111) 18.062 ms 19.221 ms
4 195.99.125.142 (195.99.125.142) 19.660 ms 21.356 ms 195.99.125.138 (195.99.125.138) 22.024 ms
5 peer7-et-4-0-5.telehouse.ukcore.bt.net (194.72.16.130) 23.593 ms peer7-et-0-1-7.telehouse.ukcore.bt.net (109.159.252.240) 24.721 ms peer7-et-0-0-5.telehouse.ukcore.bt.net (109.159.252.184) 25.658 ms
6 * * *
7 lon-tel-02t.voxility.net (5.254.112.187) 26.208 ms 13.476 ms 13.281 ms
8 mia-nap-02t.voxility.net (104.152.46.90) 119.290 ms 120.010 ms 122.879 ms
9 * * *
10 5.254.127.74 (5.254.127.74) 127.074 ms 128.181 ms 128.572 ms
11 * * *
12 * * *
13 187.110.228.41.mobtelecom.com.br (187.110.228.41) 212.012 ms 215.156 ms 211.808 ms
14 * * *
...(just * * *s)
30 * * *

 

 

traceroute from the test IP in America (which ultimately can https to the server)


# traceroute 170.84.40.26
traceroute to 170.84.40.26 (170.84.40.26), 30 hops max, 60 byte packets
1 192.243.107.154 (192.243.107.154) 0.123 ms 0.055 ms 0.053 ms
2 192.168.182.2 (192.168.182.2) 0.206 ms 0.216 ms 0.288 ms
3 38.142.200.81 (38.142.200.81) 1.115 ms 1.128 ms 1.186 ms
4 te0-0-0-3.rcr21.dfw05.atlas.cogentco.com (154.24.22.5) 0.912 ms 0.902 ms 0.826 ms
5 be3236.ccr22.dfw03.atlas.cogentco.com (154.54.24.165) 0.988 ms be3235.ccr41.dfw03.atlas.cogentco.com (154.54.7.177) 0.846 ms 0.736 ms
6 be2764.ccr32.dfw01.atlas.cogentco.com (154.54.47.213) 0.887 ms 1.300 ms be2269.ccr31.dfw01.atlas.cogentco.com (154.54.7.41) 1.164 ms
7 be2441.ccr41.iah01.atlas.cogentco.com (154.54.41.65) 6.311 ms be2443.ccr42.iah01.atlas.cogentco.com (154.54.44.229) 6.013 ms 6.008 ms
8 be3569.ccr21.mia01.atlas.cogentco.com (154.54.82.242) 33.017 ms 33.100 ms be3570.ccr22.mia01.atlas.cogentco.com (154.54.84.2) 33.083 ms
9 be2025.ccr22.mia03.atlas.cogentco.com (154.54.47.230) 33.421 ms be3401.ccr21.mia03.atlas.cogentco.com (154.54.47.30) 33.425 ms 33.515 ms
10 38.88.164.98 (38.88.164.98) 32.885 ms 38.142.154.10 (38.142.154.10) 33.026 ms 33.034 ms
11 * * *
12 172.16.9.29 (172.16.9.29) 105.161 ms 105.284 ms 105.265 ms
13 187.110.228.41.mobtelecom.com.br (187.110.228.41) 106.474 ms 106.481 ms 109.289 ms
14 * * *
...(just * * *s)
30 * * *

They both seem to get to Brazil okay, co-incidentally on hop 13 as it happens.

Weird one.

Highlighted
Dabbler
Posts: 10
Thanks: 1
Registered: 4 weeks ago

Re: Router seems to be blocking a single website

Thank you for your help guys. So if I'm correctly following the bouncing ball, the only way I can be sure of connecting to this website is by doing two things - 1) using my computer on a different service provider (now and then I can stay with family who use a BT connection) and 2) making sure TCP/IPv4 uses DNS server address 8.8.8.8

If so, I'll have to report back on that when I can use the different service provider (which could be weeks).

Highlighted
Community Gaffer
Community Gaffer
Posts: 14,508
Thanks: 2,127
Fixes: 148
Registered: ‎04-04-2007

Re: Router seems to be blocking a single website

Fix

@seebee wrote:

For me it looks like a routing issue AND a Plusnet DNS issue!



Doubt it's Plusnet DNS. I run my own Unbound DNS server and I can't resolve the website either, nor it's authoritative name servers. I can TCP trace the underlying IP as far as you can on port 443 which suggests the traffic is reaching (or at least getting close to) its destination.

If you trace the DNS lookup it fails as soon as it hits the gov.br subdomain's name servers:-

~ $ dig +trace www.ibge.gov.br @212.159.6.10

; <<>> DiG 9.11.5-P4-5.1+deb10u1-Raspbian <<>> +trace www.ibge.gov.br @212.159.6              .10
;; global options: +cmd
.                       9340    IN      NS      m.root-servers.net.
.                       9340    IN      NS      b.root-servers.net.
.                       9340    IN      NS      c.root-servers.net.
.                       9340    IN      NS      d.root-servers.net.
.                       9340    IN      NS      e.root-servers.net.
.                       9340    IN      NS      f.root-servers.net.
.                       9340    IN      NS      g.root-servers.net.
.                       9340    IN      NS      h.root-servers.net.
.                       9340    IN      NS      a.root-servers.net.
.                       9340    IN      NS      i.root-servers.net.
.                       9340    IN      NS      j.root-servers.net.
.                       9340    IN      NS      k.root-servers.net.
.                       9340    IN      NS      l.root-servers.net.
.                       9340    IN      RRSIG   NS 8 0 518400 20200727190000 202              00714180000 46594 . p73UQ24ubawllflxpdSXe9rnKAw5zek11+3QwrgZyCv0sOaIYKNaPhju kcf              z1t2IBlAgGyd5oZNAq5b3gvKTfGV7KTaOJHpuVpbWHsdSszkCOnr8 SwwbRxWtRp6dTo8aQsnzBauc9I              Yj+71+xcFFap0m2/Y1snu9t43/Bo/w s1VESJ+4qWW66EjVYdocSn09ZHfjyB19n8diwwjauklnkX89k              w4Jqo2A kTSQ7W7u/8681J1xFn7bVCfJ5H2X6z75t7EvY902JnMOC6A66HOAAm0U 5sVb7YEKd3GY3gZ              QZNS7EplEkzyOostEn4pgZSRUGAdKoxyNjPmUB4og OBL9Sw==
;; Received 525 bytes from 212.159.6.10#53(212.159.6.10) in 7 ms

br.                     172800  IN      NS      a.dns.br.
br.                     172800  IN      NS      b.dns.br.
br.                     172800  IN      NS      c.dns.br.
br.                     172800  IN      NS      d.dns.br.
br.                     172800  IN      NS      e.dns.br.
br.                     172800  IN      NS      f.dns.br.
br.                     86400   IN      DS      2471 13 2 5E4F35998B8F909557FA11              9C4CBFDCA2D660A26F069EF006B403758A 07D1A2E4
br.                     86400   IN      RRSIG   DS 8 1 86400 20200728170000 2020              0715160000 46594 . ma1sn0g6Sreds5ZEMIy0EF+mTdHzV97vDwRubkO9nK/VfsApy6R6sSpj HM+x              zYG5MQAoEvw8hRLndQe4vIzCPFDQGLgS59VIIHybL6CmGalr7S9Q fnMJOl0hLhT4yjAqbz9Ak+vESzX              /Rak5zslkbgjm29Y7vtFTA07QIOiu 7WkmTOXWPrfq04ml+XlfIM9kHCkFtp8wr6o0g8V3bOimk0ejH8              7l8g90 6zx5mt+dw1plE8GAbj6knYI9UfDOBDEdH7q5+MsnaGu3rbk/xxe1RcY1 IrLmlVWuOM6RcGh0              ieTcEfJ2qmRBcpxzd9EoOZBOVcWQgw0fKcon3dbV lBkFaQ==
;; Received 743 bytes from 192.5.5.241#53(f.root-servers.net) in 9 ms

ibge.gov.br.            3600    IN      NS      ns15.ibge.gov.br.
ibge.gov.br.            3600    IN      NS      ns16.ibge.gov.br.
ibge.gov.br.            3600    IN      NS      ns10.ibge.gov.br.
ibge.gov.br.            3600    IN      NS      ns17.ibge.gov.br.
ibge.gov.br.            900     IN      NSEC    ibram.gov.br. NS RRSIG NSEC
ibge.gov.br.            900     IN      RRSIG   NSEC 13 3 900 20200728120056 202              00714110056 2486 gov.br. 3LwRLmGatH+YPnTKu9BkraTKwwIFTDjw6Cs2lKQqnV1QCkw2CgSxDR9              x i2Y86hCDhcyTyfdI9Wt2JLeCKoDO5g==
couldn't get address for 'ns15.ibge.gov.br': failure
couldn't get address for 'ns16.ibge.gov.br': failure
couldn't get address for 'ns10.ibge.gov.br': failure
couldn't get address for 'ns17.ibge.gov.br': failure
dig: couldn't get address for 'ns15.ibge.gov.br': no more

 
It looks like whoever owns these IP's either doesn't want Plusnet traffic hitting them, or somebody is advertising something incorrectly. 

Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵

Highlighted
Dabbler
Posts: 10
Thanks: 1
Registered: 4 weeks ago

Re: Router seems to be blocking a single website

OK thanks. It's strange as I have been accessing the website on and off since 2008 and I have been with Plusnet most of that time. I don't have a solution but it seems there isn't a feasible solution.

Highlighted
Hooked
Posts: 8
Thanks: 4
Fixes: 1
Registered: ‎08-07-2017

Re: Router seems to be blocking a single website


@bobpullen wrote:
It looks like whoever owns these IP's either doesn't want Plusnet traffic hitting them, or somebody is advertising something incorrectly. 

Ah yes - so the DNS "issue" is just a side effect of (some?) Plusnet addresses being unable to talk to those Brazil ones? The normal Plusnet DNS servers are in a range that can't talk to them, however the Safeguard Plusnet servers are in BTs range and do happen to be able to (like the public servers too)?

Highlighted
Community Gaffer
Community Gaffer
Posts: 14,508
Thanks: 2,127
Fixes: 148
Registered: ‎04-04-2007

Re: Router seems to be blocking a single website

@seebee certainly seems that way. My Unbound server (whilst nothing to do with Plusnet DNS) will still be seen as coming from a Plusnet IP/traversing the Plusnet broadband network.

Seems this is the person responsible for the 170.84.40.0/22 netblock:-

 

person: José Luiz Thomaselli Nogueira
e-mail: SICIBGE@ibge.gov.br

 

Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵