AW: AW: nsupdate: A records (glue) in reverse zones

[Kevin Darcy]

Yeah, tell that to the "in bailiwick" weirdos who think that *every* 
delegation should be to an child-zone name. For the most part, they 
don't seem to have applied that "logic" to the in-addr.arpa tree so far, 
but if they ever get consistent, we could see some ugliness...

                                                                         
                  - Kevin

Kleinfeld, Ralf wrote:
> Kevin,
>
> not everything possible is reasonable,
>
> Best Regards,
> Ralf
>
>
> -----Ursprüngliche Nachricht-----
> Von: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] Im Auftrag von Kevin Darcy
> Gesendet: Freitag, 27. Oktober 2006 00:52
> An: bind-users at isc.org
> Betreff: Re: AW: nsupdate: A records (glue) in reverse zones
>
> Never say never. What's stopping someone from naming a nameserver ns1.96.130.in-addr.arpa, for instance? Reverse zones are not, after all,
> *inherently* different from any other kind of zones; A records and delegations are eminently permissible in the in-addr.arpa tree.
>
>                                                                          
>                - Kevin
>
> Kleinfeld, Ralf wrote:
>   
>> Hi,
>>
>> you won't need glue records in reverse zones, because the hostnames of 
>> the name server to which you delegate a subdomain will never be in the 
>> delegated zone.
>>
>> Best Regards,
>> Ralf
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] Im 
>> Auftrag von Sven Hergenhahn
>> Gesendet: Donnerstag, 26. Oktober 2006 14:11
>> An: bind-users at isc.org
>> Betreff: nsupdate: A records (glue) in reverse zones
>>
>> Hi everybody,
>>
>> the problem is that I am unable to create an A record in a reverse zone (for glue reasons).
>>
>> Here's what I tried:
>>
>> $ nsupdate -d
>>   
>>     
>>> zone 112.96.130.in-addr.arpa
>>> update add testarecord.my.domain.com. 900 IN A 130.96.112.13
>>>
>>>     
>>>       
>> Reply from SOA query:
>> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id:  24315 ;; flags: qr aa rd ra ; QUESTION: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION:
>> ;testarecord.my.domain.com.      IN      SOA
>>
>> ;; AUTHORITY SECTION:
>> my.domain.com.           0       IN      SOA     nameserver.other.domain.com 
>> unixadmin.other.domain.com. 397 900 420 604800 10800
>>
>> Found zone name: my.domain.com
>> The master is: nameserver.other.domain.com before getaddrinfo()
>>
>> Reply from update query:
>> ;; ->>HEADER<<- opcode: UPDATE, status: NOTZONE, id:  38866 ;; flags: 
>> qr ra ; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0
>>
>>
>> Apparently, the zone prereq is ignored. Is that not possible at all? Or can anybody  shed some light as to what I am doing wrong here.
>>
>> Thanks in advance,
>> Sven
>>
>>
>>
>>
>>
>>
>>   
>>     
>
>
>
>
>
>