[Samba] Bind9 Flat to Bind9 DLZ

[vikas]

yes i realized that there is something wrong with BIND9_FLATFILE while encountering with samba_upgradedns -h which doesn't show BIND9_FLATFILE

Any help on*drs repl*  not working i think it is pointing to wrong FQDN how do i correct that ?
> >/    Not able to to view replication.(samba-tool drs showrepl)
> />/
> />/
> />/    [root at dc2  <https://lists.samba.org/mailman/listinfo/samba>]# samba-tool drs showrepl (want to highlight the name which is
> />/  using to connect)
> />/
> />/  ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to
> />/  *dc2.ik.lan.mum* failed - drsException: DRS connection to dc2.ik.lan.mum
> />/  failed: (-1073741772, 'The object name is not found.')
> />/
> />/  File "/usr/local/samba/lib64/python2.6/site-packages/samba/netcmd/drs.py",
> />/  line 39, in drsuapi_connect
> />/
> />/  (ctx.drsuapi, ctx.drsuapi_handle, ctx.bind_supported_extensions) =
> />/  drs_utils.drsuapi_connect(ctx.server, ctx.lp, ctx.creds)
> />/
> />/  File "/usr/local/samba/lib64/python2.6/site-packages/samba/drs_utils.py",
> />/  line 54, in drsuapi_connect
> />/
> />/  raise drsException("DRS connection to %s failed: %s" % (server, e))
> />


> Welcome to the 'I have found a bug' club :-)
>
> Firstly though, it is 'BIND9_FLATFILE' not 'BIND9_FLAT' , not that this
> would have helped.
>
> If you run 'samba-tool domain provision --help' , amongst the output is
> this:
>
>     --dns-backend=NAMESERVER-BACKEND
>                           The DNS server backend. SAMBA_INTERNAL is the
> builtin
>                           name server (default), BIND9_FLATFILE uses
> bind9 text
>                           database to store zone information, BIND9_DLZ uses
>                           samba4 AD to store zone information, NONE skips the
>                           DNS setup entirely (not recommended)
>
> OK, this shows 'BIND9_FLATFILE', but if you run 'samba-tool domain join
> --help' , you will find this:
>
>     --dns-backend=NAMESERVER-BACKEND
>                           The DNS server backend. SAMBA_INTERNAL is the
> builtin
>                           name server (default), BIND9_DLZ uses samba4 AD to
>                           store zone information, NONE skips the DNS setup
>                           entirely (this DC will not be a DNS server)
>
> Whoops, 'BIND9_FLATFILE' has disappeared.
>
> I wouldn't think that using  'BIND9_FLATFILE' is a good idea, using this
> will store the dns info outside AD and what isn't in AD cannot be
> replicated.
>
> I actually think the bug is that 'samba-tool domain provision' will
> accept 'BIND9_FLATFILE'.
>
> Rowland