Bug 10876 - PTR ressource records for Host A rr's are not created in the existing reverse zone
Summary: PTR ressource records for Host A rr's are not created in the existing reverse...
Status: ASSIGNED
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: DNS server (internal) (show other bugs)
Version: 4.13.3
Hardware: x64 Linux
: P5 enhancement (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
: 10807 12258 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-10-13 13:33 UTC by Mirco
Modified: 2020-12-21 12:58 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mirco 2014-10-13 13:33:22 UTC
Using "Version 4.1.12-SerNet-Debian-9.wheezy" and internal DNS there are no associated PTR records created on the reverse zone, when adding a new "host A" ressource record in the default forwarding zone. It makes no difference if the host A rr is added by using "samba-tool dns ..." or Microsoft DNS tool (from RSAT suite). First, I created the reverse zone through Microsoft DNS tool according samba's official DNS/HowTo:

https://wiki.samba.org/index.php/DNS_Administration#Creating_a_new_zone

but I also tried again by removing the reverse zone, restarting samba4 server, and recreating the reverse zone with "samba-tool dns ..." command and afterwards restarting samba4 server again. Unfortunately without success, it didn't help either.

On Google I found some users reporting the same or similar issues, see:

http://forums.debian.net/viewtopic.php?f=10&t=113802
https://lists.samba.org/archive/samba/2014-March/179456.html

seems this issue is RPC/DNSserver related...
Comment 1 Mirco 2014-10-13 13:43:33 UTC
(In reply to d3lphi from comment #0)

I want to add following information. In Microsoft DNS tool I enter my forwarding zone ad.mycompany.com, add a new "Host A" record and enter "testentry" with IP 172.19.100.123 as ressource record. I tick the check box "Create associated pointer (PTR) record" and then on [OK]. I get no error message, everything ok until here. But the associated record is not created on my reverse zone 100.19.172.in-addr.arpa.
Comment 2 Amitay Isaacs 2014-10-14 01:44:08 UTC
This requires implementation of adding reverse record when DNS_RPC_FLAG_RECORD_CREATE_PTR flag is specified.
Comment 3 Björn Jacke 2020-12-21 11:38:27 UTC
*** Bug 12258 has been marked as a duplicate of this bug. ***
Comment 4 Björn Jacke 2020-12-21 12:58:41 UTC
*** Bug 10807 has been marked as a duplicate of this bug. ***