Re: 10.0.0.1 IP address resolving when it shouldn't

Yes, it looks like they are now aware of the issue and working on whatever the cause. I am right across the creek from them. 40 min drive, probably 15 minute flight.:smileylol:

It looks like the information I sent last night made it to someone. At least Verizon Business is blocking the route, and now Verizon Online must take the lead. It does look like the issue is being worked, The buck now stops at Verizon Online. The business end must have seen it and said, what the....

Oh well, funny that it was spotted al all. That used to show as my PPPoE default gateway. I suspect changes are in the works for something. I am DHCP since changing my service.

C:\Windows\system32>tracert 10.0.0.1

Tracing route to 10.0.0.1 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  moat.localdomain [x.x.x.x]
  2     2 ms     1 ms     1 ms  L100.WASHDC-VFTTP-69.verizon-gni.net [x.x.x.x]
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *     G0-9-2-5.WASHDC-LCR-22.verizon-gni.net [130.81.105.164]  reports: Destination net unreachable.

Trace complete.

C:\Windows\system32>