This 10.140.128.0/18 is an RFC1918 zone so he shouldn't have to worry
about what his ISP does. He can set this zone up in his resolver
and/or forward to his authoritative server. He could also setup a
stub zone in his resolver for this rfc1918 zone. He can make it work
since its internal only -
Darren Ankney wrote:
> AM Weisteen Per wrote:
>> I'm running a DNS server which is authoritative for an internal classless
>> subnet being 10.40.128.0/18 and defined in BIND as
>> 128-191.40.10.in-addr.arpa.
>> Is that notation also valid for KEA 2.0.3 ?
>> IE, may I use
>>
>>"revers
the ARM doesn't say it won't. It doesn't say it will either. I
looked around and was not able to find an RFC that specifies setting
up the domain the way you did. I found this one:
https://www.rfc-editor.org/rfc/rfc2317 that seems to suggest that
0/18.128.40.10.in-addr.arpa is a standard. I saw
Hi
I'm running a DNS server which is authoritative for an internal classless
subnet being 10.40.128.0/18 and defined in BIND as 128-191.40.10.in-addr.arpa.
Is that notation also valid for KEA 2.0.3 ?
IE, may I use
"reverse-ddns" : {
"ddns-domains": [
