A new problem of TTL in a RRset

NSD
1

Using nsd with the '.hu' domain, I get a problem:

error: ttl doesn't match the ttl of the rrset in secondary/hu, line 516218

(error repeated many times)

At the given line, I have:

$ORIGIN vivanet.hu. <<< line 516217
radius 171456 IN A 145.236.239.1 <<< line 516218

What is wrong with the TTL of the glue? How can I work around that?

It was not detected before because nsd slurped the '.hu' zone file
through a BIND 8 server which apparently fixed the TTL (I got 86400
instead of the above). If I take the zone file directly from
193.6.206.118, nsd complains :frowning:

nsd 1.2.2 on Tru64 5.1B.

2

Once Stephane Bortzmeyer wrote:

Using nsd with the '.hu' domain, I get a problem:

error: ttl doesn't match the ttl of the rrset in secondary/hu, line 516218

(error repeated many times)

At the given line, I have:

$ORIGIN vivanet.hu. <<< line 516217
radius 171456 IN A 145.236.239.1 <<< line 516218

What is wrong with the TTL of the glue? How can I work around that?

That means that there's another radius A record somewhere with a different
ttl and that is not allowed. try grep ^radius secondary/hu to see what record
causes trouble. (Apparently it appears somewhere else as duplicate glue with
a different ttl)

Alexis

3

a message of 20 lines which said:

That means that there's another radius A record somewhere with a different
ttl and that is not allowed. try grep ^radius secondary/hu to see what record
causes trouble.

OK, I get it, same origin, many records:

$ORIGIN vivanet.hu.
radius 171471 IN A 145.236.239.1
...
$ORIGIN vivanet.hu.
radius 171470 IN A 145.236.239.1

Other domains has the problem, I'll check with them. Many thanks.

4

a message of 17 lines which said:

OK, I get it, same origin, many records:

$ORIGIN vivanet.hu.
radius 171471 IN A 145.236.239.1

Problem fixed upstream by switching from BIND8 to BIND9. Apparently,
the primary was polluted by the results of some queries and happily
transmitted it to the secondaries :frowning: