On Nov 30 13:30:38 2023 bd730c5053df9efb via samba <samba at
lists.samba.org> wrote:>
> It is correct as is. PTR records point to IP addresses and reverse zones
get that in-addr.arpa naming.
>
> Best regards,
> Dave.
OK, but normally the rDNS PTR is the reverse of the regular IP. In the example,
the IP 10.99.0.1, but the wiki example PTR has only 0.99.10 and leaves off the
'1' from the final octet.
For example, my IP is 24.142.169.12. If I look that up I get:
# host 24.142.169.12
12.169.142.24.in-addr.arpa domain name pointer novatec-inc.com
All 4 octets shown. If I just try with the top 3 octets I get:
# host 24.142.169
Host 24.142.169 not found: 3(NXDOMAIN)
Maybe this is something special for the DC, but I've always seen and used
all 4
ipv4 octets in rDNS PTR records.
Just checking ...
> PS: I'm also resending this one
I am getting both your messages. Don't know why your getting some indicator
that
you need to resend.
--Mark
> On Thursday, November 30th, 2023 at 15:05, Mark Foley via samba <samba
at lists.samba.org> wrote:
>
>
> > The wiki
https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller#Create_a_reverse_zone
> > says, "For a DC with the FQDN of dc1.samdom.example.com and the
> > ipaddress of 10.99.0.1, to add a record to the 0.99.10.in-addr.arpa
..."
> >
> > Is this correct or should the rDNS PTR be 1.99.10.in-addr.arpa?
> >
> > I just want to make sure this isn't a typeo.
> >
> > Thanks --Mark
> >
> > --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba
>