[Pdns-users] Autodiscover SRV Record splitting hairs :)
s.posner at telekom.de
Fri Nov 1 10:46:56 UTC 2013
> > All records transfer just
> > fine...except for the Autodiscover SRV record. The record itself
> > registers correctly:
> > _autodiscover._tcp.testing29.com SRV 0 443
> > autodiscovery.testing29.com 14400 0
> > but...Powerdns splits the SRV record and produces an extra record/row
> > in the database, with only the id, domain id, name and type filled
> > in:
> > _tcp.test1.testing29.com A NULL NULL NULL NULL
> > Is there a remedy for this? If not, what would be a cron-compatible
> > Mysql command to delete those unwanted records from the database as
> > the Mysql root user?
> That is a normal record created/needed to support DNSSEC. Please do
> not delete it. I was concerned the first time I saw them because I
> thought the AXFR process was broken by a patch that I had written.
Right; to be more precise, these records are created by
the query bearing the much-telling name
That is exactly what is done here: If in domain X you have a record
Z.Y.X, there is a "virtual" subdomain Y implicitly created
within X - the query just "materializes" this nonexistent
subdomain in the backend for DNSSEC purposes.
On a side note - It seems you got some mangling wrong
_autodiscover._tcp.testing29.com SRV [...]
_tcp.testing29.com NULL NULL NULL NULL
_tcp.test1.testing29.com A NULL NULL NULL NULL
There is nowhere it could pull the "test1" part from,
and type (where you put the "A") is one of the four
columns set to NULL when this occurs.
That's why everyone is asked to send unmangled information.
Or you ran into something entirely unrelated to DNSSEC/empty-non-terminal.
Mit freundlichen Grüßen,
Deutsche Telekom AG, Products & Innovation
"Es hat einmal einer gesagt, das geht nicht. Dann kam einer, der wusste das nicht und hat es einfach gemacht"
More information about the Pdns-users