Heads up that there’s a major change to the PR:
https://github.com/openwrt/packages/pull/14240
It adds support for “cname”, “domain”, “mxhost”, and “srvhost” config sections.
Thanks to Bjorn for pointing me at how to use nsupdate to do this.
Calling out run-time requirements on “named” and “ns
Responses…
> On Dec 17, 2020, at 1:56 AM, Bjørn Mork wrote:
>
> Philip Prindeville writes:
>
>> https://github.com/openwrt/packages/pull/14240
>>
>> The previous one is a precursor for getting Bind to start before DHCPD.
>
>
> That makes more sense yes.
>
> I looked at it briefly. A coupl
Philip Prindeville writes:
> https://github.com/openwrt/packages/pull/14240
>
> The previous one is a precursor for getting Bind to start before DHCPD.
That makes more sense yes.
I looked at it briefly. A couple of notes without testing:
I would not have used a key named "rdnc"-anything for z
> On Dec 16, 2020, at 12:59 AM, Bjørn Mork wrote:
>
> Philip Prindeville writes:
>>> On Dec 15, 2020, at 1:22 AM, Bjørn Mork wrote:
>>>
>>> Philip Prindeville writes:
>>>
I’m trying to do the integration “glue” to allow one to operate a DNS
private zone inside your intranet (aka
Philip Prindeville writes:
>> On Dec 15, 2020, at 1:22 AM, Bjørn Mork wrote:
>>
>> Philip Prindeville writes:
>>
>>> I’m trying to do the integration “glue” to allow one to operate a DNS
>>> private zone inside your intranet (aka “split horizon”) and prime it
>>> with both static data as well
> On Dec 15, 2020, at 1:22 AM, Bjørn Mork wrote:
>
> Philip Prindeville writes:
>
>> I’m trying to do the integration “glue” to allow one to operate a DNS
>> private zone inside your intranet (aka “split horizon”) and prime it
>> with both static data as well as DHCP lease information.
>
> “
Philip Prindeville writes:
> I’m trying to do the integration “glue” to allow one to operate a DNS
> private zone inside your intranet (aka “split horizon”) and prime it
> with both static data as well as DHCP lease information.
“split horizon” is a very bad idea, and should not be encouraged.
