Re: Authoritative server recursing?

Daniele Orlandi <daniele@orlandi.com> wrote:

> Here is the strangeness:
>
> stef:~ # dig @vega -x 62.212.10.16 NS
>
> ; <<>> DiG 9.2.2 <<>> @vega -x 62.212.10.16 NS
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33042
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;16.10.212.62.in-addr.arpa. IN NS
>
> ;; ANSWER SECTION:
> 16.10.212.62.in-addr.arpa. 85140 IN NS
> mix.b-soft.com.16.10.212.62.in-addr.arpa.
> 16.10.212.62.in-addr.arpa. 85140 IN NS
> zagor.b-soft.com.16.10.212.62.in-addr.arpa.

You've missed the terminating '.' off the NS records in the
16.10.212.62.in-addr.arpa zone file:

IN NS mix.b-soft.com
IN NS zagor.b-soft.com

so they're being qualified with the zone name.

--
Ronan Flood <R.Flood@noc.ulcc.ac.uk>
working for but not speaking for
Network Services, University of London Computer Centre
(which means: don't bother ULCC if I've said something you don't like)