Differences between version 10 and previous revision of ResourceRecord.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 10 | Last edited on Sunday, November 28, 2004 11:38:44 am | by AristotlePagaltzis | Revert |
| Older page: | version 9 | Last edited on Sunday, November 28, 2004 11:29:51 am | by AristotlePagaltzis | Revert |
@@ -13,9 +13,9 @@
</verbatim>
__<tt>A6</tt>__:
Supposed to obsolete <tt>AAAA</tt> for [IPv6] addresses.
- Many people continue using AAAA due to the complexity of A6, see [AAAAvsA6].
+ Many people continue using <tt>
AAAA</tt>
due to the complexity of A6, see [AAAAvsA6].
Specified in RFC:2874. Example:
<verbatim>
$ORIGIN X.EXAMPLE.
N A6 64 ::1234:5678:9ABC:DEF0 SN-1.IP6
@@ -34,9 +34,9 @@
mail.xtra.co.nz CNAME mta.xtra.co.nz
mta.xtra.co.nz A 203.96.92.132
</verbatim>
- Some record types in [DNS] are not allowed to be CNAMEs
. Similar to DNAME. See the NamedNotes page for more details.
+ Some record types in [DNS] are not allowed to be <tt>CNAME</tt>s
. Similar to <tt>
DNAME</tt>
. See the NamedNotes page for more details.
__<tt>DNAME</tt>__:
Basically a <tt>CNAME</tt> for an entire domain. Specified in RFC:2672. Example:
<verbatim>
@@ -44,9 +44,9 @@
</verbatim>
With this in place <tt>[www.test.meta.net.nz|http://www.test.meta.net.nz/]</tt> resolves to <tt>www.wlug.org.nz</tt>.
Support for this feature is spotty. DanBernstein refuses to implement it and it doesn't seem to be mentioned at all in MicrosoftWindows (as of 2004-07-14).
- Only [BIND] seems to support it, but since it will also serve you a [
CNAME]
, most resolvers should deal with it properly:
+ Only [BIND] seems to support it, but since it will also serve you a <tt>
CNAME</tt>
, most resolvers should deal with it properly:
<verbatim>
test.meta.net.nz. 86400 IN DNAME wlug.org.nz.
www.test.meta.net.nz. 0 IN CNAME www.wlug.org.nz.
www.wlug.org.nz. 80464 IN CNAME hoiho.wlug.org.nz.
@@ -67,16 +67,16 @@
xtraceroute(1) will use these records if it can find them. Unfortunately not many sites use them.
__<tt>MX</tt>__:
MailExchanger. Identifies the [SMTP] MailServer(s) responsible for the domain.
- When no MX record exists and an A record does, the A record is chosen to take mail.
+ When no <tt>
MX</tt>
record exists and an <tt>
A</tt>
record does, the <tt>
A</tt>
record is chosen to take mail.
Specified in RFC:1035. Example:
<verbatim>
foo.com. IN MX 10 mail.foo.com.
</verbatim>
The "10" is the priority. Delivery will be attempted to MailServer~s in order of ascending priority value.
- __Note:__ the data for an MX record is a host name, __NOT__ an IP address. The following will __NOT__ work:
+ __Note:__ the data for an <tt>
MX</tt>
record is a host name, __NOT__ an [
IP]
address. The following will __NOT__ work:
<verbatim>
foo.com. IN MX 10 130.123.7.10
</verbatim>
@@ -103,9 +103,9 @@
86400 ; Retry (24 hours)
2419200 ; Expire (28 days)
604800 ) ; Neg TTL (7 days)
</verbatim>
- The name is given as "<tt>@</tt>", since that is the shorthand for the value of <tt>$ORIGIN</tt>. [TTL] is missing from this example, as it takes the zone default defined above as <tt>$TTL</tt>. The class will usually always be IN, [RR] should be obvious :)
. The name-server field is bascally
the [FQDN] of the PrimaryNameServer for the domain (don't forget the trailing '.'
!). The email-address field is the address of the person responsible for the domain -- the first dot should be read as an <tt>@</tt>, so above should be read as <tt>root@ethernal.tla</tt>. The values in parenthesis are described below:
+ The name is given as "<tt>@</tt>", since that is the shorthand for the value of <tt>$ORIGIN</tt>. [TTL] is missing from this example, as it takes the zone default defined above as <tt>$TTL</tt>. The name-server field is basically
the [FQDN] of the PrimaryNameServer for the domain (don't forget the trailing fullstop
!). The email-address field is the address of the person responsible for the domain -- the first dot should be read as an <tt>@</tt>, so above should be read as <tt>root@ethernal.tla</tt>. The values in parenthesis are described below:
Serial number::
Generally given in YYYYMMDDXX format, giving 100 possible revisions of any given zone in a day (Usually more than enough).
Refresh::
