Re: forwarding query-source (was Re: name caching and forwarding)

2013-03-05 Thread Matus UHLAR - fantomas
On 04.03.13 17:35, Shawn Bakhtiar wrote: A better solution may be (if feasible) to register and get an internet AS number and enable BGP on both links. If one fails the upstream routers (even if from desperate providers) will detect a fail and re-rout via the active link. you don't need AS

RE: forwarding query-source (was Re: name caching and forwarding)

2013-03-04 Thread Shawn Bakhtiar
, but that's very hackish. Date: Sat, 2 Mar 2013 16:16:28 +0100 From: uh...@fantomas.sk To: bind-users@lists.isc.org Subject: Re: forwarding query-source (was Re: name caching and forwarding) On 01.03.13 17:23, Lawrence K. Chen, P.Eng. wrote: I thought I had read somewhere the query-source

Re: forwarding query-source (was Re: name caching and forwarding)

2013-03-02 Thread Matus UHLAR - fantomas
On 01.03.13 17:23, Lawrence K. Chen, P.Eng. wrote: I thought I had read somewhere the query-source default is to try making queries from all the IPs on my system. No, the default is to use special IP 0.0.0.0 that causes the system (not the BIND) to select source IP address. And, my DNS

forwarding query-source (was Re: name caching and forwarding)

2013-03-01 Thread Lawrence K. Chen, P.Eng.
This reminds me of a problem that I've been having, that came up again recently. I thought I had read somewhere the query-source default is to try making queries from all the IPs on my system. And, my DNS servers have two IPs on themusing policy based routing, the first IP routes out on my

name caching and forwarding

2013-02-26 Thread Robert Moskowitz
So now I am working on adding a name caching service to my mailserver. And I am reading up on namecaching. For RHEL/Centos, there is not much to doing this as the default install of bind SEEMS to be a name caching server. But I want it to NOT go out on the net for queries, but to direct all

Re: name caching and forwarding

2013-02-26 Thread Phil Mayers
On 26/02/13 16:07, Robert Moskowitz wrote: And I am having challenges with the forward option. It reads that 'forward only' will always ask the forwarder about the query and seems to defeat caching? And 'forward first' only looks in cache after a forward fails? This does not sound right and

Re: name caching and forwarding

2013-02-26 Thread Robert Moskowitz
On 02/26/2013 11:14 AM, Phil Mayers wrote: On 26/02/13 16:07, Robert Moskowitz wrote: And I am having challenges with the forward option. It reads that 'forward only' will always ask the forwarder about the query and seems to defeat caching? And 'forward first' only looks in cache after a

Re: name caching and forwarding

2013-02-26 Thread Kevin Darcy
On 2/26/2013 11:39 AM, Robert Moskowitz wrote: On 02/26/2013 11:14 AM, Phil Mayers wrote: On 26/02/13 16:07, Robert Moskowitz wrote: And I am having challenges with the forward option. It reads that 'forward only' will always ask the forwarder about the query and seems to defeat caching?

Re: name caching and forwarding

2013-02-26 Thread Robert Moskowitz
hey, Kevin, hope you are hanging well back at the old stomping ground! On 02/26/2013 01:42 PM, Kevin Darcy wrote: On 2/26/2013 11:39 AM, Robert Moskowitz wrote: On 02/26/2013 11:14 AM, Phil Mayers wrote: On 26/02/13 16:07, Robert Moskowitz wrote: And I am having challenges with the forward

Re: name caching and forwarding

2013-02-26 Thread Mark Andrews
In message 512d0222.5020...@chrysler.com, Kevin Darcy writes: If all you want to do is run a private namespace, I wouldn't be fiddling around with forwarding at all. Set up your own root zone, propagate a private set of hints data, and be happy. I know that you once thrived in such a DNS