consolidating in-addr.arpa data

G.W. Haywood bind at jubileegroup.co.uk
Sat Sep 16 08:20:17 UTC 2023


Hi there,

On Sat, 16 Sep 2023, John Thurston wrote:

> A host which auto-registers in MS DNS, creates an A in foo.alaska.gov 
> and PTR in whatever.10.in-addr.arpa. MS DNS is happy to publish those.
> 
> But the DNS system running on BIND also has a whatever.10.in-addr.arpa 
> zone.
> 
> So if I want to find the PTR for 13.12.11.10.in-addr.arpa, I must query 
> both DNS systems in turn. If I get NXDOMAIN from both, then I can say 
> the PTR doesn't exist.
> 
> On each system, I'd like to be able to take the 10.in-addr.arpa data 
> from the other, compute the differences, and incorporate them locally. 
> Then I'll be able to query either system, and accept an NXDOMAIN with 
> confidence.

Is there a reason not to split the /8 into two /9s or something like that?
Then you'd have no fragmentation (at least not for this reason) and you'd
always know who to ask.

> And since writing my earlier note, I have re-located the code I think I 
> stumbled across earlier
> 
> Tony Finch's "nsdiff"

Does that mean problem replaced, if not solved?

-- 

73,
Ged.


More information about the bind-users mailing list