 |
I'd like to jump on here with a #metoo |
|
|
it may not be a bug, but misconfiguration can be fixed this way: tail -1 /etc/named/ipa-options-ext.conf ``` allow-recursion { any; }; ``` |
|
|
Yes, that is what I am doing too. But as you pointed out, it seems to have been added to RHEL IPA almost 10 years ago. Don't know if it got dropped along the way after that, or never added to CentOS iPA. |
|
|
Looks like this was removed in IPA 4.8. I don't know if that was accidental or on purpose. There is this. https://pagure.io/freeipa/issue/6363 |
|
|
and this https://bugzilla.redhat.com/show_bug.cgi?id=1319404#c2 |
|
|
this is the commit that removed: https://pagure.io/freeipa/c/a5cbdb57e50cfc62f61affda19ce878b2abd33de?branch=master |
|
|
sorry, it is thus one: https://pagure.io/freeipa/c/6c2710446718828e6840ac34ea6fc704ae6790db?branch=master |
|
|
I guess, my description was not right after all, it supposed to be like this for local trusted networks: allow-recursion {trusted_network;localnets;}; though, when querying ipa named for PTR, it returns an empty record host@10.1.1.2# dig a google.com @192.168.0.2 so basically, what was removed, it disallows recursion queries even for localnets :/ |
|
|
Both commands return empty answers: ``` host@10.1.1.2# dig a one.one.one.one @192.168.0.2 host@10.1.1.2# dig -x 1.1.1.1 @192.168.0.2 ``` |
- Anonymous
