Yea, FiOS has a lot of incorrect RDNS entries, you learn not to trust them. (I know, folks always point out that it could be the other side of a different connection on the same router, but I’d still call that a misconfiguration). Matt
On Sep 10, 2024, at 17:21, Neel Chauhan <neel@neelc.org> wrote: Hi,
I got Fios installed today in my NYC apartment, as I just moved back from Seattle after a 4-month stay in Connecticut.
When doing a traceroute, I am noticing an incorrect Reverse DNS entry:
[root@twin ~]# traceroute 1.1.1.1 traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets 1 _gateway (172.20.0.1) 0.145 ms 0.115 ms 0.106 ms 2 lo0-100.NYCMNY-VFTTP-372.verizon-gni.net (173.56.84.1) 2.079 ms 2.070 ms 2.061 ms 3 G0-3-4-4.PITBPA-LCR-21.verizon-gni.net (100.41.196.252) 3.751 ms T0-8-0-9.BSTNMA-LCR-21.verizon-gni.net (100.41.196.248) 4.454 ms 4.447 ms 4 * * * 5 * * * 6 162.158.61.113 (162.158.61.113) 7.246 ms 6.603 ms 162.158.61.117 (162.158.61.117) 4.944 ms 7 one.one.one.one (1.1.1.1) 6.077 ms 6.355 ms 6.346 ms [root@twin ~]#
In short, hop 3 is "G0-3-4-4.PITBPA-LCR-21.verizon-gni.net (100.41.196.252)" which seems to be a Pittsburgh, PA reverse DNS entry even when I'm in NYC. While it doesn't affect the normal operation of the service, it might give the impression packets are being routed via Pittsburgh to someone less savvy.
If someone works at the Verizon Fios/ILEC network engineering or sysadmin team could the 100.41.196.252 reverse DNS entry to say "G0-3-4-4.NYCMNY-LCR-21.verizon-gni.net" please get updated?
Thanks!
Neel Chauhan