#135 Domain names with escaped characters are not visible in DNS
Opened by mbasti. Modified

Problem

  • What does not work as expected?

Escaped domain name doesn't appear in BIND.

  • Is your problem related to a single DNS zone or a DNS record?

No

Steps to Reproduce

  • Add new record to zone, ipa dnsrecord-add zonetest. 'test space' --a-rec=172.16.0.1

*# ipa dnsrecord-show zonetest. 'test space' --raw --all
dn: idnsname=test\032space,idnsname=zonetest.,cn=dns,dc=example,dc=com
idnsname: test\032space
arecord: 172.16.0.1
objectClass: top
objectClass: idnsrecord

  • dig -t ANY test\032space.zonetest.
  • NXDOMAIN returned by dig

Attach any error messages or other suspicious information you see in logs. E.g. in /var/named/data/named.run or /var/log/messages.
15-Apr-2014 18:01:56.008 failed to convert dn idnsname=test\5C032record,idnsname=zonetest.,cn=dns,dc=example,dc=com to DNS name: bad escape
15-Apr-2014 18:01:56.008 syncrepl_update failed for object 'idnsname=test\5C032record,idnsname=zonetest.,cn=dns,dc=example,dc=com': bad escape

Environment

  • Plugin version:

bind-dyndb-ldap-4.1-1.fc20.x86_64


This seems like corner case, it will be fixed when DNSSEC works somehow.

Do you mean: "will be fixed when DNSSEC works somehow" or "will be fixed after DNSSEC works somehow"? :-)

Replying to [comment:4 mkosek]:

Do you mean: "will be fixed when DNSSEC works somehow" or "will be fixed after DNSSEC works somehow"? :-)

Let's say that English is not my native language ;-)

Results of planning meeting held on 2014-11-04.

These tickets are not directly related to upcomming FreeIPA 4.4 features.

Moving tickets as triaged on 2016-02-11 with mkosek. These tickets are not going to be implemented without strong need/good justification.

I'm setting priority to 'critical' so these tickets stay on top of The Backlog bucket.

Metadata Update from @mbasti:
- Issue assigned to someone
- Issue set to the milestone: The Backlog

Log in to comment on this ticket.

Metadata