starred/nsedit

Fork 0

mirror of https://github.com/tuxis-ie/nsedit.git synced 2026-04-26 16:15:54 +03:00

[GH-ISSUE #37] bug: priority missing in "record create" request #16

New issue

Closed

opened 2026-02-28 01:20:34 +03:00 by kerem · 6 comments

kerem commented

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

Owner

Originally created by @EugenMayer on GitHub (Mar 11, 2015).
Original GitHub issue: https://github.com/tuxis-ie/nsedit/issues/37

pdns 3.4 / postgresql

The current pdwn schema requires a priority parameter - it should be at least part of the request priority:0 .. otherwise an API error will stop people for create records using the ui.

Originally created by @EugenMayer on GitHub (Mar 11, 2015). Original GitHub issue: https://github.com/tuxis-ie/nsedit/issues/37 pdns 3.4 / postgresql The current pdwn schema requires a priority parameter - it should be at least part of the request priority:0 .. otherwise an API error will stop people for create records using the ui.

kerem

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

closed this issue
added the
wontfix
label

kerem commented

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

Author

Owner

@tuxis-ie commented on GitHub (Mar 11, 2015):

Hi,

It wasn't that easy removing the priority field. Is has been removed a few weeks ago. You (and me as well ;)) need to upgrade our nameservers.

Mark Schouten
Tuxis Internet Engineering
mark@tuxis.nl / 0318 200208

On 11 Mar 2015, at 08:08, "Eugen Mayer" notifications@github.com wrote:

pdns 3.4 / postgresql

The current pdwn schema requires a priority parameter - it should be at least part of the request priority:0 .. otherwise an API error will stop people for create records using the ui.

—
Reply to this email directly or view it on GitHub.

@tuxis-ie commented on GitHub (Mar 11, 2015): Hi, It wasn't that easy removing the priority field. Is has been removed a few weeks ago. You (and me as well ;)) need to upgrade our nameservers. ## Mark Schouten Tuxis Internet Engineering mark@tuxis.nl / 0318 200208 > On 11 Mar 2015, at 08:08, "Eugen Mayer" notifications@github.com wrote: > > pdns 3.4 / postgresql > > The current pdwn schema requires a priority parameter - it should be at least part of the request priority:0 .. otherwise an API error will stop people for create records using the ui. > > — > Reply to this email directly or view it on GitHub.

kerem commented

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

Author

Owner

@EugenMayer commented on GitHub (Mar 11, 2015):

Well at least, its still official: https://doc.powerdns.com/md/authoritative/backend-generic-mypgsql/ .. http://goo.gl/3ue0Cz .. not sure on which version you are currently focusing, but basically nobody will able to use your frontend right now

@EugenMayer commented on GitHub (Mar 11, 2015): Well at least, its still official: https://doc.powerdns.com/md/authoritative/backend-generic-mypgsql/ .. http://goo.gl/3ue0Cz .. not sure on which version you are currently focusing, but basically nobody will able to use your frontend right now

kerem commented

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

Author

Owner

@tuxis-ie commented on GitHub (Mar 11, 2015):

The documentation is behind. The current pdns version (3.4.2) does not support the priorityfield. One of the writers of the pdns api actually wrote the patch for nsedit to remove it.

Mark Schouten
Tuxis Internet Engineering
mark@tuxis.nl / 0318 200208

On 11 Mar 2015, at 08:39, "Eugen Mayer" notifications@github.com wrote:

Well at least, its still official: https://doc.powerdns.com/md/authoritative/backend-generic-mypgsql/ .. http://goo.gl/3ue0Cz .. not sure on which version you are currently focusing, but basically nobody will able to use your frontend right now

—
Reply to this email directly or view it on GitHub.

@tuxis-ie commented on GitHub (Mar 11, 2015): The documentation is behind. The current pdns version (3.4.2) does not support the priorityfield. One of the writers of the pdns api actually wrote the patch for nsedit to remove it. ## Mark Schouten Tuxis Internet Engineering mark@tuxis.nl / 0318 200208 > On 11 Mar 2015, at 08:39, "Eugen Mayer" notifications@github.com wrote: > > Well at least, its still official: https://doc.powerdns.com/md/authoritative/backend-generic-mypgsql/ .. http://goo.gl/3ue0Cz .. not sure on which version you are currently focusing, but basically nobody will able to use your frontend right now > > — > Reply to this email directly or view it on GitHub.

kerem commented

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

Author

Owner

@EugenMayer commented on GitHub (Mar 11, 2015):

wow .. you are fast moving.. :) Not sure if that is the right strategy though - i will have to remove nsedit in this case, since debians backport-repos have 3.4.1

I undestand, that you dont want legacy code or maintain legacy features. Thanks

@EugenMayer commented on GitHub (Mar 11, 2015): wow .. you are fast moving.. :) Not sure if that is the right strategy though - i will have to remove nsedit in this case, since debians backport-repos have 3.4.1 I undestand, that you dont want legacy code or maintain legacy features. Thanks

kerem commented

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

Author

Owner

@tuxis-ie commented on GitHub (Mar 11, 2015):

You can always get the latest pdns version from their website. If you're waiting for Debian you'd be able to use nsedit somewhere in 2035 ;) maybe @habbie can set up an actual working apt-get-able archive somewhere.

On a serious note, the pdns API is highly experimental, as such, kinda so is the nsedit feature set. I'm hoping for maturity in pdns soon, but have little (or just no) influence on that.

Mark Schouten
Tuxis Internet Engineering
mark@tuxis.nl / 0318 200208

On 11 Mar 2015, at 08:45, "Eugen Mayer" notifications@github.com wrote:

wow .. you are fast moving.. :) Not sure if that is the right strategy though - i will have to remove nsedit in this case, since debians backport-repos have 3.4.1

I undestand, that you dont want legacy code or maintain legacy features. Thanks

—
Reply to this email directly or view it on GitHub.

@tuxis-ie commented on GitHub (Mar 11, 2015): You can always get the latest pdns version from their website. If you're waiting for Debian you'd be able to use nsedit somewhere in 2035 ;) maybe @habbie can set up an actual working apt-get-able archive somewhere. On a serious note, the pdns API is highly experimental, as such, kinda so is the nsedit feature set. I'm hoping for maturity in pdns soon, but have little (or just no) influence on that. ## Mark Schouten Tuxis Internet Engineering mark@tuxis.nl / 0318 200208 > On 11 Mar 2015, at 08:45, "Eugen Mayer" notifications@github.com wrote: > > wow .. you are fast moving.. :) Not sure if that is the right strategy though - i will have to remove nsedit in this case, since debians backport-repos have 3.4.1 > > I undestand, that you dont want legacy code or maintain legacy features. Thanks > > — > Reply to this email directly or view it on GitHub.

kerem commented

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

Author

Owner

@EugenMayer commented on GitHub (Mar 11, 2015):

Well no offense at all - i get your point. Iam basically writing a small ruby / httpparty cli to do what i actually need. NSedit will become read-only browsing for now

@EugenMayer commented on GitHub (Mar 11, 2015): Well no offense at all - i get your point. Iam basically writing a small ruby / httpparty cli to do what i actually need. NSedit will become read-only browsing for now