No cache for NS RR in public DNS

[Lightner, Jeff]

You're saying its getting the records because they are cached at org? 

-----Original Message-----
From: bind-users-bounces+jlightner=water.com at lists.isc.org
[mailto:bind-users-bounces+jlightner=water.com at lists.isc.org] On Behalf
Of Mark Andrews
Sent: Friday, October 15, 2010 9:21 AM
To: Tech W.
Cc: bind-users at isc.org
Subject: Re: No cache for NS RR in public DNS


In message <811222.51900.qm at web15706.mail.cnb.yahoo.com>, "Tech W."
writes:
> Hello,
> 
> like this domain:
> 
> blogchina.org
> 
> I can't get its NS RR in public DNS:
> 
> dig blogchina.org ns @8.8.8.8
> 
> get nothing.
> 
> But it does work correctly.
> for example, query the record:
> 
> dig udb.yy.blogchina.org
> 
> works!

No. It's just that the lookup of udb.yy.blogchina.org does not
depend apon the presence of the blogchina.org ns records in the
zone.  The resolver uses the records from the org zone.  Only when
you explictly query for them do you notice their absence.

> How to setup Bind for this?
> 
> Thanks!
> 
> 
>       
> _______________________________________________
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org
_______________________________________________
bind-users mailing list
bind-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
 
Proud partner. Susan G. Komen for the Cure.
 
Please consider our environment before printing this e-mail or attachments.
----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
----------------------------------