Send Netdot-devel mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://osl.uoregon.edu/mailman/listinfo/netdot-devel
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-devel digest..."


Today's Topics:

   1. [Netdot - Feature #756] Request DNS update via    NSUpdate
      ([email protected])


----------------------------------------------------------------------

Message: 1
Date: Mon, 24 Mar 2014 06:00:39 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #756] Request DNS update via
        NSUpdate
To: [email protected], [email protected],
        [email protected]
Cc: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8


Issue #756 has been updated by Shining 340.


How can we call a external arbitary code  when records change ? thanks
----------------------------------------
Feature #756: Request DNS update via NSUpdate
https://osl.uoregon.edu/redmine/issues/756#change-3158

Author: john-begley-twcable-com -
Status: New
Priority: Normal
Assignee: Carlos Vicente
Category: 
Target version: 
Resolution: 


Request a feature to update DNS records using NSUpdate with the proper 
credentials.  This would allow for direct communication with DNS, record by 
record, allowing live updates instead of just by zone files.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://osl.uoregon.edu/redmine/my/account


------------------------------

_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel


End of Netdot-devel Digest, Vol 84, Issue 5
*******************************************

Reply via email to