On Fri, Jan 14, 2022 at 10:45 AM Raphael Mejias Dias <raph...@gmail.com> wrote: > > Basically, I'm wanting to create an internal address like intranet.local, > this way, I can change the internal IP address, without the obligation to > reconfigure the client machines to lookup the new IP, only changing the DNS > lookup table.
I'd avoid using the .local TLD due to RFC 6762. You might also consider whether mDNS is actually the easiest solution to your problem. > I've realized the network PC's did not find the DNS address, only the > localhost can find it, when I force the DNS, the client PC cannot access the > internet anymore. I don't know what you mean by "force the DNS" but in general most OSes will just have a list of DNS servers that they will pick from either in order or randomly, and without regard to what the TLD is. So, you'll probably want to tell them to use your internal DNS server as the only DNS server. This means it needs to be authoritative for your internal domain and resolving for the others. If you used the .local TLD then you might also be running into issues with conflicts with RFC 6762. BIND is capable of doing the job - I have it set up to resolve an internal domain and outside DNS. I have BIND set up to forward first to Google DNS, and then added my zones to it. -- Rich
