Resolved Bug: Plesk NAT - IP Reset via command line does not work because plesk things the ip does not exist.

[Talistech]

Server operating system version

Ubuntu 22.04.4 LTS

Plesk version and microupdate number

Plesk Obsidian 18.0.62 Update #2

Hi there,

I have found a bug while updating DNS records via the CLI.
You are able to update the dns records to the "internal" ip address while using NAT. But you cannot use the external/public address because Plesk thinks that that address does not exist.

root@server:~# plesk bin subscription --update example.com -ip 99.99.99.99 # Example with public address
An error occurred during domain update: An error occurred during changing of hosting settings: Unable to set IP address for hosting: IP address '99.99.99.99' does not exist

exit status 1


root@server:~# plesk bin subscription --update example.com -ip 10.26.2.102 # Example with local address
SUCCESS: Update of domain 'example.com' completed.

Thanks,

Kind regards,
Talistech

cc: @Kaspar@Plesk

 

[Talistech]

Also posted in Reports because I truly believe this is a bug.

 

[scsa20]

From the command you're trying to do you're trying to change the IP address of the subscription, not the DNS, which you do want to use the local IP address for, it'll automatically update to reflect the public IP address instead. If you want to modify the DNS only, you'll want to look at https://support.plesk.com/hc/en-us/...-specific-domain-using-CLI-in-Plesk-for-Linux so from the looks of it, this is not a bug but is done by design since the public IP is just map to the internal IP to begin with for the configuration files knows to use it instead of the private.

 

[Talistech]

From the command you're trying to do you're trying to change the IP address of the subscription, not the DNS, which you do want to use the local IP address for, it'll automatically update to reflect the public IP address instead. If you want to modify the DNS only, you'll want to look at https://support.plesk.com/hc/en-us/...-specific-domain-using-CLI-in-Plesk-for-Linux so from the looks of it, this is not a bug but is done by design since the public IP is just map to the internal IP to begin with for the configuration files knows to use it instead of the private.

You're totally right. I was a little too fast with creating this ticket. Thanks for the help!