This is a text-only version of the following page on https://raymii.org:
---
Title : FreeIPA DNS workaround for DNS zone [...]. already exists in DNS and is handled by server(s):
Author : Remy van Elst
Date : 10-04-2018
URL : https://raymii.org/s/snippets/FreeIPA_DNS_workaround_for_DNS_zone_already_exists_in_DNS_and_is_handled_by_servers.html
Format : Markdown/HTML
---
Recently I ran into an issue with FreeIPA when trying to add an existing DNS
zone. The zone already exists on the internet so, logically, FreeIPA wouldn't
allow me to hijack this domain locally. My usecase is special, so I wanted to
forcefully add this zone as a forward zone.
Recently I removed all Google Ads from this site due to their invasive tracking, as well as Google Analytics. Please, if you found this content useful, consider a small donation using any of the options below:
I'm developing an open source monitoring app called Leaf Node Monitoring, for windows, linux & android. Go check it out!
Consider sponsoring me on Github. It means the world to me if you show your appreciation and you'll help pay the server costs.
You can also sponsor me by getting a Digital Ocean VPS. With this referral link you'll get $200 credit for 60 days. Spend $25 after your credit expires and I'll get $25!
In the web UI of FreeIPA when trying to add this existing zone, the following
error appears:
DNS zone example.org. already exists in DNS and is handled by server(s): ns1.kpn.com, ns2.kpn.com
This is a logical error since hijacking a domain like this is a bad idea,
features like DNSSEC will bite you.
My setup however was different. In this setup, domain `sub.example.org` was
delegated to this environment, but via some tunneling constructions VPSes in
this environment would be able to connect internally to the `example.org`
domain. So, I want the FreeIPA system that is also the DNS resolver, to forward
queries for `example.org` to the local internal nameserver in the `example.org`
domain, and not resolving them externally.
FreeIPA wouldn't let me do that via the GUI. Which is IMHO the good option,
since you are doing something that normally will break stuff. Using the
commandline we can skip this overlap check with the `--skip-overlap-check` flag:
ipa dnsforwardzone-add --skip-overlap-check example.org --forwarder=192.0.2.10 --forwarder=198.51.100.10 --forward-policy=only
Server will check DNS forwarder(s).
This may take some time, please wait ...
Zone name: example.org.
Active zone: TRUE
Zone forwarders: 192.0.2.10, 198.51.100.10
Forward policy: only
If you do not want to add a forward zone, you can also use this flag to add a
regular zone:
ipa dnszone-add --skip-overlap-check example.org --forwarder=192.0.2.10 --forwarder=198.51.100.10 --forward-policy=only
[1]: https://www.digitalocean.com/?refcode=7435ae6b8212
---
License:
All the text on this website is free as in freedom unless stated otherwise.
This means you can use it in any way you want, you can copy it, change it
the way you like and republish it, as long as you release the (modified)
content under the same license to give others the same freedoms you've got
and place my name and a link to this site with the article as source.
This site uses Google Analytics for statistics and Google Adwords for
advertisements. You are tracked and Google knows everything about you.
Use an adblocker like ublock-origin if you don't want it.
All the code on this website is licensed under the GNU GPL v3 license
unless already licensed under a license which does not allows this form
of licensing or if another license is stated on that page / in that software:
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see .
Just to be clear, the information on this website is for meant for educational
purposes and you use it at your own risk. I do not take responsibility if you
screw something up. Use common sense, do not 'rm -rf /' as root for example.
If you have any questions then do not hesitate to contact me.
See https://raymii.org/s/static/About.html for details.