5 ms·
This sort of endearing Internet-scale thing reminds me of how NTT changes their reverse DNS's (https://mailman.nanog.org/pipermail/nanog/2016-February/084128.ht
by zkms 9y ago
This sort of endearing Internet-scale thing reminds me of how NTT changes their reverse DNS's (https://mailman.nanog.org/pipermail/nanog/2016-February/084128.html https://mailman.nanog.org/pipermail/nanog/2016-February/0841...). There's other vanity reverse-DNS tricks that you can see in traceroutes, but this is done with a global-scale IPv4/IPv6 network that actually is carrying a lot of customer traffic. Try "traceroute ntt.net" now, you'll see hops like:
9 ae-19.sayonara-todd.r04.sttlwa01.us.bb.gin.ntt.net (129.250.66.57) 17.225 ms 17.166 ms 17.171 ms
10 ae-5.sayonara-todd.r21.sttlwa01.us.bb.gin.ntt.net (129.250.2.7) 16.257 ms 16.156 ms 16.101 ms
11 ae-3.sayonara-todd.r23.snjsca04.us.bb.gin.ntt.net (129.250.3.124) 33.097 ms 33.125 ms 31.566 ms
12 ae-7.sayonara-todd.r23.dllstx09.us.bb.gin.ntt.net (129.250.4.155) 69.840 ms 69.764 ms 69.763 ms
13 ae-6.sayonara-todd.r10.dllstx09.us.bb.gin.ntt.net (129.250.5.4) 69.634 ms 74.424 ms 72.319 ms
14 ae-0.sayonara-todd.a01.dllstx09.us.bb.gin.ntt.net (129.250.3.244) 74.050 ms 74.046 ms 74.035 ms
or
3 ae-13.sayonara-todd.r05.plalca01.us.bb.gin.ntt.net (2001:418:0:5000::bae) 1.324 ms 1.307 ms 1.205 ms
4 ae-15.sayonara-todd.r02.snjsca04.us.bb.gin.ntt.net (2001:418:0:2000::172) 2.505 ms
5 ae-10.sayonara-todd.r23.snjsca04.us.bb.gin.ntt.net (2001:418:0:2000::cd) 2.091 ms 2.067 ms
6 ae-7.sayonara-todd.r23.dllstx09.us.bb.gin.ntt.net (2001:418:0:2000::1fa) 38.386 ms 39.757 ms 38.312 ms
7 ae-6.sayonara-todd.r10.dllstx09.us.bb.gin.ntt.net (2001:418:0:2000::1c1) 41.586 ms
8 ae-1.sayonara-todd.a02.dllstx09.us.bb.gin.ntt.net (2001:418:0:2000::135) 51.986 ms
- tbodt 9y agotraceroute bad.horse
- shmageggy 9y agoI needed `-m 50` to get it all
- loeg 9y agoWhat about those domains says vanity reverse DNS to you? They look like bog standard location-named routers to me.
- stedaniels 9y ago"Sayonara Todd" ... Goodbye Todd
- loeg 9y agoWho is Todd?
- vertex-four 9y agoClick the mailman link - Todd will be an engineer who left the company.
- broknbottle 9y agoSayonara Todd
- job 9y agoIt might amuse you to know the same NTT people are behind the BGP Nyancat :-)
- mcescalante 9y agoI am amazed/fascinated by this! I would love to hear more for all the non-experts here about how the BGP Nyancat came to be :)
- job 9y agoThe starting point is a BMP file of the Nyan cat which is read into a simple two dimensional array by a small python script. The script looks at the current time and maps that to a column of pixels in the BMP. Each row of pixels in the BMP is represented by one IPv4 /24. If the pixel is "on" a BGP route announcement is generated, if the pixel is "off" the route is withdrawn. Each pixel in the BMP file represents 8 hours of announcing.
- dsl 9y agoI'm curious how you handled the justification for the IP space to pull this off. ;)
- pas 9y agoThe prefixes are probably announced in aggregated form anyhow further upstream. The announcements and deannouncements are/were therefore redundant. At least't that's my hunch. We could check the same monitor though :)
- jgg7 9y agoAS15562 appears to be an employee of NTT out of the Netherlands. I can't tell if AS15562 is for personal or work, maybe both: http://bgp.he.net/AS15562 http://bgp.he.net/AS15562 I couldn't care less about the IPv6 prefixes, but the IPv4 ones are all /24s made from 209.24.0.0/16, which is registered to NTT (AS2914). 209.24/16 is publicly announced (and has been for a very long time), and is routed through NTT Amsterdam routers. I haven't looked at BGPlay to review all the data, but it looks like many of the /24s that make up that /16 were individually announced through AS15562, then later withdrawn, gradually over 4 months, to make said graph. I would hope this would be unused v4 space. That AS announced almost 98% of a /16 (probably 209.24/16): https://stat.ripe.net/AS15562#tabId=routing https://stat.ripe.net/AS15562#tabId=routing Another user voiced their concerns, particularly if it was actively used: https://news.ycombinator.com/item?id=14621859 https://news.ycombinator.com/item?id=14621859 -- there's no way any of us could know this; NTT would be authoritative, and jwhois -h rwhois.gtt.net.net -p 4321 209.24.0.0/16 doesn't give any clues. While the antic made me smirk, it doesn't (publicly) "look good" when we're living in a world that lacks (or has greatly limited) v4 space. What this says is: "NTT has a /16 they're fooling around with publicly", even though it (presumably) is harmless.
- job 9y agoOn April 1st 2015 I tried to create new poems by remixing an existing body of work through reverse DNS: https://bandaancha.eu/foros/april-fools-ntt-1717230 https://bandaancha.eu/foros/april-fools-ntt-1717230 - the original was better perhaps ;-)
- zkms 9y agoI like it a lot. There's something quite endearing about seeing human-legible text (beyond city names / interface names) in reverse DNS.