28 Jun
2024
28 Jun
'24
5:55 p.m.
Hi,
On Fri, Jun 28, 2024 at 06:08:14PM +0100, iain via BitFolk Users wrote:
I am confused by the whole thing. How does woever is
querying the rDNS know to ask your server?
There is a delegation at BitFolk's servers that lists the
nameservers provided by Richard at https://panel.bitfolk.com/dns/
All the IPs I have (which I'm astonished to
discover add up to
nine different ones) have their rDNS set by the ISP for the
connection or by the company I lease the server from. It is in
their IP address block, not mine, so putting an entry on my dns
server won't help.
For a single IPv4 it is one entry in BitFolk's reverse zone file so
it's easier to do it there. When you put the data for that in at
https://panel.bitfolk.com/dns/ that is basically what it does.
For an IPv6 /64 there can be many entries, in theory up to 2⁶⁴ - 1.
Reverse DNS zones are designed to be delegated on nibble boundaries, so we
delegate the reverse DNS for the entire /64 to customer's own choice
of servers.
The issue here is Richard's need to (work out how to) serve the zone
7.3.0.f.1.f.1.0.8.a.b.0.1.0.0.2.ip6.arpa from somewhere. Just doing
that would not do anything unless BitFolk delegates to it, but that
part is working okay.
By default BitFolk answers reverse IPv6 queries for customer space
on its own servers in a deterministic fashion. This is the "auto"
method. See:
https://tools.bitfolk.com/wiki/IPv6#Reverse_DNS
for more info.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting