Dave Warren <da...@hireahit.com> wrote: > > DNSMadeEasy calls this an "ANAME" record, internally they just lookup the > destination's IP and cache it, updating it as needed. > > It works, but it would be nice if this could be done in DNS. Sadly, it can't, > and probably won't in our lifetimes.
Never say never :-) You can implement something ANAME-alike with a script that polls the A and AAAA records at the target name and does a DNS UPDATE on the owner as necessary, but that might not scale too well. There are a couple of difficulties with implementing ANAME inside the server. Firstly it implies a weird authoritative/recursive hybrid. A bit ugly but not unreasonable. Secondly, and more importantly, is the question of how this works with zone transfers and secondaries. How do you ensure they support ANAME records? Do you include a backwards compatibility hack by adding the A and AAAA records to the zone? Tony. -- f.anthony.n.finch <d...@dotat.at> http://dotat.at/ Thames, Dover, Wight, Portland, Plymouth: Southwest 5 to 7, occasionally gale 8 in Thames, Dover and Wight. Moderate or rough. Rain or showers. Moderate or good, occasionally poor at first. _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users