Posted: Mon Mar 01, 2021 13:27 Post subject: Can't reach specific website [SOLVED]
The wife uses mealplannerpro.com, and over a week now we're unable to reach the site from our internet connection. If I use the data plan on my phone, it works. If I go to a neighbor on AT&T (I'm on Comcast), it works. I even tried a customer's PC who is also on Comcast. I've restarted the modem, router, our PCs, even tried a VM. If I use a proxy, it works. I've tried http://,https://, with www, without www. I've made sure the site isn't blocked in dd-wrt; I have no sites blocked.
Here's the tracert from my network, where I can not access the site:
Tracing route to mealplannerpro.com [52.35.236.159]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms DD-WRT [10.0.0.2]
2 10 ms 12 ms 8 ms 96.120.97.229
3 14 ms 9 ms 9 ms 96.110.139.177
4 19 ms 11 ms 9 ms 68.87.162.81
5 9 ms 8 ms 9 ms 69.139.181.169
6 14 ms 10 ms 10 ms 69.139.181.37
7 15 ms 12 ms 16 ms be-20214-cr02.miami.fl.ibone.comcast.net [68.86.90.205]
8 38 ms 38 ms 38 ms be-301-cr14.houston.tx.ibone.comcast.net [96.110.39.233]
9 38 ms 48 ms 38 ms be-1214-cs02.houston.tx.ibone.comcast.net [96.110.46.125]
10 38 ms 38 ms 37 ms be-1211-cr11.houston.tx.ibone.comcast.net [96.110.46.114]
11 43 ms 42 ms 45 ms be-311-cr02.dallas.tx.ibone.comcast.net [96.110.36.170]
12 56 ms 56 ms 56 ms be-303-cr12.1601milehigh.co.ibone.comcast.net [96.110.38.105]
13 56 ms 56 ms 58 ms be-1212-cs02.1601milehigh.co.ibone.comcast.net [96.110.39.85]
14 54 ms 55 ms 55 ms be-3202-pe02.910fifteenth.co.ibone.comcast.net [96.110.38.118]
15 76 ms 55 ms 55 ms 23.30.206.238
16 * * * Request timed out.
All requests from there timed out.
Here's the tracert from my customer's Comcast net that can access the site:
Tracing route to mealplannerpro.com [52.35.236.159]
over a maximum of 30 hops:
1 2 ms 1 ms 2 ms 10.1.10.1
2 12 ms 10 ms 10 ms 96.120.97.197
3 8 ms 9 ms 8 ms 68.85.228.193
4 12 ms 10 ms 10 ms be-106-ar01.northdade.fl.pompano.comcast.net [69.139.182.105]
5 13 ms 13 ms 15 ms be-20214-cr02.miami.fl.ibone.comcast.net [68.86.90.205]
6 38 ms 37 ms 38 ms be-302-cr14.houston.tx.ibone.comcast.net [96.110.39.237]
7 39 ms 39 ms 40 ms be-1314-cs03.houston.tx.ibone.comcast.net [96.110.46.141]
8 38 ms 38 ms 41 ms be-1311-cr11.houston.tx.ibone.comcast.net [96.110.46.130]
9 44 ms 45 ms 42 ms be-311-cr02.dallas.tx.ibone.comcast.net [96.110.36.170]
10 57 ms 56 ms 57 ms be-301-cr12.1601milehigh.co.ibone.comcast.net [96.110.38.97]
11 60 ms 56 ms 56 ms be-1212-cs02.1601milehigh.co.ibone.comcast.net [96.110.39.85]
12 60 ms 55 ms 58 ms be-3202-pe02.910fifteenth.co.ibone.comcast.net [96.110.38.118]
13 62 ms 74 ms 56 ms as8075-1-c.111eighthave.ny.ibone.comcast.net [173.167.59.118]
14 * * * Request timed out.
And a trace from a neighbor's AT&T connection that can access the site:
Tracing route to mealplannerpro.com [52.35.236.159]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms homeportal [192.168.1.254]
2 18 ms 22 ms 19 ms 99-123-204-1.lightspeed.miamfl.sbcglobal.net [99.123.204.1]
3 18 ms 18 ms 18 ms 99.167.38.50
4 77 ms 78 ms 78 ms 12.240.210.90
5 81 ms 78 ms 78 ms cr2.ormfl.ip.att.net [12.123.6.50]
6 82 ms 78 ms 78 ms ormfl21crs.ip.att.net [12.122.5.185]
7 77 ms 78 ms 79 ms 12.122.28.149
8 80 ms 78 ms 79 ms 12.122.2.197
9 76 ms 78 ms 78 ms dlstx22crs.ip.att.net [12.122.1.210]
10 77 ms 78 ms 78 ms la2ca22crs.ip.att.net [12.122.2.82]
11 75 ms 75 ms 75 ms gar5.la2ca.ip.att.net [12.122.128.25]
12 74 ms 73 ms 73 ms 12.245.156.58
13 * * * Request timed out.
So I get it that there can be routing issues, it happens, but why would it only affect my internet connection? That I can get my head around.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Mon Mar 01, 2021 13:48 Post subject:
Are you using your ISP-provided dns servers or? That's the only thing I can think of that may be an issue, outside of a routing issue. I have no issue here getting to the site, but I only got 7 hops in before requests timing out. That may be by design, though. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Thanks for the replies. I should noted I'm using Google's DNS. Though as a test I manually used 1.1.1.1 and got the same result. Since the domain resolved to the same IP address as my other tests, I figured it wasn't DNS.
We could be blacklisted for some reason! Not sure why.. or how I'd find out.
No Wireguard, but as I mentioned it does work using a VPN.
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Tue Mar 02, 2021 14:19 Post subject:
Well, I found nothing that specifies specific dns servers, save and except to enable dns over https/tls, and I have a dns override on my ISP equipment to use OpenDNS. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Other than resolving for mealplannerpro.com, does my local DNS have anything else to do with reaching the site? I always assumed it just resolved for the destination, and nothing in between.
I've tried it with and without the secure DNS in Firefox and Edge. Same problem still.
Oh I'm sure it's not a dd-wrt issue. But I knew this was the place to ask about the problem!
And yes, I just emailed them to see if that does any good. I guess I expected to receive some kind of message or indication that our IP address has been blocked.
Maybe Comcast can give me a new IP address? I sort of dread having to call them.
Just a follow up. I used the option in dd-wrt to clone my PC's MAC address to the router after unplugging my modem. I restarted the router, plugged in the modem, and I got a new IP address from Comcast. And now I can reach the website.