Reverse lookup ptr records not updating
It's not just for resolving IP addresses into names and vice versa.Clients find their Domain Controller/s and other important AD services by DNS queries, this means that your clients must use your Domain Controller/s as their nameservers.By default, Samba creates the following two forward zones during provisioning/upgrading (of course with your own domain name): The Samba internal DNS is a new implementation.Although BIND is a grown up DNS and long in production on millions of servers, the Samba BIND DLZ module is still new.DNS lookup does the opposite by resolving an IP address to a designated domain name.You should always set the reverse DNS, even if your Linode hosts more than one domain name.If you discover problems or missing features, please open a bug report/feature request at https://bugzilla.samba.org/. If you are using BIND_DLZ as the backend, then your new zone is directly live without restarting Samba or BIND.
Please note that in general, your ISP must setup and maintain these Reverse DNS records (i.e. The internal DNS backend currently needs a restart of Samba to take effect. on adding PTR record in DNS using powershell, PTR record is opposite of A record, PTR record resolves IPAddress to hostname. (Make sure you have added correct subnet reverse lookup zone before adding PTR record).The Reverse Lookup tool will do a reverse IP lookup.If you type in an IP address, we will attempt to locate a dns PTR record for that IP address.