Wildcard in NS record
michael at kjorling.com
Fri Oct 19 16:26:24 UTC 2001
-----BEGIN PGP SIGNED MESSAGE-----
First of all, I would add "thankfully" about the error message. BIND 9
is a lot more picky about the fact that zone files should follow the
standards - something that should have been enforced in the first
place, but for various reasons was not.
When you delegate, you need to set up a zone on the delegated-to
(RDATA part) server for the name in question. Since a host label can
be up to 63 characters long (IIRC), this means at least 36^63
combinations. That's a HUGE number. No one wants to set up that number
of zones. (My calculator gives me 1.11444*10^98 - that's roughly equal
to a single 1 followed by 98 zeroes. No, I'm not going to type them
What are you trying to accomplish, anyway?
On Oct 17 2001 17:13 +0200, Ame wrote:
> I have a wildcard in the NS record of a domain.tld on ns1.server.tld :
> @ NS ns1.server.tld.
> @ NS ns2.server.tld.
> * NS ns1.server.tld.
> for delegate every subdomain of domain.tld on the same server.
> With BIND 8.2.3 it works without problem but with BIND 9.1.3 in
> named.messages I see:
> invalid NS owner name (wildcard)
> and it doesn't work.
> Someone can help me?
Michael Kjörling -- Programmer/Network administrator ^..^
PGP: 95f1 074d 336d f8f0 f297 6a5b 2aa3 7bfd 8a70 e33e \/
Internet: michael at kjorling.com -- FidoNet: 2:204/254.4
"There is something to be said about not trying to be glamorous
and popular and cool. Just be real -- and life will be real."
(Joyce Sequichie Hifler, September 13 2001)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Public key is at http://michael.kjorling.com/contact/pgp.html
-----END PGP SIGNATURE-----
More information about the bind-users