Re: Reverse lookup for classless networks

2018-12-27 Thread Grant Taylor via bind-users
It has come to my attention that my answer to the following question might not have been clear. So I'll try again. First I want to be clear that I was discussing what the records should be, RFC 2317 Classless IN-ADDR.ARPA Delegation (read: CNAME) or standard NS delegation. I don't care how

Re: Reverse lookup for classless networks

2018-12-27 Thread Grant Taylor via bind-users
On 12/27/18 12:14 PM, John Levine wrote: Well, yeah, like I said it's wrong but you can often get away with it. }:-) I'll admit that it's not 100% proper. The DNS specs are a mess and the SOA at the top is poorly described in 1034 and 1035 (as is a lot of other stuff.) You'll definitely

Re: Reverse lookup for classless networks

2018-12-27 Thread John Levine
In article you write: >-=-=-=-=-=- > >On 12/27/18 11:24 AM, John Levine wrote: >> Well, there's those pesky old DNS standards, but we're used to software >> working around screwed up zones. > >Agreed. Which standard(s) does this run afoul of? > >> If the parent delegates a name to a child

Re: Reverse lookup for classless networks

2018-12-27 Thread Grant Taylor via bind-users
On 12/27/18 11:24 AM, John Levine wrote: Well, there's those pesky old DNS standards, but we're used to software working around screwed up zones. Agreed. Which standard(s) does this run afoul of? If the parent delegates a name to a child server, the child server must have an SOA at that

Re: Reverse lookup for classless networks

2018-12-27 Thread John Levine
From: John Levine To: bind-users@lists.isc.org Subject: Re: Reverse lookup for classless networks In-Reply-To: Organization: Taughannock Networks Cc: gtay...@tnetconsulting.net Bcc: johnl-sent X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding

Re: Reverse lookup for classless networks

2018-12-27 Thread Grant Taylor via bind-users
On 12/27/18 9:01 AM, Barry Margolin wrote: The alternative is to have a separate zone for each address, and delegate each of them to your server. So the parent zone would have: It does not require a separate zone for each address. But it does require some creative zone work. ;

Re: Reverse lookup for classless networks

2018-12-27 Thread Barry Margolin
In article , Nagesh Thati wrote: > Thanks Mark, > But is there any other way without using any CNAMEs? The alternative is to have a separate zone for each address, and delegate each of them to your server. So the parent zone would have: 0 IN NS ns1.yourdomain.com. IN NS ns2.yourdomain.com.

Re: Reverse lookup for classless networks

2018-12-27 Thread Nagesh Thati
Thanks Mark, But is there any other way without using any CNAMEs? On Thu, Dec 27, 2018 at 4:45 PM Mark Andrews wrote: > Because it requires the parent zone with the CNAME records to also be set > up which maps the well known query names to the alternate names. > > > -- > Mark Andrews > > On 27

Re: Reverse lookup for classless networks

2018-12-27 Thread Mark Andrews
Because it requires the parent zone with the CNAME records to also be set up which maps the well known query names to the alternate names. -- Mark Andrews > On 27 Dec 2018, at 21:01, Nagesh Thati wrote: > > Hello, > I have been trying to make the reverse zones for the classless networks. I

Reverse lookup for classless networks

2018-12-27 Thread Nagesh Thati
Hello, I have been trying to make the reverse zones for the classless networks. I was able to create such zones by following an online guide. The guide says to create a reverse zone for a classless network as following, Network: *28.0.0.0/27 * Reverse Zone: