# Issues in Atlas J-root instance stats page

**URL:** <https://forum.ripe.net/t/issues-in-atlas-j-root-instance-stats-page/430>\
**Category:** RIPE Atlas\
**Tags:** dns\
**Created:** [6 April 2023 06:01 UTC](https://forum.ripe.net/t/issues-in-atlas-j-root-instance-stats-page/430 "2023-04-06T06:01:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gaurav.kansal](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.ripe.net/gaurav.kansal/32/242_2.png) [@gaurav.kansal](https://forum.ripe.net/u/gaurav.kansal)\
**Post date:** [6 April 2023 06:01 UTC](https://forum.ripe.net/t/issues-in-atlas-j-root-instance-stats-page/430/1 "2023-04-06T06:01:50Z")

</div>

In the following page, it is shown that majority of probes (located in India) going to unknown instances of J-root node (92 out of 93 going to unknown).  
[https://atlas.ripe.net/results/maps/root-instances/?server=16&question=10300&af=4&filter=India+(in)](https://atlas.ripe.net/results/maps/root-instances/?server=16&question=10300&af=4&filter=India+(in))

If looking for j-root instances from all the probes, the following page is showing 7399 probes out of 9742 probes preferring unknown j-root instance.  
[https://atlas.ripe.net/results/maps/root-instances/?server=16&question=10300&af=4&filter=](https://atlas.ripe.net/results/maps/root-instances/?server=16&question=10300&af=4&filter=)

I check the hostname.bind output for j-root instance from few ISPs from my location (New Delhi, India), i get the “rootns-eldel4” output.

On root servers page, it is mentioned that J root has an instance in New Delhi.

So, most probably most of the nodes mentioned as Unknown are legitimate nodes of J root. Is there a possibility of having a look at this and update the info on Atlas database accordingly.

---

<div class="post-metadata">

**Author:** ![camin](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.ripe.net/camin/32/243_2.png) [@camin](https://forum.ripe.net/u/camin)\
**Post date:** [6 April 2023 09:13 UTC](https://forum.ripe.net/t/issues-in-atlas-j-root-instance-stats-page/430/2 "2023-04-06T09:13:57Z")

</div>

Hi Gaurav. Yes, we can update the mapping of servers to regions. Do you know if there is a list of instances somewhere, or a description of the naming scheme? I can see that it looks very much like “rootns-el{3-letter IATA airport code}#”, but it would be nice to confirm.

---

<div class="post-metadata">

**Author:** ![gaurav.kansal](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.ripe.net/gaurav.kansal/32/242_2.png) [@gaurav.kansal](https://forum.ripe.net/u/gaurav.kansal)\
**Post date:** [6 April 2023 09:45 UTC](https://forum.ripe.net/t/issues-in-atlas-j-root-instance-stats-page/430/3 "2023-04-06T09:45:03Z")

</div>

@camin

Unfortunately No. Can we connect with some in Verisign OR we can go with adding the names as per “rootns-el{3-letter IATA airport code}#” naming convention to get rid of so called “Unknown” nodes.

---

<div class="post-metadata">

**Author:** ![camin](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.ripe.net/camin/32/243_2.png) [@camin](https://forum.ripe.net/u/camin)\
**Post date:** [6 April 2023 13:28 UTC](https://forum.ripe.net/t/issues-in-atlas-j-root-instance-stats-page/430/4 "2023-04-06T13:28:04Z")

</div>

OK, I’ll look into it and respond here when it’s fixed.

---

<div class="post-metadata">

**Author:** ![gaurav.kansal](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.ripe.net/gaurav.kansal/32/242_2.png) [@gaurav.kansal](https://forum.ripe.net/u/gaurav.kansal)\
**Post date:** [13 May 2023 07:47 UTC](https://forum.ripe.net/t/issues-in-atlas-j-root-instance-stats-page/430/5 "2023-05-13T07:47:22Z")

</div>

@camin Did you find a way to fix this ?