client 1.2.3.4#56789: update 'sampledomain.com/IN' denied

[Simon Waters]

Doug Barton wrote:
> 
> On Mon, 1 Jul 2002, Simon Waters wrote:
> 
> >
> > Johan Kuuse wrote:
> > >
> > > I still have some doubts.
> > > If I change the MNAME field to "localhost" for zone "sampledomain.com",
> > > should the host "localhost.sampledomain.com" be used as 127.0.0.1?
> >
> > Yes, all domains (that clients belong to) should have a
> > localhost (that is in an RFC somewhere), pointing to 127.0.0.1.
> 
> Reference please? http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc1537.html
> suggests something similar to what you're saying, but it actually wants
> you to be authoritative for "localhost." which is something quite
> different. I added the following to my resolvers configs a while back:

RFC1537

"Note that all domains that contain hosts should have a
"localhost" A
 record in them."

I don't think I'm pushing it to suggest "localhost" should be
127.0.0.1 in these examples, but I suppose the standard doesn't
say it has to map to 127.0.0.1. Paul has bemoaned the dubious
status of 127/8 before.

RFC1537 doesn't say you should be a primary for "localhost."
only that you primary "0.0.127.in-addr.arpa." and map " 1 IN PTR
localhost.". I think you are infering stuff that isn't stated
from them using "localhost." as a name server.

nslint never liked the failure of PTR and A records to match for
127.0.0.1, I never fixed it either, the code just left my meagre
programming skills behind.