mirror of
https://github.com/tuxis-ie/nsedit.git
synced 2026-04-26 16:15:54 +03:00
[GH-ISSUE #111] Import a new zone feature #61
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
pull-request
question
question
upstream
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nsedit#61
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @skfigved on GitHub (Aug 31, 2016).
Original GitHub issue: https://github.com/tuxis-ie/nsedit/issues/111
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.
@ruben-herold commented on GitHub (Sep 9, 2016):
Here the same
@tuxis-ie commented on GitHub (Sep 9, 2016):
Sorry, missen this one. Will look into this Monday
@skfigved commented on GitHub (Sep 12, 2016):
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
@tuxis-ie commented on GitHub (Sep 13, 2016):
I can't reproduce this... Can you show me the zone and screenshots of when you are trying to do an import?
@skfigved commented on GitHub (Sep 13, 2016):
test123.com.txt
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.
If i import them with "overwrite nameservers" unticket. Then it works but i have to manually correct the nameservers to reflect the new ones
@skfigved commented on GitHub (Sep 13, 2016):
Here with screenshots
@bjoe2k4 commented on GitHub (Sep 17, 2016):
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.
@tuxis-ie commented on GitHub (Sep 17, 2016):
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?
@skfigved commented on GitHub (Sep 17, 2016):
Yes indeed the function is very useful, and i can sometimes do bulk imports of 20-30 zones at a time.
I do have trailing dots on the nameservers
@tuxis-ie commented on GitHub (Sep 17, 2016):
Multiple zones at a time? How do you do that?
@skfigved commented on GitHub (Sep 17, 2016):
Apologies, it was badly worded. Not multiple zones at a time. But importing them one at a time