Strange trace results from router

tahequivoice — Tue, 05 Mar 2019 08:05:04 GMT

When doing a traceroute on a 2900, I am seeing returns of the destination IP instead of the real internet IP.

#trace 4.2.2.1 sou g0/0.102
Type escape sequence to abort.
Tracing the route to 4.2.2.1
VRF info: (vrf in name/id, vrf out name/id)
1 10.100.102.85 [AS ] 0 msec 0 msec 4 msec
2 10.255.255.30 [AS ] 0 msec 4 msec 0 msec
3 4.2.2.1 [AS ] 0 msec 4 msec 0 msec
4 4.2.2.1 [AS ] 4 msec 0 msec 4 msec
5 4.2.2.1 [AS ] 0 msec 4 msec 0 msec
6 4.2.2.1 [AS ] 0 msec 4 msec 0 msec
7 4.2.2.1 [AS ] 4 msec 4 msec 4 msec
8 * * *
9 4.2.2.1 [AS ] 0 msec 4 msec 0 msec
10 * * *
11 4.2.2.1 [AS ] 0 msec 0 msec 0 msec

If I enable DNS lookup, the IP is replaced with the domain name used such as yahoo.com or google.

#trace 8.8.8.8 sou g0/0.102
Type escape sequence to abort.
Tracing the route to google-public-dns-a.google.com (8.8.8.8)
VRF info: (vrf in name/id, vrf out name/id)
1 10.100.102.85 [AS ] 20 msec 20 msec 8 msec
2 10.255.255.30 [AS ] 4 msec 4 msec 16 msec
3 google-public-dns-a.google.com (8.8.8.8) [AS ] 28 msec 32 msec 32 msec
4 google-public-dns-a.google.com (8.8.8.8) [AS ] 28 msec 24 msec 36 msec
5 google-public-dns-a.google.com (8.8.8.8) [AS ] 28 msec 16 msec 12 msec
6 google-public-dns-a.google.com (8.8.8.8) [AS ] 12 msec 8 msec 24 msec
7 google-public-dns-a.google.com (8.8.8.8) [AS ] 24 msec 20 msec 24 msec
8 google-public-dns-a.google.com (8.8.8.8) [AS ] 40 msec 24 msec 16 msec
9 google-public-dns-a.google.com (8.8.8.8) [AS ] 16 msec 24 msec 20 msec
10 google-public-dns-a.google.com (8.8.8.8) [AS ] 24 msec 16 msec 16 msec
11 google-public-dns-a.google.com (8.8.8.8) [AS ] 16 msec 16 msec 20 msec
12 google-public-dns-a.google.com (8.8.8.8) [AS ] 48 msec 12 msec 16 msec
13 google-public-dns-a.google.com (8.8.8.8) [AS ] 32 msec 32 msec 36 msec
14 * * *
15 google-public-dns-a.google.com (8.8.8.8) [AS ] 24 msec 28 msec 28 msec

I am also seeing our ASN in the trace.

I have never seen this before on any router, switch or PC. What could be causing this? If a client behind the router does a trace, they get *** for each hop beyond #2 which is the firewall until the final destination.

tema Strange trace results from router en Routing

Strange trace results from router