Looks to be a "lame server" problem for "isc.org"

[Paul Vixie]

> Jun 30 19:45:43 Sun-E3000 named[21349]: Lame server on 'isc.org' (in
> 'isc.org'?): [198.151.248.183].53 'ns2.gnac.com'
> ...
> 1009 wwinzer at Sun-E3000:~ ==> dig @ns2.gnac.com. isc.org ns
> ...
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
> ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 13
> ...

fixed in the isc.org delegation.  we were pointing at ns2.gnac.com whereas
the server that was actually slaving isc.org was ns1.gnac.com.  these used
to be the same box so isc's erroneous delegation used to have no impact.

> Looks as if ns2.gnac.com isn't responding to any requests.
> ONE MORE TEST:
> 
> 1011 wwinzer at Sun-E3000:~ ==> dig @ns2.gnac.com. sgi.com. any
> ...
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
> ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 13

that's the right answer.  ns2.gnac.com runs with recursion disabled, and
it is not authoritative for that zone.  "dig @ns-ext.vix.com sgi.com ns"
produces the identical result.  there is nothing wrong with ns2.gnac.com;
if you ask it something it's configured to know the answer to, it will
tell you.  try "dig @ns2.gnac.com gnac.com ns" as an example.

> Thank GOD for multiple nameservers in different part of the world, eh
> ISC.ORG?

absolutely.  thanks for your report.