Re: [homenet] draft-ietf-homenet-front-end-naming-delegation vs. DynDNS

[Tero Kivinen <[e-mail]>]

Juliusz Chroboczek writes:
> And it's literally four lines of shell:
> 
>     while true; do
>         wget --post-data 'name=gameserver.myhome.net&password=topsecret' \
>              https://dyndns.example.com
>         sleep $((24 * 3600))
>     done

How does that get both IPv4 and IPv6 addresses published? Perhaps bit
more parameters are needed?

The reason people use those dyndns services is because they only use
IPv4, and they have NATs, and they want to publish the outer address
of the NAT. I would hope we are getting proper non-natted IPv6
networks with globally routable address at home too, so you do not
need to use such hacks.

On the other hand same thing using nsupdate (using TSIG and dynamic
dns) is one command line + input file for nsupdate:
----------------------------------------------------------------------
nsupdate -k $KEYFILE << EOF
server ns.example.com.
zone myhome.net.
update add gameserver.myhome.net. 3600 A $IP4
update add gameserver.myhhome.net. 3600 AAAA $IP6
send
EOF
----------------------------------------------------------------------
No need to sleep and do operations periodically, you only need to run
this when the IP-addresses change...
-- 
[e-mail]