| migration (135446) | migration (143731) |
|---|---|
| 1Copyright (C) 2004 Internet Systems Consortium, Inc. ("ISC") 2Copyright (C) 2000, 2001, 2003 Internet Software Consortium. 3See COPYRIGHT in the source root or http://isc.org/copyright.html for terms. 4 5 BIND 8 to BIND 9 Migration Notes 6 7BIND 9 is designed to be mostly upwards compatible with BIND 8, but 8there is still a number of caveats you should be aware of when --- 105 unchanged lines hidden (view full) --- 114by BIND 9. The fix is to move the opening parenthesis to the first 115line. 116 1172.5. Unimplemented BIND 8 Extensions 118 119$GENERATE: The "$$" construct for getting a literal $ into a domain 120name is deprecated. Use \$ instead. 121 | 1Copyright (C) 2004 Internet Systems Consortium, Inc. ("ISC") 2Copyright (C) 2000, 2001, 2003 Internet Software Consortium. 3See COPYRIGHT in the source root or http://isc.org/copyright.html for terms. 4 5 BIND 8 to BIND 9 Migration Notes 6 7BIND 9 is designed to be mostly upwards compatible with BIND 8, but 8there is still a number of caveats you should be aware of when --- 105 unchanged lines hidden (view full) --- 114by BIND 9. The fix is to move the opening parenthesis to the first 115line. 116 1172.5. Unimplemented BIND 8 Extensions 118 119$GENERATE: The "$$" construct for getting a literal $ into a domain 120name is deprecated. Use \$ instead. 121 |
| 1222.6. TXT records are no longer automatically split. |
|
| 122 | 123 |
| 124Some versions of BIND accepted strings in TXT RDATA consisting of more 125than 255 characters and silently split them to be able to encode the 126strings in a protocol conformant way. You may now see errors like this 127 dns_rdata_fromtext: local.db:119: ran out of space 128if you have TXT RRs with too longs strings. Make sure to split the 129string in the zone data file at or before a single one reaches 255 130characters. 131 |
|
| 1233. Interoperability Impact of New Protocol Features 124 1253.1. EDNS0 126 127BIND 9 uses EDNS0 (RFC2671) to advertise its receive buffer size. It 128also sets an EDNS flag bit in queries to indicate that it wishes to 129receive DNSSEC responses; this flag bit usage is not yet standardised, 130but we hope it will be. --- 107 unchanged lines hidden (view full) --- 238The BIND 8 named unconditionally sets the umask to 022. BIND 9 does 239not; the umask inherited from the parent process remains in effect. 240This may cause files created by named, such as journal files, to be 241created with different file permissions than they did in BIND 8. If 242necessary, the umask should be set explicitly in the script used to 243start the named process. 244 245 | 1323. Interoperability Impact of New Protocol Features 133 1343.1. EDNS0 135 136BIND 9 uses EDNS0 (RFC2671) to advertise its receive buffer size. It 137also sets an EDNS flag bit in queries to indicate that it wishes to 138receive DNSSEC responses; this flag bit usage is not yet standardised, 139but we hope it will be. --- 107 unchanged lines hidden (view full) --- 247The BIND 8 named unconditionally sets the umask to 022. BIND 9 does 248not; the umask inherited from the parent process remains in effect. 249This may cause files created by named, such as journal files, to be 250created with different file permissions than they did in BIND 8. If 251necessary, the umask should be set explicitly in the script used to 252start the named process. 253 254 |
| 246$Id: migration,v 1.37.2.3.2.2 2004/03/06 13:16:19 marka Exp $ | 255$Id: migration,v 1.37.2.3.2.3 2004/11/22 22:33:09 marka Exp $ |