This looks like a bug in the import process. Until I fix it in the next
release, you could work around it by entering the domain names in the
in-addr.arpa format.
- Jamie
On Wed, 2005-06-29 at 22:16, Martin Mewes wrote:
> Hi all,
>
> did anyone ever tried this one here?
>
> If you batch-import something like this
>
> 172.22.0.5:master
> 172.22.0.6:master
> 172.22.0.7:master
> 172.22.0.8:master
>
> to the DNS-Server it should create zones for
>
> 254.50.22.172.in-addr.arpa. (etc)
>
> Instead it creates
>
> 254.50.22.172.in-addr.arpa.. (etc)
> ---------------------------^ (see the additional dot)
>
> which makes the zone not usable.
>
> If you add that zone manually everything is correct.
>
> bis dahin/kind regards
>
> Martin Mewes
|
