Re: [Pdns-users] PDNS-Recursor Not Providing DNS Lookups?

2008-08-30 Thread bert hubert
On Fri, Aug 22, 2008 at 01:43:32PM -0600, Darren Gamble wrote:
 Hi everyone,
 
 Just to throw my two cents in here...
 
  I'm not sure what to do now - it might be good for PowerDNS to set the
 'rd'
  bit in forwarded queries.
 
 We've been meaning to open up a trac ticket for this.  Our organization
 actually has situations where we'd like powerdns to use the rd bit, and
 also situations where we don't.

Please open up such a ticket, and it will happen.

 I think the best way to handle this would be two different configuration
 directives to handle the two different situations.

Most likely, indeed.

Bert

-- 
http://www.PowerDNS.com  Open source, database driven DNS Software 
http://netherlabs.nl  Open and Closed source services
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users


Re: [Pdns-users] PDNS-Recursor Not Providing DNS Lookups?

2008-08-22 Thread Kenneth Marshall
On Fri, Aug 22, 2008 at 07:42:31PM +0200, bert hubert wrote:
 On Fri, Aug 22, 2008 at 12:30:36PM -0400, Steve Chapman wrote:
  I'm working in an environment that uses split DNS (some parentcompany.com
  servers we want resolved from corporate DNS servers, others from Internet
  DNS servers).  I've installed the pdns-recursor RPM (3.1.7-1) on my RHEL 5
  bind DNS server and configured the recursor, all defaults except:
 
 Very good!
 
  If I run an nslookup Server2.parentcompany.com IP of Corporate DNS
  server, I get a valid IP address, and then if I subsequently re-run the
  nslookup against the PDNS Recursor, it provides the answer from then on.
  Why isn't it providing the answer initially?  Any ideas would be helpful.
 
 The reason is that PowerDNS is expecting you to forward queries to an
 authoritative server.
 
 It appears you are forwarding them to a server that is not authoritative for
 Server2.parentcompany.com, but is in itself a caching resolver.
 
 PowerDNS is sending so called 'non-recursion desired' questions to your
 internal nameserver, and this internal server is therefore not recursing for
 your questions.
 
 Once you've triggered the internal server to look the question up, it keeps
 the answer in the cache.
 
 The second time PowerDNS asks, no recursion is needed, since the answer is
 there already.
 
 I'm not sure what to do now - it might be good for PowerDNS to set the 'rd'
 bit in forwarded queries.
 
 Any ideas?
 
I vote for setting the 'rd' bit in the forwarded queries. That certainly
best fits the behavior that I was expecting to see.

Regards,
Ken
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users


Re: [Pdns-users] PDNS-Recursor Not Providing DNS Lookups?

2008-08-22 Thread Leen Besselink
On Fri, Aug 22, 2008 at 01:40:05PM -0500, Kenneth Marshall wrote:
 On Fri, Aug 22, 2008 at 07:42:31PM +0200, bert hubert wrote:
  On Fri, Aug 22, 2008 at 12:30:36PM -0400, Steve Chapman wrote:
   I'm working in an environment that uses split DNS (some parentcompany.com
   servers we want resolved from corporate DNS servers, others from Internet
   DNS servers).  I've installed the pdns-recursor RPM (3.1.7-1) on my RHEL 5
   bind DNS server and configured the recursor, all defaults except:
  
  Very good!
  
   If I run an nslookup Server2.parentcompany.com IP of Corporate DNS
   server, I get a valid IP address, and then if I subsequently re-run the
   nslookup against the PDNS Recursor, it provides the answer from then on.
   Why isn't it providing the answer initially?  Any ideas would be helpful.
  
  The reason is that PowerDNS is expecting you to forward queries to an
  authoritative server.
  
  It appears you are forwarding them to a server that is not authoritative for
  Server2.parentcompany.com, but is in itself a caching resolver.
  
  PowerDNS is sending so called 'non-recursion desired' questions to your
  internal nameserver, and this internal server is therefore not recursing for
  your questions.
  
  Once you've triggered the internal server to look the question up, it keeps
  the answer in the cache.
  
  The second time PowerDNS asks, no recursion is needed, since the answer is
  there already.
  
  I'm not sure what to do now - it might be good for PowerDNS to set the 'rd'
  bit in forwarded queries.
  
  Any ideas?
  
 I vote for setting the 'rd' bit in the forwarded queries. That certainly
 best fits the behavior that I was expecting to see.
 
 
Maybe add a seperate option like this ?:

forward-zones-with-rdbit= ?
recurse-forward-zones= ?

 Regards,
 Ken
 ___
 Pdns-users mailing list
 Pdns-users@mailman.powerdns.com
 http://mailman.powerdns.com/mailman/listinfo/pdns-users
 
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users


RE: [Pdns-users] PDNS-Recursor Not Providing DNS Lookups?

2008-08-22 Thread Darren Gamble
Hi everyone,

Just to throw my two cents in here...

 I'm not sure what to do now - it might be good for PowerDNS to set the
'rd'
 bit in forwarded queries.

We've been meaning to open up a trac ticket for this.  Our organization
actually has situations where we'd like powerdns to use the rd bit, and
also situations where we don't.

I think the best way to handle this would be two different configuration
directives to handle the two different situations.


Darren Gamble
Systems Architect, Regional Services
Shaw Cablesystems GP
630 - 3rd Avenue SW
Calgary, Alberta, Canada
T2P 4L4
(403) 781-4948
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users