The goal of Dynamic DNS extensions is that a local host can establish initial contact with a peer host when the local host knows only the HIT of the peer but not the IP address or domain name. The extensions do not provide hostname-to-HIT look up support (see section Chapter 32, DNS proxy), just HIT-to-IP look up.
Currently HIP daemon performs name resolution in the following order:
in hit-to-ip.infrahip.net zone
With "hipconf hit-to-ip on", the HIP daemon uses IP addresses of 5.7.d.1.c.c.8.d.0.6.3.b.a.188.8.131.52.0.5.2.e.4.7.5.e.184.108.40.206.0.0.2.hit-to-ip.infrahip.net. to contact peer host with HIT 2001:1e:574e:2505:264a:b360:d8cc:1d75
Default hit-to-ip.infrahip.net. suffix can be changed with "hipconf hit-to-ip-set <new.hit-to-ip.zone.>. Please note it is independent from HIT_TO_IP_ZONE in /etc/hip/nsupdate.conf"
With "hipconf nsupdate on", the HIP daemon also maintains records in hit-to-ip.infrahip.net. Once you start hipd, it will call nsupdate.pl with HIT and IP address for every HIT of your host. It is executed upon mobility events (i.e. address changes) later on. There is an example of update query:
update delete 5.7.d.1.c.c.8.d.0.6.3.b.a.220.127.116.11.0.5.2.e.4.7.5.e.18.104.22.168.0.0.2.hit-to-ip.infrahip.net update add 5.7.d.1.c.c.8.d.0.6.3.b.a.22.214.171.124.0.5.2.e.4.7.5.e.126.96.36.199.0.0.2.hit-to-ip.infrahip.net 1 IN A 188.8.131.52 update add 5.7.d.1.c.c.8.d.0.6.3.b.a.184.108.40.206.0.5.2.e.4.7.5.e.220.127.116.11.0.0.2.hit-to-ip.infrahip.net 1 IN AAAA 2001:708:140:220:215:60ff:fe9f:60c4
hit-to-ip.infrahip.net used for experiments has HIT in SOA record, therefore updates are sent to HIT and cause HIP base exchange with the master DNS server. Your system should resolve its location by HIT. After the base exchange update is submitted via HIP, which allows DNS server to authenticate the clients and permit updates only of their own location. Changes made to ISC BIND can be found in patches/bind directory.
We also try to assign domain name pointers for HITs. On daemon start nsupdate.pl will query 5.7.d.1.c.c.8.d.0.6.3.b.a.18.104.22.168.0.5.2.e.4.7.5.e.22.214.171.124.0.0.2.ip6.arpa and send update if needed. Unfortunately we modify information in 126.96.36.199.0.0.2.ip6.arpa only on our DNS server as we do not have global delegation yet.