Could be the radio, could just be marginal alignment -- the antenna is highly directional. Regardless, if it isn't yours, you want to have the provider take a look. I highly doubt any provider would let you get access to the admin UI for a tower or any other part of their network, so the fact that you can bring up a login screen is another strong indication that you are seeing the rooftop radio at 10.0.0.1.
The whole DNS thing basically boils down to the fact that, unless you run your own private DNS server on your personal LAN, any DNS operation has to contact a server on the Internet (read on the other side of the air hops). So, when things are not well, this: 1) isn't going to work; 2) is going to incur a large delay as the system waits for the response that is never coming.
The radio could be doing a number of things: routing, bridging, NAT, etc. The main point here is things are going wrong inside your provider's network. If they let you access the admin UI for the radio, you could probably tell a whole lot more. If there's an option to use your own radio, it might not be the worst way to go. If someone comes out to service your radio, maybe they will leave you with the login info (doubtful, but one never knows). They should be able to check the signal strength from their network and may know your signal isn't great or be able to check when you are on the phone. If any of this doesn't make sense, let me know...
I assume you tried ubnt/ubnt to log into the radio? Did the utility tell you anything?
Here's something on layer 2 (bridge) tracert: <
http://www.fragmentationneeded.net/2...raceroute.html>. A bridge will typically have a layer 3 IP address, but it doesn't follow that it is going to show up in tracert.
If you are using Windows, try the pathping command -- it is more informative than tracert and possibly somewhat less confusing.