Sorry, this is going to be a pedantic post, so I might as well start
here:
> Subject: Re: DNS reverse sub delegation NXDOMAIN problem, Class C
No, there's no such thing as "Class C", so please forget that. It's
a /24 network. CIDR is in; class is dismissed.
On Tue
On 19.08.14 11:54, Bazy V wrote:
One post said 220/24 is not the correct format,
Another post said that is the format.
no post said this.
Not sure which one is correct.
220.20.172.IN-ADDR.ARPA is the correct zone into which to put PTR records.
Setting 220NSns2.sub.
C PTR file.
Message: 2
Date: Tue, 19 Aug 2014 13:37:08 +0100
From: Phil Mayers
To: bind-users@lists.isc.org
Subject: Re: DNS reverse sub delegation NXDOMAIN problem, Class C
Message-ID: <53f344f4.3010...@imperial.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 19/
On 19/08/14 13:12, Bazy V wrote:
$ORIGIN 20.172.IN-ADDR.ARPA.
0.220/24 NS ns2.sub.test.com
On 19.08.14 13:37, Phil Mayers wrote:
You don't need to do this. You just need:
$ORIGIN 20.172.IN-ADDR.ARPA.
220 NS ns2.sub.test.com.
RFC 2317 is only need for /25 and longer.
... and it e
Hi Bazy
On Tue, Aug 19, 2014 at 08:12:58AM -0400, Bazy V wrote:
> so I set up the following in my reverse file for ns2.sub.test.com domain
> ---
> $ORIGIN 20.172.IN-ADDR.ARPA.
>
>NS ns1.test.com
> 0.220/24 NS ns2.sub.test.com
> 43.222
On 19/08/14 13:12, Bazy V wrote:
$ORIGIN 20.172.IN-ADDR.ARPA.
0.220/24 NS ns2.sub.test.com
You don't need to do this. You just need:
$ORIGIN 20.172.IN-ADDR.ARPA.
220 NS ns2.sub.test.com.
RFC 2317 is only need for /25 and longer.
___
Plea
6 matches
Mail list logo
