You can make a reverse DNS record (or any DNS record, for that matter,) say anything at all. There isn't a National Committee for the Verification of DNS Updates checking this stuff out and demanding in-person inspections and notarized affidavits swearing that 100% of all information in the DNS is accurate and means whatever the end-user might infer it to mean.
For instance, part of the tracroute from my house to Google looks like this:
6 be-33112-cs01.doraville.ga.ibone.comcast.net (96.110.43.81) 19.602 ms
7 be-33142-cs04.doraville.ga.ibone.comcast.net (96.110.43.93) 22.738 ms
8 be-302-cr13.56marietta.ga.ibone.comcast.net (96.110.39.49) 23.202 ms
You can see these hostnames are obviously meant to encode some geographic data -- strictly for the convenience of the provider, it doesn't mean anything else -- but you, as the user, cannot tell from these records that these routers are actually where you think they are, based on the host names.
Another issue is the server you're communicating with might take a completely different path to get back to you, and you'd have no real way of knowing that.
For instance, part of the tracroute from my house to Google looks like this:
6 be-33112-cs01.doraville.ga.ibone.comcast.net (96.110.43.81) 19.602 ms
7 be-33142-cs04.doraville.ga.ibone.comcast.net (96.110.43.93) 22.738 ms
8 be-302-cr13.56marietta.ga.ibone.comcast.net (96.110.39.49) 23.202 ms
You can see these hostnames are obviously meant to encode some geographic data -- strictly for the convenience of the provider, it doesn't mean anything else -- but you, as the user, cannot tell from these records that these routers are actually where you think they are, based on the host names.
Another issue is the server you're communicating with might take a completely different path to get back to you, and you'd have no real way of knowing that.