|
|
·
· Home
· New Account
· Admin Section
· Help
|
The RR Management screens allow you to edit all of the settings for each individual RR record within namespaces that you own.
After you have done changing your settings, click on "Save" to update the database.
If you wish to delete the record instead, you must click on the "Confirm" checkbox at the bottom of the page before you click on "Delete".
The ID number of the RR is shown at the top of the screen, and then several pieces of information are listed below:
The name and ID # of the namespace that this RR belongs to. Clicking on then ID # will open a Namespace Management screen for that namespace. Primary and Wildcard A Records will have their status shown in the Namespace field as well.
The last date and time that a change was made to the settings for this RR Record.
How many times this hostname has been looked up on the Internet, and the last time a lookup was made. Because ISPs cache DNS information, this number may not be accurate, but it still serves as a bare minumum number of DNS hits your hostname has had.
The name of the RR record within the Zone it belongs to. This will almost always be everything in the namespace's name up to the first dot (.); for instance, an RR record in the hostname.yi.org namespace would have a Name of hostname. However, if this is the primary record in a Zone, the name will be blank, and if this is a wildcard record, the name will be preceeded by the asterisk (*) symbol.
The type of RR record that this is:
The content of this RR record. The type of content that is needed depends on the Type of the RR record:
This field is only relevant if you have multiple RR Records of the same type in one namespace. It specifies the priority for these records. The record with the lowest "Aux" value is considered "most important". For example, if you have two MX records, one with an Aux value of "10" and the other with an Aux value of "20", the one with an Aux of "10" is considered the primary SMTP server, and the one with an Aux of "20", the secondary.
"Time To Live". This field specifies how many seconds this record is allowed to remain in another DNS server's cache, in seconds. The recommended value is twice as often as your IP address changes. So long as your IP address does not change, having a higher TTL increases the speed at which people can access your host while decreasing the amount of bandwidth yi.org has to consume serving your hostname.
Here are some suggested TTL values for different types of internet connections:
With most Dialup ISPs, your IP changes every time you reconnect.
With Cable/ADSL, your IP usually only changes when you reboot, and even then it is rare for your IP to change. A TTL of 86400 seconds should keep you safe.
Setting your TTL this high when you know your IP is not going to change often is a good idea. That way, ISPs will cache your IP address for a long time, so that their users do not have to preform yi.org look-ups all the time to reach your webpage.
| Apache/2.2.3 (Debian) mod_perl/2.0.2 Perl/v5.8.8 Server at www.yi.org Port 80 |
|