From 3287b57976fa270224c18aa21445d24bb7fa760f Mon Sep 17 00:00:00 2001 From: Andreas Gustafsson Date: Mon, 12 Feb 2001 22:09:52 +0000 Subject: [PATCH] RFC 1035 specifies that the current origin should be restored after an $INCLUDE, but it is silent on whether the current domain name should also be restored. BIND 9 restores both of them. This could be construed as a deviation from RFC 1035, a feature, or both. [RT #874] --- doc/arm/Bv9ARM-book.xml | 17 ++++-- doc/arm/Bv9ARM.ch06.html | 26 +++++---- doc/arm/Bv9ARM.ch07.html | 15 +++-- doc/arm/Bv9ARM.ch08.html | 14 ++--- doc/arm/Bv9ARM.ch09.html | 116 +++++++++++++++++++-------------------- doc/arm/Bv9ARM.html | 26 ++++----- 6 files changed, 115 insertions(+), 99 deletions(-) diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml index 38f8022665..7d1dab764d 100644 --- a/doc/arm/Bv9ARM-book.xml +++ b/doc/arm/Bv9ARM-book.xml @@ -2,7 +2,7 @@ - + @@ -4711,11 +4711,16 @@ if it were included into the file at this point. If origin i specified the file is processed with $ORIGIN set to that value, otherwise the current $ORIGIN is used. - -The behavior when origin is -specified differs from that described in RFC 1035. The origin and -current domain revert to the values they were prior to the $INCLUDE once -the file has been read. +The origin and the current domain name +revert to the values they had prior to the $INCLUDE once +the file has been read. + +RFC 1035 specifies that the current origin should be restored after +an $INCLUDE, but it is silent on whether the current +domain name should also be restored. BIND 9 restores both of them. +This could be construed as a deviation from RFC 1035, a feature, or both. + + The <command>$TTL</command> Directive Syntax: $TTL default-ttl diff --git a/doc/arm/Bv9ARM.ch06.html b/doc/arm/Bv9ARM.ch06.html index 5b88f6018f..451fa41fab 100644 --- a/doc/arm/Bv9ARM.ch06.html +++ b/doc/arm/Bv9ARM.ch06.html @@ -10012,6 +10012,13 @@ CLASS="command" >$ORIGIN is used.

The origin and the current domain name +revert to the values they had prior to the $INCLUDE once +the file has been read.

Note: The behavior when origin is -specified differs from that described in RFC 1035. The origin and -current domain revert to the values they were prior to the +RFC 1035 specifies that the current origin should be restored after +an $INCLUDE once -the file has been read.

, but it is silent on whether the current +domain name should also be restored. BIND 9 restores both of them. +This could be construed as a deviation from RFC 1035, a feature, or both. +

6.3.5.3. The $TTL

6.3.6. BIND
7.2. chroot

7.2. chroot

7.2.1. The chroot

7.2.2. Using the setuidBIND -to write.

named
daemon is running as a +nonprivileged user, it will not be able to bind to new restricted ports if the +server is reloaded.

8.1. Common Problems
8.2. Incrementing and Changing the Serial Number
8.3. Where Can I Get Help?

8.1. Common Problems

8.1.1. It's not working; how can I figure out what's wrong?

8.2. Incrementing and Changing the Serial Number

8.3. Where Can I Get Help?

A.1. Acknowledgements
A.3. General DNS

A.1. Acknowledgements

A.1.1. A Brief History of the DNS

A.2.1.1. HS = hesiod

A.2.1.2. CH = chaos

A.3. General DNS

A.3.1. IPv6 addresses (A6)

Bibliography

Standards

[RFC974] C. Partridge,

[RFC1034] P.V. Mockapetris,

[RFC1035] P. V. Mockapetris,

[RFC2181] R., R. Bush Elz,

[RFC2308] M. Andrews,

[RFC1995] M. Ohta,

[RFC1996] P. Vixie,

[RFC2136] P. Vixie, S. Thomson, Y. Rekhter, and J. Bound,

[RFC2845] P. Vixie, O. Gudmundsson, D. Eastlake, 3rd, and B. Wellington,

Proposed Standards Still Under Development

[RFC1886] S. Thomson and C. Huitema,

[RFC2065] D. Eastlake, 3rd and C. Kaufman,

[RFC2137] D. Eastlake, 3rd,

Other Important RFCs About DNS

[RFC1535] E. Gavron,

[RFC1536] A. Kumar, J. Postel, C. Neuman, P. Danzig, and S. Miller,

[RFC1982] R. Elz and R. Bush,

Resource Record Types

[RFC1183] C.F. Everhart, L. A. Mamakos, R. Ullmann, and P. Mockapetris,

[RFC1706] B. Manning and R. Colella,

[RFC2168] R. Daniel and M. Mealling,

[RFC1876] C. Davis, P. Vixie, T., and I. Dickinson,

[RFC2052] A. Gulbrandsen and P. Vixie,

[RFC2163] A. Allocchio,

[RFC2230] R. Atkinson,

DNS

[RFC1101] P. V. Mockapetris,

[RFC1123] Braden,

[RFC1591] J. Postel,

[RFC2317] H. Eidnes, G. de Groot, and P. Vixie,

DNS

[RFC1537] P. Beertema,

[RFC1912] D. Barr,

[RFC1912] D. Barr,

[RFC2010] B. Manning and P. Vixie,

[RFC2219] M. Hamilton and R. Wright,

Other DNS

[RFC1464] R. Rosenbaum,

[RFC1713] A. Romao,

[RFC1794] T. Brisco,

[RFC2240] O. Vaughan,

[RFC2345] J. Klensin, T. Wolf, and G. Oglesby,

[RFC2352] O. Vaughan,

Obsolete and Unimplemented Experimental RRs

[RFC1712] C. Farrell, M. Schulze, S. Pleitner, and D. Baldoni,

A.4.3. Other Documents About BIND

Bibliography

Paul Albitz and Cricket Liu,

6.3.6. BIND
7.2. chroot
7.2.1. The chroot
7.2.2. Using the setuid
8.1. Common Problems
8.1.1. It's not working; how can I figure out what's wrong?
8.2. Incrementing and Changing the Serial Number
8.3. Where Can I Get Help?
A.1. Acknowledgements
A.1.1. A Brief History of the DNS
A.3. General DNS
A.3.1. IPv6 addresses (A6)
A.4.3. Other Documents About BIND