Hi,
I'm currently looking for a convenient solution for the problem of manual
configuration of DNS RRs. The usual setup is that you configure domain and
IP relation in your DNS configuration, in zonefiles or some other kind of
DB, and nearly the same configuration is done in your server application,
may it be a HTTP, SMTP or XMPP server.
In my opinion an ideal solution would be that the applications send the
records they need to the master DNS server. This kind of DNS record
management would be ideal for shared hosting providers or clustered server
situations. I'm sure several shared hosting providers already deploy
something of that kind but I haven't found a open documented way of doing
this.
After all one should aim for minimal configuration by humans to reduce the
amount of errors being introduced by them. Sure, some manual configuration
would still be needed in the DNS server for example, DNS records like SOA
and NS and authentication information to authenticate applications (entities
that want to send DNS updates) against the server.
The protocol that seems to handle such DNS updates seems to be RFC 2136
which is around since 1997. I wonder how far this RFC is implemented among
authoritative DNS servers and whether that RFC is the right approach to
solve the problem of double DNS configuration.
Cheers,
Tobias Markmann
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf