Hi,
I may well be missing something obvious, or quite possibly I am wrongly
thinking that things should work in a certain way - so I thought I would
ask here first :)
I am running a Samba 4.7.7 AD domain consisting of 4 DCs using Samba's
internal DNS, and I am using Windows' 'DNS Manager' MMC tool as
admin.
Under "Forward Lookup Zones" I have "mydomain.org", and
under "Reverse
Lookup Zones" I have a number of entries of the form
"1.168.192.in-addr.arpa", "1.1.10.in-addr.arpa", etc.
I add a new host to the forward lookup zone as follows:
Name: test1
[ FQDN: test1.mydomain.org. ] - this is auto-populated and greyed out
IP address: 192.168.1.123
[X] Create associated pointer (PTR) record
[ ] Allow any authenticated user to update DNS records with the same owner
name
The forward record gets created just fine, as expected - but I would have
thought that a PTR record should also be created under
1.168.192.in-addr.arpa - this doesn't happen.
Should this work?
Jonathan
--
"If we knew what it was we were doing, it would not be called research,
would it?"
- Albert Einstein
On Fri, 11 May 2018, Jonathan Hunter via samba wrote:> Hi, > > I may well be missing something obvious, or quite possibly I am wrongly > thinking that things should work in a certain way - so I thought I would > ask here first :) > > I am running a Samba 4.7.7 AD domain consisting of 4 DCs using Samba's > internal DNS, and I am using Windows' 'DNS Manager' MMC tool as admin. > > Under "Forward Lookup Zones" I have "mydomain.org", and under "Reverse > Lookup Zones" I have a number of entries of the form > "1.168.192.in-addr.arpa", "1.1.10.in-addr.arpa", etc. > > I add a new host to the forward lookup zone as follows: > Name: test1 > [ FQDN: test1.mydomain.org. ] - this is auto-populated and greyed out > IP address: 192.168.1.123 > [X] Create associated pointer (PTR) record > [ ] Allow any authenticated user to update DNS records with the same owner > name > > The forward record gets created just fine, as expected - but I would have > thought that a PTR record should also be created under > 1.168.192.in-addr.arpa - this doesn't happen. > > Should this work?Known issue. See https://bugzilla.samba.org/show_bug.cgi?id=12186 Regards, -- Tom me at tdiehl.org
On 11 May 2018 at 21:24, <me at tdiehl.org> wrote:> On Fri, 11 May 2018, Jonathan Hunter via samba wrote: > > I may well be missing something obvious, or quite possibly I am wrongly >> thinking that things should work in a certain way - so I thought I would >> ask here first :) >> [...] > > The forward record gets created just fine, as expected - but I would have >> thought that a PTR record should also be created under >> 1.168.192.in-addr.arpa - this doesn't happen. > > > > Known issue. See https://bugzilla.samba.org/show_bug.cgi?id=12186 >Thank you. At least I know it isn't me missing something obvious :) Sadly I don't have Samba coding experience, otherwise I'd put this on my list to look at. Cheers, Jonathan -- "If we knew what it was we were doing, it would not be called research, would it?" - Albert Einstein