This page covers the following:
- Why do we need the DNS Infrastructure?
- How to Provision NetIDs and JoinEUIs in the DNS for OTAA and Roaming?
As per the LoRaWAN Backend specifications, the DNS infrastructure is used for the following operations:
- OTAA: By the NS to get the IP address of the Join Server
- Roaming: By the vNS (Visited NS) to find the hNS (Home NS)
- OTAA: Associate a batch of devices to one specific Join Server using a DNS look-up, combining DevEUI and JoinEUI
Two types of identifiers are provisioned in the DNS - 1. NetIDS for Roaming and 2. JoinEUI for OTAA. as per the backend specification, the LoRa Alliance DNS tree is as shown in the below figure:
As of now, the LoRa DNS service is not operational. Hence, for the Academic LoRaWAN roaming purposes we have a separate zone called iotreg.net where the NetIDs and JoinEUIs could be provisioned as shown in the figure below:
To provision the information in the DNS (Currently only the JoinEUI info), Send your JoinEUI information (i.e. the Join EUI and the corresponding JS domain name or IP address) to sandoche.balakrichenan@afnic.fr AND antoine.bernard@afnic.fr
Once the JoinEUI information is updated to the DNS, one can verify whether the information is updated properly by reversing the JoinEUI, delimiting by ‘.’ and adding the suffix “joineuis.iotreg.net” and testing using the dig utility as shown inthe figure:
Once verified that your NetID and JoinEUI provisioned in the Internet are publicly accessible, Next section to follow : OTAA-Setup Using DNS
- In any case, If you want to go back to the Readme Page
- In any case, If you want to go back to the Architecture page
- In any case, If you want to go back to the Setting up the End-Device
- In any case, If you want to go back to the Setting up the GW
- In any case, If you want to go back to the NS Setup
- In any case, If you want to go back to the AS Setup