Here is the above with correct formatting:

# cat >> /etc/dhcp/dhclient-enter-hooks <<EOF
make_resolv_conf() {
    :
    # skip when using IPA
}
EOF
# chmod +x /etc/dhcp/dhclient-enter-hooks

AND

# edit /etc/NetworkManager/NetworkManager.conf
# add dns=none to the [main] section

Triage discussion:

rcrit: I believe we document that the IPA server should have a static IP but I don't know if we state that this static IP should not come from DHCP, or the possible repercussions if it does.
D.P. 4.2. It will become a more important issue when we focus on the automated deployment.

Processing leftovers from 4.2 backlog - this ticket was found as suitable for consideration in next big feature release - 4.4.

Overwriting resolv.conf should not break anyone's DNS. If it does, then he already has broken configuration in some way.

Also, the proposed fix is very specific to internal implementation details of
current NetworkManager-DHCP integration and will not work in containers (with networkd)
and in later Fedoras (with resolv.conf managed by dnssec-trigger daemon).

For these reasons it seems that FreeIPA is not the right place to fix it.