Just one record fails

[Barry Margolin]

In article <c7numk$3l3$1 at sf1.isc.org>, a.r.kuiters at kpn.com wrote:

> Hi Barry,
> 
> Yes, I've also put in a head from named.conf

You still haven't answered the question: which is the *one* record that 
fails?  Everything else is probably irrelevant.

All you've shown is a bunch of delegation records.  Is the problem 
record in one of those subdomains?  If so, the problem may be on the 
server you're delegating to.

> 
> // generated by named-bootconf.pl
> 
> options {
>         directory "/etc/named.data";    // running directory for named
>         /*
>          * If there is a firewall between you and nameservers you want
>          * to talk to, you might need to uncomment the query-source
>          * directive below.  Previous versions of BIND always asked
>          * questions using port 53, but BIND 8.1 uses an unprivileged
>          * port by default.
>          */
>         // query-source address * port 53;
> };
> 
> controls {
>   inet 127.0.0.1 allow {localhost;} keys {rndckey;};
> };
> 
> key "rndckey" {
>   algorithm hmac-md5;
>   secret "<removed>=";
> };
> 
> //
> // type         domain                  source file
> //
> zone "gprs" {
>         type master;
>         file "db.gprs";
> };
> 
> And here a head from db.gprs
> 
> $TTL 86400
> gprs. IN    SOA     ns1.mnc008.mcc204 root.ns1.mnc008.mcc204 (
>                         2004050302      ; serial
>                         3600            ; refresh every 60 min
>                         900             ; retry every 15 min
>                         604800          ; expire after a week
>                         86400           ; minimum TTL 1 day
>                         )
>                         IN      NS      ns1.mnc008.mcc204
>                         IN      NS      ns2.mnc008.mcc204
> 
> mnc002.mcc238           IN      NS      ns1.mnc002.mcc238
>                         IN      NS      ns2.mnc002.mcc238
> mnc001.mcc206           IN      NS      ns1.mnc001.mcc206
>                         IN      NS      ns2.mnc001.mcc206
> mnc003.mcc262           IN      NS      ns1.mnc003.mcc262
>                         IN      NS      ns2.mnc003.mcc262
> mnc002.mcc228           IN      NS      ns1.mnc002.mcc228
>                         IN      NS      ns2.mnc002.mcc228
> mnc030.mcc234           IN      NS      ns1.mnc030.mcc234
>                         IN      NS      ns2.mnc030.mcc234
> mnc088.mcc222           IN      NS      ns1.mnc088.mcc222
>                         IN      NS      ns2.mnc088.mcc222
> mnc001.mcc240           IN      NS      ns1.mnc001.mcc240
> 
> and a tail
> 
> ns2.mnc007.mcc262       IN      A       62.180.77.17
> ns1.mnc008.mcc262       IN      A       62.180.77.81
> ns2.mnc008.mcc262       IN      A       62.180.77.17
> ns1.mnc170.mcc310       IN      A       66.102.185.70
> ns2.mnc170.mcc310       IN      A       66.102.184.70
> ns1.mnc077.mcc270       IN      A       212.66.79.6
> ns2.mnc077.mcc270       IN      A       212.66.79.7
> ns1.bharti.india        IN      A       61.95.248.50
> ns1.mnc001.mcc208       IN      A       212.234.96.11
> ns2.mnc001.mcc208       IN      A       212.234.96.74
> 
> 
> 
> -----Oorspronkelijk bericht-----
> Van: Barry Margolin [mailto:barmar at alum.mit.edu]
> Verzonden: maandag 10 mei 2004 14:18
> Aan: comp-protocols-dns-bind at isc.org
> Onderwerp: Re: Just one record fails
> 
> 
> In article <c7nmqd$2suk$1 at sf1.isc.org>, a.r.kuiters at kpn.com wrote:
> 
> > Hi Barry,
> > 
> > The record is in db.gprs 
> 
> Which record is it?  Is the problem record shown in the DB file excerpt 
> below?
> 
> > The query answers for a quarter of an hour, the next 45 minutes it doesn't
> > 
> > The SOA looks like
> > 
> > $TTL 86400
> > gprs. IN    SOA     ns1.mnc008.mcc204 root.ns1.mnc008.mcc204 (
> >                         2004050302      ; serial
> >                         3600            ; refresh every 60 min
> >                         900             ; retry every 15 min
> >                         604800          ; expire after a week
> >                         86400           ; minimum TTL 1 day
> >                         )
> >                         IN      NS      ns1.mnc008.mcc204
> >                         IN      NS      ns2.mnc008.mcc204
> > 
> > mnc001.mcc208           IN      NS      ns1.mnc001.mcc208
> >                         IN      NS      ns2.mnc001.mcc208
> > ns1.mnc001.mcc208       IN      A       212.234.96.11
> > ns2.mnc001.mcc208       IN      A       212.234.96.74
> > 
> > There are no messages indicating this problem in the log file. 
> > 
> > Regards,
> > Rob
> > 
> > -----Oorspronkelijk bericht-----
> > Van: Barry Margolin [mailto:barmar at alum.mit.edu]
> > Verzonden: maandag 10 mei 2004 12:25
> > Aan: comp-protocols-dns-bind at isc.org
> > Onderwerp: Re: Just one record fails
> > 
> > 
> > In article <c7nknk$2r1s$1 at sf1.isc.org>, a.r.kuiters at kpn.com wrote:
> > 
> > > Hi all,
> > > 
> > > Since we did an upgrade to BIND 9.2 we have one record that keeps
> failing
> > > and strangely enough its on our primairy DNS. The slave just resolves it
> > > fine. What could be the case here?
> > > 
> > > Regards,
> > > Rob
> > 
> > You'll need to provide more details, we're not mind readers.
> > 
> > Have you checked your log to see if the master complains about the line 
> > when it's loading the zone file?

-- 
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***