Newbie question: exposing a "sub" domain

[Beau E. Cox]

Thank you Kevin - I'll try that
(put "something.mydomain.com" in the
"mydomain.com" zone.)

Aloha => Beau.

-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
Behalf Of Kevin Darcy
Sent: Tuesday, October 22, 2002 3:22 PM
To: bind-users at isc.org
Subject: Re: Newbie question: exposing a "sub" domain



"Beau E. Cox" wrote:

> Hi -
>
> I have bind 9 up and running on my Linux server.
>
> I have a registered domain, say "mydomain.com".
>
> Can I expose "someplace.mydomain.com" to the
> external world, or do I have to register my
> nameserver or "someplace.mydomain.com"?
>
> In a nutshell:
>
> If a public nameserver out there in i-land gets
> a request to go to "somplace.mydomain.com", does it:
>
> 1> look up "someplace.mydomain.com"
> 2> It will not be found.
> 3> then, lookup "mydomain.com" -or- fail?

If you already have mydomain.com registered and are already hosting it
successfully, then you can add the name "someplace.mydomain.com" to that
DNS zone and everyone should be able to resolve it. Same goes for names
underneath someplace.mydomain.com, e.g. "foo.someplace.mydomain.com".

However, if you want "someplace.mydomain.com" to be served by a
different set of nameservers than those which serve "mydomain.com", e.g.
so that the "someplace" folks can maintain their own branch of the
DNS tree, then you need to delegate a subzone, and that is a lot more
complicated than simply adding names to the mydomain.com zone. I won't
go into the details unless that's what you're actually intending to do.


-Kevin