Hi Peter,
thanks for your answer. I now understand better what happens.
It is not causing trouble, but we saw a weird behavior Friday and this
was one thing we noticed and did not understand.
Thanks for your patience.
Thomas
On 09/16/2013 09:14 AM, Peter van Dijk wrote:
Hello Thomas,
On Sep 13, 2013, at 15:41 , Thomas Mieslinger wrote:
+-----------+-----------+--------------------------------------+-------+---------------------------------------------------------------------------+-------+------+---------------------+
| id | domain_id | name | type |
content | ttl
| prio | change_date |
+-----------+-----------+--------------------------------------+-------+---------------------------------------------------------------------------+-------+------+---------------------+
| 160510155 | 2734 | _jabber._tcp.die-optimisten.net | SRV | 0 5269
jabber.gmx.net | 86400 |
5 | 2013-09-13 15:30:08 |
| 160510156 | 2734 | _xmpp-client._tcp.die-optimisten.net | SRV | 0 5222
jabber.gmx.net | 86400 |
5 | 2013-09-13 15:30:08 |
| 160510157 | 2734 | _xmpp-server._tcp.die-optimisten.net | SRV | 0 5269
jabber.gmx.net | 86400 |
5 | 2013-09-13 15:30:08 |
| 160510164 | 2734 | _tcp.die-optimisten.net | NULL | NULL
| NULL |
NULL | 2013-09-13 15:30:08 |
+-----------+-----------+--------------------------------------+-------+---------------------------------------------------------------------------+-------+------+---------------------+
19 rows in set (0.01 sec)
You see record id 160510164.
It wasn't in the axfr. I have longer zones with 20 to 40 NULL records which are
duplicates of real names. As long as the type is NULL the select will probably
not return them to powerdns, But select * from records where type is null;
returns 12561 rows :-(
How do I stop this?
This is new behaviour in 3.2, making sure we support Non-Empty Terminals
correctly. This is required to do DNSSEC correctly, and also, strictly
speaking, to do DNS correctly.
If you look carefully, you will see that they are not duplicates of real names
- they are shorter suffixes of real names, to make sure there are no 'gaps' in
the DNS tree.
Now, the question is - are these records causing you any trouble?
Kind regards,
_______________________________________________
Pdns-users mailing list
[email protected]
http://mailman.powerdns.com/mailman/listinfo/pdns-users
_______________________________________________
Pdns-users mailing list
[email protected]
http://mailman.powerdns.com/mailman/listinfo/pdns-users
