On Friday, December 27, 2019 10:01:31 AM PST Reindl Harald wrote: > Am 27.12.19 um 18:58 schrieb Matus UHLAR - fantomas: > >>>> The only thing that I saw was a slip in that there is something > >>>> outside the local DNS server that needs to be configured for reverse > >>>> DNS. > >> > >> Am 27.12.19 um 18:48 schrieb Matus UHLAR - fantomas: > >>> I think that it should be either change local DNS or call ISP to > >>> change it, > >>> not both at once. Having both usually creates/hides different kinds of > >>> problems > > > > On 27.12.19 18:50, Reindl Harald wrote: > >> says who? > > > > common sense I'd say... > > > >> in our /24 range 1-99 are public servers, the rest is internal > >> infrastructure and workstations and there is no point to have that > >> mapping public > > > > Either you have DNS records or you have not. If you have them, either you > > manage them, or you fetch part of it from customer > > have you ever heard about internal and external views?
I think there is a couple of things going on here. 1: is the IP space delegated or not? if it is, then there needs to be a local reverse zone. 2: if the ISP is involved then maybe they own the IP space and its not really delegated. or maybe its shared space don't know. 3: using views are great for splitting IP or fwd zones between internal hosts and ext hosts. but you still need to own the zones. i would say have a conversation with the ISP about the reverse zone, and ask specifically how its setup and why. and if you own the IP space or not and what the delegation is like. -N6Ghost _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
