I have not been able to get onto the dontronics web site for the last four or five days, cannot find an email address in some of Don's replies as it seems linked to the web site Contacted my ISP so if you are watching Don ?? the reply I received from them is below. cheers Cam.
Thank you for your online support request.
I am able to view the website you reported OK down this end. I believe the problem you are experiencing is part of a larger problem Internode has encountered over recent months.
The problem affects customers who are on a particular IP address range with Internode. This is not a problem with Internode itself but with the particular websites.
Internode has an advisory on our website about the issue:
formatting link
I will add this support request to the others that we are currently looking into and hopefully we will be able to get this website to change its configuration to ensure its correct functionality.
Cam, here is the immediate answer I got back from my web host.
=======================================
Don McKenzie wrote: Some customers experiencing issues with some websites
Don,
The problem seems to be on there end not ours, what you are going to have to do is get your customer to get his ISP to assign him a new IP address.
Regards,
Adam Regards,
Adam
Ticket ID: KMF-70479 Tracking URL: Click Here Department: AffordableHost - Support Created On: 12 May 2005 05:38 PM Last Update: 12 May 2005 05:38 PM Status: Closed
--
Don McKenzie
E-Mail Contact Page: http://www.e-dotcom.com/ecp.php?un=Dontronics
Some ISPs are major sources of spam, spew, or virus-spreading zombies and refuse to clean up their act. Because of this they find that the IP addresses they use get blocked by other nodes on the Net. Non-spamming customers of that ISP get blocked as well.
This is good news! If the ISP's that permit spamming are getting blocked we may see a slowdown (I am not naive enough to think it is the end) of Spam. It is a pity more direct, and faster, action can not be taken. Apparently the majority of it emanates from Florida though I seem to get a fair bit from Russia.
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ \/\/\/\/\ Chris Hills Staffs England /\/\/\/\/\ /\/\/ snipped-for-privacy@phaedsys.org
This is a problem, too. The ISP's blocking address ranges seem to block also supposedly unused address ranges (e.g. 85.x.y.z). This killed my new (and totally respectable IP) from some routers. I had to VPN to my other site with an 80.x.y.z-series address to get ny the blocking.
The blockers should have a clue before doing anything radical.
I agree. A very extreme example is Verizon. They seem to block all traffic from Europe. It happened quite a few times that a customer from the USA sent me an e-mail with a support question regarding our products and I couldn't answer him because he was with Verizon. Every reply bounced.
That's what is happening when I try to email Don by replying to his direct email. No joy on this one. I still cannot connect. If you read this Don could you get your ISP to read the information in the link I originally posted, and if possible talk to Internode.
Cam, I have sent you a message with a clean email reply address that doesn't go through the system, so you can communicate directly with me.
Can you try what Neil suggests above?
Unfortunately, blocking IP addresses isn't the way to get rid of spam.
I am also waiting on a response from my message to my web host below:
Don...
Web Host Ticket message: ====================================
Hi Adam, as this thread was started and is still running in a newsgroup, can you please clarify for me if you are blocking 58.0.0.0/8 and/or 59.0.0.0/8.
If you are not, then why would the customer need a new IP address?
If you are, can you please explain why you are blocking it.
Thanks in advance, Cheers Don...
--
Don McKenzie
E-Mail Contact Page: http://www.e-dotcom.com/ecp.php?un=Dontronics
Here are the results. I'm not 100% sure on how to interpret them, but doing an nslookup on the last IP addr in the output just seems to state the obvious. I guess when your blocked, that's it ?
e:\embedded\bin>tracert dontronics.com
Tracing route to dontronics.com [209.9.226.66] over a maximum of 30 hops:
1 * ** Request timed out. 2 17 ms 20 ms 20 ms loop0.lns1.mel2.internode.on.net [150.101.212.16] 3 19 ms 20 ms 19 ms gi0-1-3.cor2.mel2.agile.on.net [150.101.212.115] 4 20 ms 20 ms 27 ms gi2-4.cor1.mel3.internode.on.net [150.101.212.162] 5 30 ms 34 ms 32 ms pos1-2.bdr1.syd6.agile.on.net [203.16.212.237] 6 205 ms 206 ms 206 ms pos1-0.bdr1.lax1.agile.on.net [203.16.213.149] 7 198 ms 197 ms 198 ms GigabitEthernet3-2.GW1.LAX15.ALTER.NET [208.222.8.93] 8 205 ms 206 ms 206 ms 0.so-2-0-0.CL1.LAX15.ALTER.NET [152.63.115.210] 9 197 ms 198 ms 199 ms 0.so-4-1-0.XL1.LAX7.ALTER.NET [152.63.117.118] 10 199 ms 199 ms 199 ms 0.so-6-1-0.BR1.LAX7.ALTER.NET [152.63.113.1] 11 209 ms 206 ms 207 ms 204.255.168.30 12 208 ms 208 ms 207 ms tbr2-p012101.la2ca.ip.att.net [12.123.29.6] 13 249 ms 247 ms 249 ms tbr2-cl2.sl9mo.ip.att.net [12.122.10.13] 14 252 ms 249 ms 251 ms tbr1-cl2.sl9mo.ip.att.net [12.122.9.141] 15 266 ms 264 ms 267 ms tbr1-cl4.wswdc.ip.att.net [12.122.10.29] 16 260 ms 259 ms 257 ms gar1-p300.ascva.ip.att.net [12.123.8.49] 17 267 ms 270 ms 265 ms att-peer.er1.iad1.ptptech.net [209.9.224.154] 18 ** * Request timed out. ........... 30 * * * Request timed out.
YOU > 16 gar1-p300.ascva.ip.att.net [12.123.8.49] ME | 10 gar1-p300.ascva.ip.att.net [12.123.8.49]
YOU > 17 att-peer.er1.iad1.ptptech.net [209.9.224.154] ME | 11 att-peer.er1.iad1.ptptech.net [209.9.224.154]
YOU > 18 Request timed out. ME | 12 titan.genwebhost.com [209.9.226.66]
So why can I get from 209.9.224.154 to 209.9.226.66 and you can't?
Would you be so kind as to ping 209.9.224.154 and 209.9.226.66 and report the results?
Lets look at possible blocking:
Your NNTP-Posting-Host is 59.167.68.200, which is ppp68-200.lns1.mel2.internode.on.net. I am assuming that this is #1 on your tracert.
#2 on your tracert is 150.101.212.16, which is loop0.lns1.mel2.internode.on.net
Let's look at them all at
formatting link
150.101.212.16 not listed in bl.spamcop.net
150.101.212.16 not listed in dnsbl.njabl.org
150.101.212.16 not listed in dnsbl.njabl.org
150.101.212.16 not listed in cbl.abuseat.org
150.101.212.16 not listed in dnsbl.sorbs.net
150.101.212.16 not listed in relays.ordb.org.
59.167.68.200 not listed in bl.spamcop.net
59.167.68.200 not listed in dnsbl.njabl.org
59.167.68.200 not listed in dnsbl.njabl.org
59.167.68.200 not listed in cbl.abuseat.org
59.167.68.200 not listed in dnsbl.sorbs.net
59.167.68.200 not listed in relays.ordb.org.
209.9.224.154 not listed in bl.spamcop.net
209.9.224.154 not listed in dnsbl.njabl.org
209.9.224.154 not listed in dnsbl.njabl.org
209.9.224.154 not listed in cbl.abuseat.org
209.9.224.154 not listed in dnsbl.sorbs.net
209.9.224.154 not listed in relays.ordb.org.
209.9.226.66 not listed in bl.spamcop.net
209.9.226.66 not listed in dnsbl.njabl.org
209.9.226.66 not listed in dnsbl.njabl.org
209.9.226.66 not listed in cbl.abuseat.org
209.9.226.66 not listed in dnsbl.sorbs.net
209.9.226.66 not listed in relays.ordb.org.
OK, so nobody on either end is on a common block list.
Route tracing seems not be reliable here. My traceroute (from Linux, Windows and OSX) get killed at att-peer.er1.iad1.ptptech.net, but pings and web accesses to dontronics.com do work.
Tracing route to dontronics.com [209.9.226.66] over a maximum of 30 hops:
1 * ** Request timed out. 2 17 ms 20 ms 20 ms loop0.lns1.mel2.internode.on.net [150.101.212.16] 3 19 ms 20 ms 19 ms gi0-1-3.cor2.mel2.agile.on.net [150.101.212.115] 4 20 ms 20 ms 27 ms gi2-4.cor1.mel3.internode.on.net [150.101.212.162] 5 30 ms 34 ms 32 ms pos1-2.bdr1.syd6.agile.on.net [203.16.212.237] 6 205 ms 206 ms 206 ms pos1-0.bdr1.lax1.agile.on.net [203.16.213.149] 7 198 ms 197 ms 198 ms GigabitEthernet3-2.GW1.LAX15.ALTER.NET [208.222.8.93] 8 205 ms 206 ms 206 ms 0.so-2-0-0.CL1.LAX15.ALTER.NET [152.63.115.210] 9 197 ms 198 ms 199 ms 0.so-4-1-0.XL1.LAX7.ALTER.NET [152.63.117.118] 10 199 ms 199 ms 199 ms 0.so-6-1-0.BR1.LAX7.ALTER.NET [152.63.113.1] 11 209 ms 206 ms 207 ms 204.255.168.30 12 208 ms 208 ms 207 ms tbr2-p012101.la2ca.ip.att.net [12.123.29.6] 13 249 ms 247 ms 249 ms tbr2-cl2.sl9mo.ip.att.net [12.122.10.13] 14 252 ms 249 ms 251 ms tbr1-cl2.sl9mo.ip.att.net [12.122.9.141] 15 266 ms 264 ms 267 ms tbr1-cl4.wswdc.ip.att.net [12.122.10.29] 16 260 ms 259 ms 257 ms gar1-p300.ascva.ip.att.net [12.123.8.49] 17 267 ms 270 ms 265 ms att-peer.er1.iad1.ptptech.net [209.9.224.154] 18 ** * Request timed out. ........... 30 * * * Request timed out.
Trace complete.
--
Don McKenzie
E-Mail Contact Page: http://www.e-dotcom.com/ecp.php?un=Dontronics
Reply from 209.9.224.154: bytes=32 time=262ms TTL=246 Reply from 209.9.224.154: bytes=32 time=260ms TTL=246 Reply from 209.9.224.154: bytes=32 time=260ms TTL=246 Reply from 209.9.224.154: bytes=32 time=260ms TTL=246
Ping statistics for 209.9.224.154: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 260ms, Maximum = 262ms, Average = 260ms
Ping statistics for 209.9.226.66: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
I can ping both, so we know they both respond to pings. Looks like 209.9.226.66 is blocking you and not me.
That's all we can do from here; now it is up to Don's ISP.
BTW, I have had my employer purchase many dontronics products and my experience has been that they sit there quietly doing what they were designed to do without ever giving you any trouble. (My only connection to dontronics is as a happy customer).
OK, I have their full attention now Cam, so we may get a resolution. Latest ticket text from my web host below: Check your IP address as Jeff has indicated below, and I will pass it on.
See how we go from there.
Don...
=============================================================== Some customers experiencing issues with some websites
Don,
I have seen this issue on one other hosting server within the system.
This may be related to a resolution problem between the ISP connection and the server. Please provide the IP address that is experiencing the issue and I will attempt to research the connectivity between the connection and the server.
Please have those affected by this issue visit the following page to retrieve their IP address.
formatting link
Thanks
Jeff
If you have any further questions, please do not hesitate to ask.
Thanks, Jeff
--
Don McKenzie
E-Mail Contact Page: http://www.e-dotcom.com/ecp.php?un=Dontronics
Got a big message from Cam's ISP, which I also happen to have 2 individual accounts with.
This is the short version, but it defines the problem:
=================================================== We've recently received an allocation of IPv4 address space from APNIC which has been drawn from 59.0.0.0/8, which was previously marked by IANA as "reserved".
IANA redesignated it (along with 58.0.0.0/8) nearly a year ago. Nevertheless, we're finding that a number of network operators have continued to block those addresses in their bogon filters. ===================================================
I now have an email address for Cam's ISP, I have to link this up with my web host, so we don't have to go through the web form ticket system. This may be a feat in itself. :-)
Of course, spam destroyed the ability for web hosts to communicate readily with each other. :-(
Don...
--
Don McKenzie
E-Mail Contact Page: http://www.e-dotcom.com/ecp.php?un=Dontronics
============================================== From my web host: I have cleared the IP address and block setting from the bogon filters within the hosting server, please let me know if this does not correct the issue. ==============================================
and it only took 6 days to convince them that they were wrong. all working now.
Don...
D> Cam wrote:
--
Don McKenzie
E-Mail Contact Page: http://www.e-dotcom.com/ecp.php?un=Dontronics
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.