On Sun, 2021-12-26 at 14:16 -0500, Dave Mintz via FreeIPA-users wrote: I have freeIPA with DNS over several replication instances running. The domains are like yours mostly internal and not to resolve externally. Without a lot of boring details, you do not need to register your TLD if you just use the domain internally. As long as the resolver your internal hosts point to is your authoritative DNS server that FreeIPA manages, the clients will get responses as they need. This requires your server not to just blindly forward all DNS externally. I have forward turned off on my domains. This means when a client requests a public DNS address, the bind server managed by FreeIPA will do a NS lookup to see where the request needs to be sent. It's not 1.1.1.1 or similar services doing that. Works great for a small network where your domain is 100% internal. You can have an external NS too and they can provide very different answers. Perhaps you just want MX to resolve externally but an ocean of internal addresses should not. If someone outside your network tries to resolve an address, they will hit the external resolver (not managed by FreeIPA!) and only resolve what it knows about.

Hi, the various settings are explained in DNS forward policies in IdM <https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/... . By default, the DNS server does not forward queries if they are related to a zone for which it is authoritative (=for zones listed in *ipa dnszone-find*). For other zones: - if they are defined as a forward zone (configured with *ipa dnsforwardzone-add*), the zone forwarder/policy is used - if they are not defined as a forward zone, the general configuration applies (global forwarder and global policy or per-server forwarder and policy if they exist). flo On Mon, Dec 27, 2021 at 5:40 AM Dave Mintz via FreeIPA-users < freeipa-users(a)lists.fedorahosted.org&gt; wrote:

Hi Rafael What is not clear to me is how to integrate FreeIPA with a real public DNS domain, which I think is what Dave is referring to as he mentioned he owns a legitimate domain. In any case, AFAIK we're not supposed to use made up domains for internal DNS anymore ... I see the docs talk about server.idm.example.com - presumably example.com is supposed to be some legitimate DNS domain and idm.example.com is a delegated subdomain, although this doesn't appear to be explained. Microsoft docs talk about using delegated subdomains of legitimate public DNS domains for internal corporate DNS, which is what got me into this train of thought in the first place. Delegating a subdomain to a private IP (your internal DNS server) and hiding that delegation with a split view on your public DNS is one way of hiding the subdomain from public view whilst keeping all your private DNS data private and hosted/managed in house. Whether you use FreeIPA's DNS for internally hosting idm.example.com or not is a matter of choice I suppose. Whilst I'm here and at the opposite end of this topic, I run bad.domain for our FreeIPA DNS domain (going back years to the original installation) with the realm BAD - I'm getting a bit uncomfortable about this configuration and wondered if I'll drop out of support at some point - any thoughts on that? (I surely can't be the only one!) I haven't used FreeIPA's DNS. Thanks Angus ________________________________ From: Rafael Jeffman via FreeIPA-users <freeipa-users(a)lists.fedorahosted.org&gt; Sent: Monday, 27 December 2021, 1:31 pm To: FreeIPA users list Cc: Dave Mintz; Peter Larsen; Rafael Jeffman Subject: [Freeipa-users] Re: DNS and FreeIPA Sorry for the top reply, but this is more an overview about all messages than a direct answer. Everything here assumes you are using FreeIPA's integrated DNS. First, it was suggested that split view DNS is used. Don't do that, as it is not supported by FreeIPA. Use it only if you manage your own external DNS, without using FreeIPA to manage entries. Regarding forwarding DNS queries, the easiest way is to set a global forwarder. In my home lab I use public ones, like Google and Cloudflare, and I'm not much concerned about external traffic, so I leave the default configuration, "forward first", enabled. You can find more information about the available options here: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/... A lot more about working with DNS can be found https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/... Regards, Rafael On Mon, Dec 27, 2021 at 1:40 AM Dave Mintz via FreeIPA-users <freeipa-users@lists.fedorahosted.org<mailto:freeipa-users@lists.fedorahosted.org>> wrote: Hi Peter, Thank you so much! Could you please elaborate on how to configure the FreeIPA DNS server to forward only non-local-domain queries? In the DNS Global Configuration there is the Forward policy Forward first Forward only Forwarding disabled Which one should be used to do what you say below? Do I need to set a Global forwarder? Best, Dave _______________________________________________ FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org<mailto:freeipa-users@lists.fedorahosted.org> To unsubscribe send an email to freeipa-users-leave@lists.fedorahosted.org<mailto:freeipa-users-leave@lists.fedorahosted.org> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/<https://... List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines<https://emea01.... 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<https://emea01.safelinks.prote... -- Rafael Guterres Jeffman Senior Software Engineer FreeIPA - Red Hat