Network2/Experiments/tinydns: Difference between revisions
< Network2 | Experiments
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 2: | Line 2: | ||
== Dynamic DNS configuration == |
== Dynamic DNS configuration == |
||
There seems to be no widely-adopted standard API for (remotely) modifying DNS zone files. For example, the standardized DNS UPDATE protocols defined by RFCs [http://tools.ietf.org/html/rfc2136 2136] and [http://tools.ietf.org/html/rfc3007 3007] seem to be sparsely implemented at best. Other approaches, like [http://tools.ietf.org/html/draft-jennings-app-dns-update-02 draft-jennings-app-dns-update-02] have not been standardized. Finally, there are open problems with truth maintenance as described in other unstandardized work [ |
There seems to be no widely-adopted standard API for (remotely) modifying DNS zone files. For example, the standardized DNS UPDATE protocols defined by RFCs [http://tools.ietf.org/html/rfc2136 2136] and [http://tools.ietf.org/html/rfc3007 3007] seem to be sparsely implemented at best. Other approaches, like [http://tools.ietf.org/html/draft-jennings-app-dns-update-02 draft-jennings-app-dns-update-02] have not been standardized. Finally, there are open problems with truth maintenance as described in other unstandardized work [http://files.dns-sd.org/draft-sekar-dns-ul.txt draft-sekar-dns-ul-01]. |
||
http://files.dns-sd.org/draft-sekar-dns-ul.txt draft-sekar-dns-ul-01]. |
|||
Revision as of 18:43, 25 December 2009
Dynamic DNS configuration
There seems to be no widely-adopted standard API for (remotely) modifying DNS zone files. For example, the standardized DNS UPDATE protocols defined by RFCs 2136 and 3007 seem to be sparsely implemented at best. Other approaches, like draft-jennings-app-dns-update-02 have not been standardized. Finally, there are open problems with truth maintenance as described in other unstandardized work draft-sekar-dns-ul-01.