Intent When there is a city wide Wireless Sensor Network (WSN), this has to be resolved with anything meaningful, say name of where it is located. then this has to be the name that it should be resolved to. to creat DNSed, as in past tense in English for DNS. To DNS the shit out of the IoT. To create an amazing network and to overload the DNS servers. To create everything out in the open, so everything in the Hollywood movies can come true. Scenario When a water tank level indicator at place called “Meereen”. There is a number for the water tank which is 256. then, this can be described in the internet nomenclature as domain name: meereen.got object: water tank number: 256 sensor type: level indicator this would translate to an internet name of “level.256.water.meereen.got” usually, there is only a sensor in a an area and they are organised in cluster. in that case, Meereen’s water tank is being referenced, and the sensor 256 is being addressed where the level is being asked for, https://256.water.meereen.got/level where level is a service provided by the sensor Possibility: It is possible to use BIND9 to build a DNS server, then create the zone records to point to the different sensors. the tutorial gives a good insight on deploying a BIND9 DNS server [3]. There are very good python libraries available in such an instance to build an DNS server and then work with their API. The following are some interesting DNS APIs… Read more