belvdr said:You are absolutely correct about the cable modem being a bridge. It's not a router at all.
Counting the hops may or may not be 2 or 3. My guess is it may be more, as most networks aren't flat. Test it with traceroute. For example, on Windows:
tracert -d ns1.yourisp.com
Most Unix, and I think OS X:
tracroute -d ns1.yourisp.com
It will count out the number of hops for you. In addition, if the packet spends any lengthy time at one hop, you'll definitely see where the problem lies.
EDIT: Here's the output from mine. Notice the line with asterisks (*) and "Request timed out". That's nothing to worry about here. It simply means ICMP packets are being dropped and we're not getting a response. If the numbers are extremely high, say 2 or 3 seconds (not ms), then that's your issue:
Code:C:\>tracert -d 216.68.4.10 Tracing route to 216.68.4.10 over a maximum of 30 hops 1 1 ms 1 ms 1 ms 192.168.1.1 2 8 ms 7 ms 7 ms 10.236.238.1 3 8 ms 9 ms 8 ms 216.68.54.92 4 * * * Request timed out. 5 8 ms 7 ms 8 ms 216.68.4.10
I should've been more clear, I was talking about the numbers of times the DNS request was getting forwarded, and I referred to it as hops.