Set-PveClusterSdnDns
Update sdn dns object configuration.
API: PUT /cluster/sdn/dns/{dns}, Proxmox VE API viewer
Syntax
Section titled “Syntax”Set-PveClusterSdnDns [-PveTicket <PveTicket>] [-Delete <string>] [-Digest <string>] -Dns <string> [-Fingerprint <string>] [-Key <string>] [-LockToken <string>] [-Reversemaskv6 <int>] [-Ttl <int>] [-Url <string>] [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Delete |
string |
No | A list of settings you want to delete. |
-Digest |
string |
No | Prevent changes if current configuration file has a different digest. This can be used to prevent concurrent modifications. |
-Dns |
string |
Yes | The SDN dns object identifier. |
-Fingerprint |
string |
No | Certificate SHA 256 fingerprint. |
-Key |
string |
No | |
-LockToken |
string |
No | the token for unlocking the global SDN configuration. |
-Reversemaskv6 |
int |
No | |
-Ttl |
int |
No | |
-Url |
string |
No |
Every parameter also binds by property name from the pipeline, so an object with node and vmid properties (the output of Get-PveGuest, for one) fills -Node and -Vmid. Without -PveTicket the cmdlet uses the last connection, see Connection.
Output
Section titled “Output”A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.