Re: [Pdns-users] Domain serial with Postgres backend
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mitchell Smith wrote: I added changed_date as a 7th field, hoping that it was an optional argument; however the serial for my zones is still stuck on 0. Did you make a change resulting in a modified changed-date after you changed the query to include the field? Without such change there is little reason to change the serial. Hugo. - -- [EMAIL PROTECTED] http://hugo.vanderkooij.org/ PGP/GPG? Use: http://hugo.vanderkooij.org/0x58F19981.asc A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting frowned upon? Bored? Click on http://spamornot.org/ and rate those images. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFIrlefBvzDRVjxmYERAmCeAJ0ROp8glq2gcqI00+F25UgZy9rGZwCaApOT AWtEubu1t5E721pXGkKLIAo= =q1J9 -END PGP SIGNATURE- ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] DNAME record support?
Hello, according to the latest PowerDNS documentation, there is no support for the DNAME record. Are there any intentions to implement them? Or any reasons not to implement them? http://www.rfc-editor.org/rfc/rfc2672.txt Kind regards Marten ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] PDNS-Recursor Not Providing DNS Lookups?
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: allow-from=127.0.0.1 (users query the bind server, bind queries pdns on port 5301, so only bind should be accessing pdns) forward-zones-file=/etc/powerdns/zonesfile ignore-rd-bit=on local-address=127.0.0.1 local-port=5301 The zonesfile then contains things like: Server1.parentcompany.com=IP of Internet DNS server Server2.parentcompany.com=IP of Corporate DNS server When I start the pdns-recursor and point bind to it, my nslookups fail: [EMAIL PROTECTED] powerdns]# nslookup server localhost Default server: localhost Address: 127.0.0.1#53 set port=5301 Server2.parentcompany.com Server: localhost Address:127.0.0.1#5301 ** server can't find Server2.parentcompany.com: SERVFAIL Using a tcpdump, I did see a dns request go to the correct DNS server, but no response was provided. 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. Thank you, Steve Chapman ___ 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?
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?
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?
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
