Kathy Zhu via FreeIPA-users wrote:
Hi List,
I created a PTR record "90.91" in "0.10.inaddr.arpa." zone via GUI,
then
found:
1, I can see the record via GUI
2, When I looked it up on the command line, I got "not found: 3(NXDOMAIN)".
How did you look?
3, Its dn is not in "ldapsearch -Y GSSAPI -b
idnsname=0.10.inaddr.arpa.,cn=dns,dc=example,dc=com" output.
You can add the target idnsname=90.91, e.g.
ldapsearch -Y GSSAPI -b
idnsname=0.10.inaddr.arpa.,cn=dns,dc=example,dc=com idnsname=90.91
Above 3 explained why the record could not be resolved. However, why
does this happen? I can see the record in GUI, where is this record?
I'm not a DNS expert by far, but this format looks a bit off. I tend to
be simplistic and have actual zones for each reverse, so I'd have
created 91.0.10.inaddr.arpa. and added 90 to it.
I was able to duplicate what you see though using the ##.## format.
So I don't know if what you're doing is wrong or if it's something in
bind-dyndb-ldap, but having discrete zones is a workaround.
rob
I created more PTR records for testing, they are all the same way -
can
be seen in GUI, but not resolvable and not in ldapsearch output.
Any idea for me to troubleshoot this?
Many thanks.
Kathy
_______________________________________________
FreeIPA-users mailing list -- freeipa-users(a)lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-leave(a)lists.fedorahosted.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedoraho...
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure