[GH-ISSUE #129] nameserver with 2500+ records takes a while for loading in nsedit. #79

New issue

Open

opened 2026-02-28 01:20:53 +03:00 by kerem · 2 comments

kerem commented

2026-02-28 01:20:53 +03:00

Owner

Originally created by @vandalon on GitHub (Oct 18, 2016).
Original GitHub issue: https://github.com/tuxis-ie/nsedit/issues/129

When using nsedit on a pdns server with 2500+ domains and 40K+ records nsedit needs more then a minute to load. Probably because nsedit loads all zones and records at once :)

Originally created by @vandalon on GitHub (Oct 18, 2016). Original GitHub issue: https://github.com/tuxis-ie/nsedit/issues/129 When using nsedit on a pdns server with 2500+ domains and 40K+ records nsedit needs more then a minute to load. Probably because nsedit loads all zones and records at once :)

kerem added the

question

upstream

labels

2026-02-28 01:20:53 +03:00

kerem commented

2026-02-28 01:20:54 +03:00

Author

Owner

@tuxis-ie commented on GitHub (Nov 3, 2016):

I know there has been progress on this, outside nsedit. Can you share the update?

@tuxis-ie commented on GitHub (Nov 3, 2016): I know there has been progress on this, outside nsedit. Can you share the update?

kerem commented

2026-02-28 01:20:54 +03:00

Author

Owner

@vandalon commented on GitHub (Nov 3, 2016):

There has been a change in the API-code within pdns which fixes this issues. But this is not (yet) in production. Furthermore this change in the api disables dns-sec checking when listing all zones.

@vandalon commented on GitHub (Nov 3, 2016): There has been a change in the API-code within pdns which fixes this issues. But this is not (yet) in production. Furthermore this change in the api disables dns-sec checking when listing all zones.