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

[Doug Barton]

On Mon, 8 Jul 2002, Simon Waters wrote:

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

Good point... I glossed over that.

> RFC1537 doesn't say you should be a primary for "localhost."

It says:

- "localhost" itself is used and expected to work on some systems.

My feeling is, better safe than sorry. I also think that if the resolver
returns an answer for localhost. when a user types it in, it saves having
to search the other domains in the search list for localhost.domain.

Doug
-- 
   "We have known freedom's price. We have shown freedom's power.
      And in this great conflict, ...  we will see freedom's victory."
	- George W. Bush, President of the United States
          State of the Union, January 28, 2002

         Do YOU Yahoo!?