Oleg Ponomarev wrote:
Hi! On Thu, 23 Apr 2009, Robert Moskowitz wrote:If I understand BIND enough, this means you allow anyone to do a zone transfer for 1.0.0.1.0.0.2.ip6.arpa? No acl on your side (other than {any;}):Yes, XFER is allowed now. As you can see the zone is very small. Probably it is time to put an ACL due to privacy concerns etcApr 23 10:04:47 oqo3 named[2261]: zone 1.0.0.1.0.0.2.ip6.arpa/IN/test: Transfer started. Apr 23 10:04:48 oqo3 named[2261]: transfer of '1.0.0.1.0.0.2.ip6.arpa/IN' from 193.167.187.149#53: connected using 192.168.128.35#41375 Apr 23 10:04:48 oqo3 hipd[2480]: info(netdev.c:1201@hip_netdev_event) Addr: 2607:f4b8:0003:0011:020c:96ff:fe40:cb63 Apr 23 10:04:49 oqo3 named[2261]: zone 1.0.0.1.0.0.2.ip6.arpa/IN/test: transferred serial 2008121782 Apr 23 10:04:49 oqo3 named[2261]: transfer of '1.0.0.1.0.0.2.ip6.arpa/IN' from 193.167.187.149#53: end of transfer Apr 23 10:04:49 oqo3 named[2261]: zone 1.0.0.1.0.0.2.ip6.arpa/IN/test: sending notifies (serial 2008121782)So once I have transfered, you now have my IP and send a notify?Not automatically, although I can add your IP to "also-notify". But it would trigger IXFER on every update.
I don't see any other way for this to work as I add my own records and move around my nets. At least until we get the ORCHID zone properly delegated.
BTW, the manual for Dynamic DNS mentions the zone 1.0.0.1.0.0.2.hit-to-ip.infrahip.net, not 1.0.0.1.0.0.2.ip6.arpa.
I can see HIT-to-IP using this special zone, but you seem to indicate that nsupdate is updating ip6.arpa on your server....