client 1.2.3.4#56789: update 'sampledomain.com/IN' denied
Doug Barton
DougB at DougBarton.net
Mon Jul 8 01:33:07 UTC 2002
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:
/* RFC 1537 recommends these in order to prevent spurious queries */
zone "localhost" { type master; file "master/rfc1537.db"; };
zone "0.in-addr.arpa" { type master; file "master/rfc1537.db"; };
zone "127.in-addr.arpa" { type master; file "master/rfc1537.db"; };
zone "255.in-addr.arpa" { type master; file "master/rfc1537.db"; };
This is that file:
$TTL 1h
@ SOA localhost. hostmaster.yahoo-inc.com. (
42 1d 12h 1w 10m )
; Serial, Refresh, Retry, Expire, Neg. cache TTL
NS localhost.
A 127.0.0.1
1.0.0 PTR localhost.
I plan to add authority for the rfc 1918 space zones to that as well, as
soon as I find time to test how that'll interact with our own use of those
zones.
--
"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!?
More information about the bind-users
mailing list