On Wed, Sep 2, 2009 at 3:03 PM, Edward Lewis<ed.le...@neustar.biz> wrote: >> It works very well. One large country's incumbent telco has all of its >> subscribers behind a scripted powerdns server synthesising PTRs, and >> with exception of the large hardware cost savings (these were gigabyte >> size zones), nobody noticed. (...) > "It works very well"? - From your response it sounds like it *doesn't* work > with the things I mentioned. This is a good idea, a good start. It just > needs further development.
DNS can be seen as two things - one is about actual zones, and distributing them over AXFR, and supporting things like dynamic updates etc. The other DNS is about answering questions in a valid way, without being interested in the backend, since it is out of sight. In this second sense, scripting answers works very well, and powers autogenerated PTR records, but also interesting forms of (geographical) load balancing. So for most people, it really works very well - even if there is no zone that can be transferred, or updated using dynamic updates. > and slaves have to be the same make. Sure, you can achieve all this with > one implementation that shares a database backend - but the DNS protocol > doesn't have a standard way to plug in any database to any name server. The protocol may not, but several implementations do. > I think there is a latent need to extend the DNS protocol to include an > answer synthesis mechanism that is more flexible than RFC 4592. It's easy to > come up with partial solutions, we need one that has all the features or the > current protocol. Dunno - I don't hear any users clamoring for it. They typically think of DNS in the second sense. Bert _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
