diff --git a/CHANGELOG.md b/CHANGELOG.md
index d55b4c9..91d3c99 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -18,6 +18,7 @@ Released closed milestones can be found on [GitHub](https://github.com/Icinga/ic
 ### Breaking changes
 
 * The `-AcceptConnections` argument for the install wizard had the opposite effect in the previous versions. Please review your configuration on a test setup before proceeding with a mass-rollout to ensure the Agent behaves as expected
+* The wizard now ships with a new argument `-ConvertEndpointIPConfig` which will convert hostnames or FQDN entries for connection information to IP addresses. If you are having a CLI string available and neither want to be asked this question or change current behaviour, set the argument to 0: `-ConvertEndpointIPConfig 0`
 
 ### Enhancements
 
diff --git a/doc/30-upgrading-framework.md b/doc/30-upgrading-framework.md
index e162a6a..9afda81 100644
--- a/doc/30-upgrading-framework.md
+++ b/doc/30-upgrading-framework.md
@@ -8,6 +8,8 @@ Specific version upgrades are described below. Please note that version updates
 
 ### Behavior changes
 
+#### Changes on -AcceptConnections
+
 The behaviour on how the `-AcceptConnections` argument of the setup wizard is working has been fixed. Prior to version v1.1.0 the opposite effect took place.
 
 Previous behaviour:
@@ -18,3 +20,9 @@ New behavior:
 
 Setting `-AcceptConnections 1` will only configure the Agent to wait for parent node(s) and open the Windows firewall for incoming traffic.
 Using `-AcceptConnections 0` is now working properly by letting the Agent establish the connection to the parent node(s)
+
+#### New wizard argument -ConvertEndpointIPConfig
+
+With v1.1.0 a new argument is added to the wizard which will prompt a question if hostnames or FQDN for connection data from the Agent to the parent node(s) shall be converted to IP addresses. If you are unsure of the result, you can manually add `-ConvertEndpointIPConfig 0` to your finished configuration string or scripts or answer the question with `no` to keep the current behavour.
+
+By using `-ConvertEndpointIPConfig 1` or answering the wizard question with `yes`, all endpoint configuration data for your parent node(s) are resolved from hostname/FQDN to IP Addresses if possible