You can't resolve differences in both directions automatically without
inevitable conflicts, similar to merging code changes. That said, RPZ for
fun and profit...
On Fri, 15 Sep 2023, John Thurston wrote:
A host which auto-registers in MS DNS, creates an A in foo.alaska.gov and PTR
in
Create a 10.in-addr.arpa zone with appropriate delegations and have all servers
serve it. That way they can all find te sub zones.
--
Mark Andrews
> On 16 Sep 2023, at 10:16, John Thurston wrote:
>
>
> A host which auto-registers in MS DNS, creates an A in foo.alaska.gov and PTR
> in
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
Hi John.
Can you tell me a bit more please?
- What zones exist in both BIND and MS DNS for something.10.in-addr.arpa?
- Where are hosts auto registering to? I'd guess MS, but it would be good
to confirm.
- What does fragmentation look like? A few real examples would be useful.
I'm trying to
This question involves making our BIND system work with Microsoft's DNS
software. If this makes it off-topic, let me know and I'll be quiet
about it.
We use ISC BIND to hold and host most of our zone data. Internally, we
have delegated some zones, and they are held in Microsoft DNS. These
5 matches
Mail list logo
