migration bind9 flat file to DLZ

[Amitay Isaacs]

Hi Andreas,

On Thu, Feb 16, 2012 at 12:37 AM, Andreas Oster <aoster at novanetwork.de> wrote:
> Am 09.02.2012 09:23, schrieb Amitay Isaacs:
>> On Thu, Feb 9, 2012 at 7:12 PM, Andreas Oster <aoster at novanetwork.de> wrote:
>>> Hi Amitay,
>>>
>>> Am 09.02.2012 08:54, schrieb Amitay Isaacs:
>>>> Hi Andreas,
>>>>
>>>> On Thu, Feb 9, 2012 at 6:41 PM, Andreas Oster <aoster at novanetwork.de> wrote:
>>>>
>>>>> now the upgradedns script completed without any errors. The bind9 demon
>>>>> could
>>>>> load the data but something seems to be wrong. I am not allowed to edit the
>>>>> novanetwork.loc Forward Lookup Zone.  In DNS administration tool I get the
>>>>> following
>>>>> error when selecting "novanetwork.loc": Zone not loaded by DNS Server
>>>>> The rest seems to be OK.
>>>>>
>>>>> Thank you for your great efforts and kind help.
>>>>>
>>>>> best regards
>>>>>
>>>>> Andreas
>>>>>
>>>> I am assuming that you are using relatively recent source from git master for
>>>> running samba. Can you see the records from the zone in dns management
>>>> tool?
>>>>
>>>> Are you able to run samba-tool dns commands? For example,
>>>>
>>>>    samba-tool dns serverinfo <server> -U administrator%<password>
>>>>    samba-tool dns zonelist <server> -U administrator%<password>
>>>>
>>>> If the above commands fail, you might be running older version of samba
>>>> without RPC dnsserver support.
>>>>
>>>> Amitay
>>> I think there are some more issues.
>>> dc, and gc in the _msdcs.novanetwork.loc tree are grey and there are no
>>> entries visable.
>>> domains and pdc are populated
>>>
>>> best regards
>>>
>>> Andreas
>>>
>>
>> This is a known issue. If you refresh, the entries get fixed. But I haven't
>> been able to figure out the cause of this.
>>
>> Amitay.
>>
> Hello Amitay,
>
> I have recognized that with Microsoft DNS we have _msdcs listed
> under the domain, in our case novanetwork.loc. When I use your
> upgradedns script to generate the DNS stuff for bind_dlz we get
> a seperate entry _msdcs.novanetwork.loc
>
> Is this on purpose or did something go wrong ?
>
> Thank you for your kind help.
>
> best regards
>
> Andreas
>

All _msdcs records are stored under ForestDnsZones. So you should be
able to see second forward zone as _msdcs.novanetwork.loc. In the zone
novanetwork.loc (under DomainDnsZones), there is a single _msdcs record,
which is a glue NS record.

Amitay.