In zones overview, serial shows 0 instead of correct serial number

[harkx]

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

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

[tuxis-ie]

Is this for all your zones or just one?

[harkx]

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

[tuxis-ie]

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

[harkx]

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.

[tuxis-ie]

Sorry that this took me so long.

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

[harkx]

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

according to pdnsutil check-zone:

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

[harkx]

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.

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.

[krombel]

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

[krombel]

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