RR for win2k
Stephens, Bill
Bill.Stephens at fritolay.com
Thu Apr 20 11:38:54 UTC 2000
Windows 2000 DNS allows the use of the "_" character, and uses it
for its dynamic SRV records. Some clients will not allow you to query an
invalid name. For example nslookup under OS/2 (I know dead os) will not
lookup invalid hostnames, unless you add a norfc1123 record in the resolver
file. Also, he has stated that he used the warn statement in his DNS, this
should allow his DNS to host the invalid names.
-Bill Stephens
Joseph S D Yao <jsdy at cospo.osis.gov>
04/19/2000 09:11 PM
To: Tim Maestas <tmaestas at idc.dhs.org>@SMTP at Exchange
cc: Art Houle <houle at mailer.fsu.edu>@SMTP at Exchange,
bind-users at isc.org@SMTP at Exchange
Subject: Re: RR for win2k
On Wed, Apr 19, 2000 at 06:54:23PM -0700, Tim Maestas wrote:
> This is a limitation of nslookup in interactive mode. It doesn't
like
> underscores.
>
> -Tim
Incorrect. 'Nslookup' doesn't care.
Underscores are illegal in host names. If the original questioner
checks his log files, I suspect that he will find that 'named' will
not
accept this name. But even more so:
> On Wed, 19 Apr 2000, Art Houle wrote:
> > $origin xyz.tld
> > _sites IN A global-catalog.xyz.tld.
"A" records must have IP addresses on the right hand side. If you
are
using the name [without underscores] as an alias for another name,
this
should be a "CNAME" record.
> > A nslookup query responds with 'can't find _sites.xyz.tld:
Non-existent
> > hosts/domain', but it works if I remove the underbar. Is there
a config
> > option that fixes this?
Yes, there is. But it can't force all other name servers to accept
this illegal name.
The option is:
[ check-names ( master | slave | response ) ( warn | fail |
ignore); ]
e.g., if you say:
check-names master warn;
then it will be accepted but warn you of the error of your ways.
The defaults are:
check-names master fail;
check-names slave warn;
check-names response ignore;
--
Joe Yao jsdy at cospo.osis.gov - Joseph S. D.
Yao
COSPO/OSIS Computer Support
EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.
More information about the bind-users
mailing list