Sample updating client records
All editing must be done on the authoritative nameservers for the given domain. If you are uncomfortable with the command line, you can also update your A records using Web Host Manager.NOTE: Before updating any DNS record, you will want to lower the Time to Live (TTL) values for that zone file. If you have any questions or are not comfortable making these changes yourself, please feel free to contact Heroic Support.This article assumes that you are running BIND on a linux server, that you already have an understanding of what DNS is, the different types of DNS entries, and how DNS works. In this example, we will change the IP address of the ftp.subdomain.Please note: The incorrect editing of your zone file can take your site offline. To make these changes from the command line: That is all you have to do to change an A record on the command line.A guide to dropping the TTL values can be found here. ( 2010090802 ; serial, todays date todays 86400 ; refresh, seconds 7200 ; retry, seconds 3600000 ; expire, seconds 86400 ) ; minimum, seconds === Liquid Web’s Heroic Support is always available to assist customers with this or any other issue.Below is an example of what the zone file looks like from the command line. It would be perfectly feasible to implement Record Update in order to maintain a database served only via OAI, or only via a proprietary HTML interface.To contrast OAI and record update, OAI is a pull mechanism to update databases and is used generally for scheduled batch processing, while record update is a push mechanism intended for more interactive use.
* * Copyright (c) 2012 Yannick Albert ( * Licensed under the MIT license (By default, Samba creates the following two forward zones during provisioning/upgrading (of course with your own domain name): The Samba internal DNS is a new implementation.Although BIND is a grown up DNS and long in production on millions of servers, the Samba BIND DLZ module is still new.The Record Update service allows for remote maintenance from and administration of records within a compliant database.It has a simple and extensible mechanism for this, a single request/response pair that allows for creation, replacing and deleting records and metadata about those records.