REST API: PTR record does not align with REST API state for deleted rdns (or even SCP)

leee

Code

$ dig @root-dns.netcup.net +short -x 198.51.100.100
v22025example.nicesrv.de.
$ go run cmd/netcup/main.go rdns get 198.51.100.100
v22025example.nicesrv.de
$ go run cmd/netcup/main.go rdns delete 198.51.100.100
$ curl -s -H "Accept: application/hal+json" \
  -H "Authorization: Bearer $(go run cmd/netcup/main.go auth print-access-token)" \
  -X GET \
  'https://servercontrolpanel.de/scp-core/api/v1/rdns/ipv4/198.51.100.100' | jq
{
  "rdns": null
}

Alles anzeigen

After using `DELETE /api/v1/rdns/ipv4/{ip}` on a vServer IP with the REST API, I would expect for there to be no PTR record. However:

Code

$ # wait 10 minutes for netcup infrastructure to deploy changed records
$ dig @root-dns.netcup.net +short -x 198.51.100.100
nobody.yourvserver.net.

If netcup would like `nobody.yourvserver.net` to be a default PTR record for servers that have no explicitly defined hostname, the REST API should also report this on `GET`.

It is also especially weird that SCP does not have the updated hostname either. Is that also on a batched job like the every 10 minute DNS server updates but at a less frequent interval?

**[netcup] Sarah G.**

Hello leee

For a better overview, we will now respond briefly to each thread here—even though most of the responses will be similar, we want to keep a better overview of your input.

We have forwarded the issue described to the relevant department, which is currently reviewing it. Unfortunately, we cannot provide you with more detailed info at this point in time.

Thank you very much once again!

Kind regards
Sarah & the netcup team