subdomains.domain.com

[Michael Kjorling]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Jun 20 2001 08:02 -0700, Danie I. wrote:

> Michael,
> Thank you very much for the kind advice.
> But what naughty little bast..., please ?

You do want to be careful with wildcard records - e.g. in terms of
mail routing. I'm sure there are people here who can tell horror
stories. I have never used wildcard records for this very reason, and
try to stay away from them.

> Would you pls desfine a little for me and any other way to handle
> this task of delegating subdomains to anotherNS.com
>
> Forwarders ? .

Will forward everything you are not authorative for - I doubt that is
what you're going for.

Of course you could do it the standard way, without wildcards:

	$ORIGIN domain.com.
	@ SOA xxx xxx ...
	@ A 123.45.67.89
	subdomain1 NS ns1.nameserver.com.
		NS ns2.nameserver.com.
	subdomain2 NS ns1.nameserver.com.
		NS ns2.nameserver.com.
	; ...

This is the way I'd do it. If you have too many subdomains to
conviniently type all the NS records by hand, write a script to do it.


Michael Kjörling

- -- 
Michael Kjörling - michael at kjorling.com - PGP: 8A70E33E
"We must be the change we wish to see" (Mahatma Gandhi)

^..^     Support the wolves in Norway -- go to     ^..^
 \/   http://home.no.net/ulvelist/protest_int.htm   \/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7MMriKqN7/Ypw4z4RAl2SAJ9XdVzq3oVmrmHQmDG4p/DC5mj8aACg4OUA
e6hvVZolpvDm1KfqljFrT2E=
=fB1u
-----END PGP SIGNATURE-----