Request Redirect

[Kevin Darcy]

Since "views" require parallel maintenance of zone data, they are 
somewhat of a heavyweight/sledgehammer approach to the problem.

Subject to certain caveats, the "sortlist" feature may be a better fit 
for this requirement, i.e. define the name with *both* IP addresses, and 
then sort the answers depending on the source address range of the 
querying client.

Caveats:
1) All caching resolvers need to have the same sortlist capability and 
synchronized definitions -or- they must at all times exactly preserve 
the order of the responses they received from upstream, even when 
answering from their own cache
2) If #1 cannot be met, then the client must be able to tolerate an 
occasional "wrong" answer, resulting, typically, in a connection attempt 
to the "wrong" resource, and potentially a timeout/failover to the other 
address. The extent of the "wrongness" can be mitigated by lowering the 
TTL values on the RRset, but then this increases query traffic, so it's 
a tradeoff.

                                                                         
                                     - Kevin

On 6/15/2010 7:58 AM, Jorge Fábregas wrote:
> On Tuesday 15 June 2010 07:52:34 sasa sasa wrote:
>    
>> we have 2 network, when network 1 request www.example.com i want to reply
>> with x.x.x.x A record, and when network 2 request www.example.com i want
>> to reply with y.y.y.y A record. is that possible in Bind configuration?
>>      
> Hi,
>
> Sure. Check out Bind Views:
>
> http://www.zytrax.com/books/dns/ch7/view.html
>
> HTH,
> Jorge
> _______________________________________________
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
>
>
>