so I've narrowed the problem down. installing pure freeipa is working just
fine. My problems start arising after I add dns proxy to katello:
https://docs.theforeman.org/3.5/Installing_Server/index-katello.html#configuring-external-idm-dns_foreman.
I have 4 ipa servers 1 master 3 replicas, each r
here is the named.service log
Mar 31 13:29:52 mserver001p.test.domain.com systemd[1]: Starting Berkeley
Internet Name Domain (DNS)...
░░ Subject: A start job for unit named.service has begun execution
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ A start job for unit
its getting weirder and weirder ... really speechless
[lessfoobar@rserver003p ~]$ ssh rserver003p.test.domain.com
Web console: https://rserver003p.test.domain.com:9090/ or
https://192.168.0.24:9090/
Last login: Thu Mar 30 21:48:04 2023 from 192.168.66.66
[lessfoobar@rserver003p ~]$ host mserver
Hi thanks for checking my thread out,
> This is listing records for zone 'int.domain.com'.
This is my mistake while changing the domain for the post. I've missed this
part. you can safely ignore
> Do you have reverse records (PTR) in place? What are the records for zone
> '0.168.192.in-addr.arp
rcrit suggested to add those records also:
ipa dnszone-find
Zone name: 168.192.in-addr.arpa.
Active zone: True
Authoritative nameserver: mserver001p.test.domain.com.
Administrator e-mail address: hostmaster.test.domain.com.
SOA serial: 1680032832
SOA refresh: 3600
SOA retry: 900
SO
Hi,
On Tue, Mar 28, 2023 at 12:23 PM Anonymous via FreeIPA-users
wrote:
>
> So for the last week I'm having trouble with my DNS. It is not working as
> expected and is giving me all sort of headaches. I have 4 ipa servers and 4
> clients. This is test env for evaluation purposes and I wan't to
On 5/22/19 3:55 PM, Kristian Petersen via FreeIPA-users wrote:
When I say it won't resolve, I am getting NXDOMAIN as the result of the
query like this:
[root@ipa3 /]# nslookup ipa1 ipa3
Server: ipa3
Address: xxx.xxx.xxx.xxx#53
** server can't find ipa1: NXDOMAIN
Running journal
When I say it won't resolve, I am getting NXDOMAIN as the result of the
query like this:
[root@ipa3 /]# nslookup ipa1 ipa3
Server: ipa3
Address:xxx.xxx.xxx.xxx#53
** server can't find ipa1: NXDOMAIN
Running journalctl -u named-pkcs11 shows a ton of lines like the following:
May 2
Kristian Petersen via FreeIPA-users wrote:
> Hey all,
>
> I am using IPA for my DNS and have 3 total servers in the group. 2 of
> them are responding to queries just fine, but the 3rd (which is bare
> metal, not a VM like the others) is not resolving the queries issued to
> it. Running ipactl st
