Yep.
I understand the IP space can be delegated, and some of it allocated for
use by systems registering in MS DNS. But this isn't going to happen.
There are multiple MS Active Directories, with registered machines
scattered willy-nilly across the 10-dot address-space, sometimes several
competing in the same subnets. The "design and delegate" ship sailed
years ago. I don't have a prayer of correctly fixing the underlying problem.
After thinking harder, I don't even need correct records in all of the
publishers of the various 10.in-addr.arpa zones. My goal now is simpler.
Get the PTR-records from the zones handled by ISC BIND into (and out of)
one particular MS DNS system. I don't need to get the PTRs registered in
MS DNS back into the BIND data.
I think I can get where I need to be by leveraging /nsdiff/
No. We won't be correctly publishing accurate PTRs from all of the
possible DNS services in the environment. But this is achievable, and
will address the problem (of our own making) which is causing pain.
--
Do things because you should, not just because you can.
John Thurston 907-465-8591
john.thurs...@alaska.gov
Department of Administration
State of Alaska
On 9/15/2023 10:55 PM, Greg Choules wrote:
This is because (close your ears MS) it assumes it is the only DNS in
town. Why would there be another one? If there is one client with a
10.x.y.z address then there are potentially several billion more, so
we'll create 10... just to be on the safe side. This makes MS DNS THE
source of truth for all 10, so no-one else can have any of it unless
you start creating delegations.
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
