19 Jul
2019
19 Jul
'19
1:16 p.m.
I think this is resolved now.
Yes it looks like it is. Can you explain how this affects the
content of the 44.rev zone file and the configuration of a DNS server
that serves that zone?
I now have the 44.in-addr.arpa configured in a local DNS server and
loaded with that zonefile as downloaded from the FTP server.
Rob
19 Jul
19 Jul
1:33 p.m.
New subject: Reverse DNS broken
On Fri, Jul 19, 2019 at 08:16 Rob Janssen <pe1chl(a)amsat.org> wrote:
The 44.in-addr.arpa zone probably should be split into 192 zones for each
/16 in the remaining /10 and /9. The administrators should take a look how
to organise things going forward.
Kind regards,
Job
I think this
is resolved now.
Yes it looks like it is. Can you explain how this affects the
content of the 44.rev zone file and the configuration of a DNS server
that serves that zone?
I now have the 44.in-addr.arpa configured in a local DNS server and
loaded with that zonefile as downloaded from the FTP server.
1965
days inactive
1965
days old
1 comments
2 participants
participants (2)
-
Job Snijders -
Rob Janssen