Problems w/ Reverse DNS and RFC 2317

[Joseph S D Yao]

On Fri, May 19, 2000 at 09:32:44AM -0400, G. Del Merritt wrote:
> * The BNF also doesn't allow for in-addr.arpa naming either, since the 
> strings don't begin with a "#".  It's nice to have standards that call 
> themselves "conventions"...

This is changed in a later RFC.  I don't have it in front of me, but
the archives are searchable now, and the question of naming standards
comes up every month or so.  Please note that the RFCs you cited are
obsoleted and updated by a couple of newer ones.  ;-)

1034 Domain names - concepts and facilities. P.V. Mockapetris.
     Nov-01-1987. (Format: TXT=129180 bytes) (Obsoletes RFC0973, RFC0882,
     RFC0883) (Obsoleted by RFC1065, RFC2308) (Updated by RFC1101,
     RFC1183, RFC1348, RFC1876, RFC1982, RFC2065, RFC2181, RFC2308,
     RFC2535) (Also STD0013) (Status: STANDARD)

1035 Domain names - implementation and specification. P.V.
     Mockapetris. Nov-01-1987. (Format: TXT=125626 bytes) (Obsoletes
     RFC0973, RFC0882, RFC0883) (Updated by RFC1101, RFC1183, RFC1348,
     RFC1876, RFC1982, RFC1995, RFC1996, RFC2065, RFC2181, RFC2136,
     RFC2137, RFC2308, RFC2535) (Also STD0013) (Status: STANDARD)

You might try an INFORMATIONAL RFC:
1912 Common DNS Operational and Configuration Errors. ...

-- 
Joe Yao				jsdy at cospo.osis.gov - Joseph S. D. Yao
COSPO/OSIS Computer Support					EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.