Re: Possibility of using views to properly return appropriate IP address for hostname based on requestor subnet?

and secondaries. In my > experience, unless there are completely different teams who don't talk much > to each other running separate DNS servers, it is best to keep all your > primary zones in one place (or two for resilience). It makes it easier to > administer and to u

Re: Possibility of using views to properly return appropriate IP address for hostname based on requestor subnet?

main.com" { > # 10.32.1.0/24 > etc... > > zone "net3.domain.com" { > # 10.32.10.0/24 > etc... > > zone "net4.domain.com" { > # 10.32.20.0/24 > etc... > > zone "net5.domain.com" { > # 10.32.30.0/24 > etc... > > zone &q

Re: Possibility of using views to properly return appropriate IP address for hostname based on requestor subnet?

t; for its production side or > system.lab.domain.com" for its lab side. There is no ambiguity about what > address "system" has because each one now has a unique name. > > Note that this requires clients to use FQDNs, which IMHO is a good thing. > I always try to avoid &

Possibility of using views to properly return appropriate IP address for hostname based on requestor subnet?

Hi, I have two domains configured, a production and lab/testing domain [let's say domain.com and lab.domain.com]. I have a few different networks configured [192.168.10.0/24 and 10.32.10.0/24]. I have a system that has two network cards on both the 192.168.10.X network and 10.32.10.X network. I