Yes, you can configure DNAT to use a DDNS hostname instead of a specific public IP address. This will allow you to avoid having to manually update the DNAT configuration if your public IP address changes. To do this, you will need to create a DNS record for your DDNS hostname that points to your public IP address. Once you have done this, you can configure DNAT to use the DDNS hostname as the destination address.

This workaround will allow you to avoid having to manually update the DNAT configuration if your public IP address changes. However, it is important to note that this workaround will only work if your ISP allows you to create static IP aliases.

Yes, you can configure DNAT to use a DDNS hostname instead of a specific public IP address. This will allow you to avoid having to manually update the DNAT configuration if your public IP address changes. To do this, you will need to create a DNS record for your DDNS hostname that points to your public IP address. Once you have done this, you can configure DNAT to use the DDNS hostname as the destination address.

This workaround will allow you to avoid having to manually update the DNAT configuration if your public IP address changes. However, it is important to note that this workaround will only work if your ISP allows you to create static IP aliases.