Problems w/ Reverse DNS and RFC 2317

G. Del Merritt dmerritt at intranets.com
Fri May 19 13:32:44 UTC 2000


At 11:25 AM 5/18/00 +1000, Mark.Andrews at nominum.com wrote:
>         Also I would *not* call the zone 64_26.137.7.12.in-addr.arpa as
>         there are broken resolvers that will reject that name.  I would
>         use "64-127.137.7.12.in-addr.arpa" instead as this works with
>         these broken resolvers.  It is also a naming scheme which copes

This confuses me.  RFC 819 (Appendix A), RFC 1034, and RFC 1035 don't allow 
"_" in domain names*.  Is that prohibition countermanded by a later RFC and 
I've just missed the update?  Or is a resolver that wouldn't handle 
64_26.137.7.12.in-addr.arpa "broken" for some other reason?

* 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"...


--
G. Del Merritt                                dmerritt at intranets.com
http://www.intranets.com - Get everyone on the same page(sm)




More information about the bind-users mailing list