domain name entries in a zone

Preston Wade Preston_Wade at hilton.com
Thu Jun 3 22:10:32 UTC 2004


I think that because, I think of a domain and a host as two different =
types of nodes.  If you want host type entries such as foo.com then they =
should live in the com domain.  If you want host type entries such as =
www.foo.com then they should live in the foo.com domain.

Thanks,
Preston

-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
Behalf Of Barry Margolin
Sent: Wednesday, June 02, 2004 1:09 PM
To: comp-protocols-dns-bind at isc.org
Subject: Re: domain name entries in a zone


In article <c9kuga$2lab$1 at sf1.isc.org>,
 "Preston Wade" <Preston_Wade at hilton.com> wrote:

> Thanks for the reply.
>=20
> The primary domain is actually being hosted by someone else.  So in =
this =3D
> case this would not work.  However I am using this method for some =
other =3D
> domains.
>=20
> I think a lot of people have missed my point.  I wasn't looking for =
=3D
> responses about what users expect.  I get that all the time.  I was =
=3D
> really looking for more of a philosophical conversation around whether =
=3D
> host type records should be allowed for domain names.  Personally, I =
=3D
> believe host type resource records for foo.com should have to be made =
in =3D
> the com domain.  Not that it would be possible, but given the =
hierarchy =3D
> that is how I think it should work.

Why do you think that?  The organization that manages the COM domain=20
doesn't manage any of the machines or networks in the FOO.COM domain. =20
Why should they be involved if the address of the foo.com machine=20
changes?  The purpose of delegation is to assign the responsibility for=20
maintaining records to the organization that's managing the hosts or=20
networks.  The only time the parent zone's administrators should be=20
involved is if something related to the delegation is changing.

--=20
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***





More information about the bind-users mailing list