[GH-ISSUE #133] In zones overview, serial shows 0 instead of correct serial number #84

Closed
opened 2026-02-28 01:20:54 +03:00 by kerem · 9 comments
Owner

Originally created by @harkx on GitHub (Nov 2, 2016).
Original GitHub issue: https://github.com/tuxis-ie/nsedit/issues/133

Small display issue with the overview zones screen, it does not show the serial in the overview:

image

When "searching" however it does show the serial correctly:

image

Originally created by @harkx on GitHub (Nov 2, 2016). Original GitHub issue: https://github.com/tuxis-ie/nsedit/issues/133 Small display issue with the overview zones screen, it does not show the serial in the overview: ![image](https://cloud.githubusercontent.com/assets/7738282/19919449/2885256c-a0d3-11e6-8e35-700787b5ad14.png) When "searching" however it does show the serial correctly: ![image](https://cloud.githubusercontent.com/assets/7738282/19919490/73e580ec-a0d3-11e6-8eec-124abd939d11.png)
kerem 2026-02-28 01:20:54 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

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

Is this for all your zones or just one?

<!-- gh-comment-id:257795345 --> @tuxis-ie commented on GitHub (Nov 2, 2016): Is this for all your zones or just one?
Author
Owner

@harkx commented on GitHub (Nov 2, 2016):

It's for all zones, on my main overview they all show 0 as serial. When searching however it shows correctly.

image

<!-- gh-comment-id:257795882 --> @harkx commented on GitHub (Nov 2, 2016): It's for all zones, on my main overview they all show 0 as serial. When searching however it shows correctly. ![image](https://cloud.githubusercontent.com/assets/7738282/19920621/223fa6ee-a0da-11e6-872c-ea2ab871a825.png)
Author
Owner

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

Are you able to query the pdns API directly? I have the feeling this is a pdns issue.

<!-- gh-comment-id:258086536 --> @tuxis-ie commented on GitHub (Nov 3, 2016): Are you able to query the pdns API directly? I have the feeling this is a pdns issue.
Author
Owner

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

Yeah, sure, for the rest it's working, and it does show the serial correctly when I search a domain in nsedit, just not in the default overview screen.

If you want me to do a specific query, let me know, I'd be happy to test.

<!-- gh-comment-id:258087736 --> @harkx commented on GitHub (Nov 3, 2016): Yeah, sure, for the rest it's working, and it does show the serial correctly when I search a domain in nsedit, just not in the default overview screen. If you want me to do a specific query, let me know, I'd be happy to test.
Author
Owner

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

Sorry that this took me so long.

Can you show a SOA-record for which the serial is displayed incorrectly?

<!-- gh-comment-id:259916669 --> @tuxis-ie commented on GitHub (Nov 11, 2016): Sorry that this took me so long. Can you show a SOA-record for which the serial is displayed incorrectly?
Author
Owner

@harkx commented on GitHub (Nov 12, 2016):

Here's an example and indeed I think you're right, the SOA record is messed up:

image

according to pdnsutil check-zone:

image

Now to find out what's wrong.. I always created zones like this, also DNS queries don't error.

<!-- gh-comment-id:260107961 --> @harkx commented on GitHub (Nov 12, 2016): Here's an example and indeed I think you're right, the SOA record is messed up: ![image](https://cloud.githubusercontent.com/assets/7738282/20236391/1234c9d2-a8b4-11e6-9cda-f5fb5026c7f8.png) according to pdnsutil check-zone: ![image](https://cloud.githubusercontent.com/assets/7738282/20236413/9db913be-a8b4-11e6-8ac2-814d72917d37.png) Now to find out what's wrong.. I always created zones like this, also DNS queries don't error.
Author
Owner

@harkx commented on GitHub (Nov 14, 2016):

I must've checked the wrong zone last time with pdnsutil check-zone because when I do that for my domains, it gives correct results. Sorry for the mistake.

image

But the problem remains in the view though.. when searching a domain the results show the domain and the correct serial. When just in the default via (no search) it displays 0.

<!-- gh-comment-id:260279565 --> @harkx commented on GitHub (Nov 14, 2016): I must've checked the wrong zone last time with pdnsutil check-zone because when I do that for my domains, it gives correct results. Sorry for the mistake. ![image](https://cloud.githubusercontent.com/assets/7738282/20258349/86b321b8-aa4f-11e6-9ade-acb572ada40a.png) But the problem remains in the view though.. when searching a domain the results show the domain and the correct serial. When just in the default via (no search) it displays 0.
Author
Owner

@krombel commented on GitHub (Nov 28, 2016):

I found out, that the powerdns-API produced the wrong serial.

I got following response when fetching the API directly from powerdns:

curl -H "X-API-Key: MySecretAPI-Key" localhost:4321/api/v1/servers/localhost/zones | python -m json.tool
[
    {
        "account": "test",
        "dnssec": false,
        "id": "mydomain.tld.",
        "kind": "Master",
        "last_check": 0,
        "masters": [],
        "name": "mydomain.tld.",
        "notified_serial": 0,
        "serial": 0,
        "url": "api/v1/servers/localhost/zones/mydomain.tld."
    }
]

So this issue has to be fixed upstream

<!-- gh-comment-id:263260188 --> @krombel commented on GitHub (Nov 28, 2016): I found out, that the powerdns-API produced the wrong serial. I got following response when fetching the API directly from powerdns: ``` curl -H "X-API-Key: MySecretAPI-Key" localhost:4321/api/v1/servers/localhost/zones | python -m json.tool [ { "account": "test", "dnssec": false, "id": "mydomain.tld.", "kind": "Master", "last_check": 0, "masters": [], "name": "mydomain.tld.", "notified_serial": 0, "serial": 0, "url": "api/v1/servers/localhost/zones/mydomain.tld." } ] ``` So this issue has to be fixed upstream
Author
Owner

@krombel commented on GitHub (Nov 28, 2016):

And it seems to be an open issue already
PowerDNS/pdns#4328

The advice there: Disable (possibly empty) bind-backend
It solved the issue in my case altough it is just a workaround

<!-- gh-comment-id:263260909 --> @krombel commented on GitHub (Nov 28, 2016): And it seems to be an open issue already PowerDNS/pdns#4328 The advice [there](https://github.com/PowerDNS/pdns/issues/4328#issuecomment-257091810): Disable (possibly empty) bind-backend It solved the issue in my case altough it is just a workaround
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nsedit#84
No description provided.