-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import a new zone feature #111
Comments
Here the same |
Sorry, missen this one. Will look into this Monday |
I have managed to go around the issue by deleting the NS records before zone import. Not selecting "overwrite nameservers" and just adding these manually after import |
I can't reproduce this... Can you show me the zone and screenshots of when you are trying to do an import? |
I have uploaded a sample zone i just created. If i import the zone with "overwrite nameservers" ticket it will just set up a blank zone. |
i can confirm this as well, however i don't see it as such big of a problem. In any case you have to type new nameservers, either before or after adding the zone. I would actually recommend to remove the entire feature to overwrite the nameservers. |
I haven't had time to reproduce it yet, but I assume that one usually uses this function when you migrate a zone from other name servers to your, which are usually the same. So the function is very useful. One thing, do your name servers have trailing dots? |
Yes indeed the function is very useful, and i can sometimes do bulk imports of 20-30 zones at a time. |
Multiple zones at a time? How do you do that? |
Apologies, it was badly worded. Not multiple zones at a time. But importing them one at a time |
Seems this fnction stopped working after updating to 4.01 and nsedit from master branch.
It does not throw any error message, but simply just sets up a blank zone with just the nameservers and SOA. Unable to import any records.
The text was updated successfully, but these errors were encountered: