Inconsistency at ns.ripe.net ?

[Arvid Carlander]

James,

Thanks - I will get in touch with hostmaster at ripe.net.

What puzzled me was that the ttl values for the ns listing from ns.ripe.net
remain the same across successive digs. I read this to mean that they were
not cached and therefore ns.ripe.net acted either as a master or slave -
either would make it authoritative, would it not?

; <<>> DiG 8.3 <<>> @ns.ripe.net 232.62.in-addr.arpa soa
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 2
;; QUERY SECTION:
;;      232.62.in-addr.arpa, type = SOA, class = IN

;; AUTHORITY SECTION:
232.62.in-addr.arpa.    5D IN NS        dns1lo.highwayone.net.
232.62.in-addr.arpa.    5D IN NS        dns2lo.highwayone.net.
232.62.in-addr.arpa.    5D IN NS        ns.ripe.net.

Is it not contradictory to list yourself in the authority section with a
full ttl while claiming not to be authoritative?

-Arvid

"James Raftery" <james-bind-users at now.ie> wrote in message
news:9eluhu$s38 at pub3.rc.vix.com...
>
> On Fri, May 25, 2001 at 07:39:39AM +0000, Arvid Carlander wrote:
> > If ns.ripe.net list themselves as authority for 232.62.in-addr.arpa,
should
> > they not be able to list the name servers for 17.232.62.in-addr.arpa in
> > their answer section?
>
> Hi Arvid,
>
> Yes, they should. But ns.ripe.net is not announcing 232.62.in-addr.arpa
> authoritatively. I'd suggest a mail to hostmaster at ripe.net pointing out
> that ns.ripe.net is lame for a /16 reverse zone.
>
> > ; <<>> DiG 8.3 <<>> @ns.ripe.net 17.232.62.in-addr.arpa. ns
> > ; (1 server found)
> > ;; res options: init recurs defnam dnsrch
> > ;; got answer:
> > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
> > ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 2
>
> The 'aa' flag is missing == not authoritative.
>
>