When either type of client (static or DHCP client) initiates an A record update with its authoritative DNS server, it will first start by performing an SOA query for the FQDN of the client in question: The client then receives a response from the authoritative DNS server containing information about the server that is to process the dynamic update.From there, the client continues communicating with the primary DNS server that accepted the A record update.
Clients with dynamically-set network connections (DHCP clients) will communicate with both the authoritative DNS server and the DHCP server for updating A and PTR records.
What we outline in this post is how you can create and update PTR records for yourself, without having to revert to us.
So let’s see how can you update the PTR records of an IP address you’re using within Cloud Sigma’s clouds.
This has worked in past versions of webmin, pre-1.780. add record: www1; 10.2.3.1; update reverse = Yes 3.
add record: www2; 10.2.3.1; update reverse = Yes 4.