Just looked at j root in detail. Unfortunately not much of traffic is going to J root. BSNL along with its main upstream providers Tata & Airtel - all picking outside routes. Tata AS4755 is taking directly to AS6453 while AS6453 is passing to NTT in London which is next taking back to Japan and then going to HK anycasted node (yeah head shake routing!). Here's a view: traceroute to j.gtld-servers.net (192.48.79.30), 30 hops max, 60 byte packets 1 router.local (192.168.1.1) [AS8151/AS28513] 1.180 ms 1.621 ms 2.121 ms 2 117.207.48.1 (117.207.48.1) [AS9829] 26.935 ms 29.328 ms 31.956 ms 3 218.248.173.46 (218.248.173.46) [AS9829] 34.393 ms 37.093 ms * 4 115.114.57.165.static-Mumbai.vsnl.net.in<http://115.114.57.165.static-mumbai.vsnl.net.in/> (115.114.57.165) [AS4755] 74.623 ms 78.281 ms 82.352 ms 5 if-0-100.tcore2.MLV-Mumbai.as6453.net (180.87.39.25) [*] 299.987 ms 300.397 ms 314.175 ms 6 if-6-2.tcore1.L78-London.as6453.net (80.231.130.5) [AS6453] 314.573 ms 264.576 ms 261.030 ms 7 Vlan704.icore1.LDN-London.as6453.net<http://vlan704.icore1.ldn-london.as6453.net/> (80.231.130.10) [AS6453] 279.896 ms 280.312 ms * 8 Vlan522.icore1.LDN-London.as6453.net<http://vlan522.icore1.ldn-london.as6453.net/> (195.219.83.22) [AS6453] 333.651 ms 326.233 ms 330.307 ms 9 ae-4.r23.londen03.uk.bb.gin.ntt.net (129.250.5.40) [AS2914] 323.084 ms 324.204 ms 329.300 ms 10 as-0.r22.osakjp01.jp.bb.gin.ntt.net (129.250.5.35) [AS2914] 457.845 ms 459.011 ms 456.842 ms 11 as-0.r20.newthk02.hk.bb.gin.ntt.net (129.250.2.7) [AS2914] 495.869 ms 495.615 ms 496.840 ms 12 ae-1.r02.chwahk02.hk.bb.gin.ntt.net (129.250.3.131) [AS2914] 476.471 ms 478.525 ms 478.104 ms 13 * * * 14 * * * 15 * * * *Router:* gin-mlv-core1 *Site:* IN, Mumbai - MLV, VSNL *Command:* show ip bgp 192.48.79.30 BGP routing table entry for *192.48.79.0/24* Bestpath Modifiers: deterministic-med Paths: (3 available, best #2) Multipath: eBGP 2914 36631 36631, (aggregated by 36631 203.131.245.40) ldn-icore1. (metric 2991) from mlv-tcore1. (66.110.10.202) Origin IGP, valid, internal Community: Originator: ldn-icore1. 2914 36631 36631, (aggregated by 36631 203.131.245.40) ldn-icore1. (metric 2991) from cxr-tcore1. (66.110.10.113) Origin IGP, valid, internal, best Community: Originator: ldn-icore1. 2914 36631 36631, (aggregated by 36631 203.131.245.40) ldn-icore1. (metric 2991) from mlv-tcore2. (66.110.10.215) Origin IGP, valid, internal Community: Originator: ldn-icore1. Path via NTT in all cases. So Mumbai - London - Japan - HongKong. Very likely because of same old problem I mentioned - Tata peers with NTT in London but not Japan. anurag@laptop:~$ dig j.gtld-servers.net a +short 192.48.79.30 anurag@laptop:~$ awhois 192.48.79.30 AS | IP | BGP Prefix | CC | AS Name 36631 | 192.48.79.30 | 192.48.79.0/24 | US | ZGTLD - VeriSign Global Registry Services http://bgp.he.net/AS36631#_peers And situation for Airtel isn't better at all for J root. Instead of picking NTT, they are using Packnet/AsiaNetcom because Packnet is likely a client of Hurricane Electric and Airtel peers with HE. Mon Mar 12 14:22:49 GMT+05:30 2012 traceroute 192.48.79.30 Type escape sequence to abort. Tracing the route to j.gtld-servers.net (192.48.79.30) 1 59.145.6.149 [MPLS: Label 800 Exp 0] 288 msec 59.145.6.145 [MPLS: Label 800 Exp 0] 284 msec 59.145.0.181 [MPLS: Label 1668 Exp 0] 260 msec 2 202.56.223.50 [MPLS: Label 308480 Exp 0] 256 msec 256 msec 202.56.223.205 [MPLS: Label 311696 Exp 0] 276 msec 3 182.79.220.198 [MPLS: Label 1795 Exp 0] 276 msec 276 msec 182.79.252.161 [MPLS: Label 1795 Exp 0] 272 msec 4 AES-Static-122.36.144.59.airtel.in<http://aes-static-122.36.144.59.airtel.in/> (59.144.36.122) 272 msec 272 msec 288 msec 5 he.net.coresite.com (206.223.143.122) 288 msec 292 msec 272 msec 6 10gigabitethernet2-1.core1.lax1.he.net (72.52.92.121) [AS 6939] 272 msec 276 msec 288 msec 7 pacnet.10gigabitethernet2-3.core1.lax1.he.net (216.218.223.206) [AS 6939] 288 msec 288 msec 272 msec 8 te0-1-0-0.wr1.nrt0.asianetcom.net (61.14.157.89) [AS 10026] 264 msec 264 msec 284 msec 9 te0-0-4-0.wr2.nrt0.asianetcom.net (61.14.157.14) [AS 10026] [MPLS: Label 16191 Exp 0] 288 msec 292 msec 276 msec 10 te0-0-0-0.wr2.osa0.asianetcom.net (61.14.157.2) [AS 10026] [MPLS: Label 16002 Exp 0] 276 msec 300 msec 292 msec 11 te0-0-4-0.wr1.osa0.asianetcom.net (61.14.157.21) [AS 10026] 292 msec 292 msec 276 msec 12 te0-1-0-0.wr1.hkg0.asianetcom.net (61.14.157.57) [AS 10026] 272 msec 268 msec 288 msec 13 ge-4-1-0-0.cr4.hkg3.asianetcom.net (61.14.157.142) [AS 10026] 284 msec 288 msec 264 msec 14 te3-2.gw1.hkg4.asianetcom.net (202.147.16.198) [AS 10026] 336 msec 264 msec 284 msec 15 VNB-0025.gw1.hkg4.asianetcom.net<http://vnb-0025.gw1.hkg4.asianetcom.net/> (203.192.137.78) [AS 10026] 284 msec 288 msec 268 msec 16 * * * Same problem applies on J gTLD server too. It might be having an instance in India but since no link to local ISPs or niXi...everyone hears J root in Hong Kong. Anyone from Verisign or Indian ISPs here for onlist or offlist comments? Again, I apologize for any wrong conclusions. I am still learning all this stuff. Please excuse my ignorance and correct me if you find something. Thanks On Sun, Mar 11, 2012 at 4:57 PM, Peter Losher <plosher@isc.org> wrote:
On Mar 11, 2012, at 4:11 AM, Anurag Bhatia wrote:
Btw coming back to original question - can you put some light on gTLDs in India? Are there any instances? Just to clarify - with gTLD I am refering to .com/net/org primarily.
You would have to ask Verisign as operators of the com/net gTLD servers and Afilias for .org about their DNS deployments. I can only speak for ISC as we operate F.ROOT-SERVERS.NET.
Best Wishes - Peter -- [ plosher@isc.org | Senior Operations Architect | ISC | PGP E8048D08 ]
-- Anurag Bhatia anuragbhatia.com or simply - http://[2001:470:26:78f::5] if you are on IPv6 connected network! Twitter: @anurag_bhatia <https://twitter.com/#!/anurag_bhatia> Linkedin: http://linkedin.anuragbhatia.com