Re: [Pdns-users] rec_control dump-cache not dumping to file

[Eric Raymond]

Yep, that was it.  I didn't notice that it was using setuid/setgid with
privatetmp.

Thanks for the help!

On Tue, Apr 24, 2018 at 1:01 PM bert hubert 
wrote:

> On Tue, Apr 24, 2018 at 07:37:11PM +, Eric Raymond wrote:
> > I have found this to be not working in 4.1.X releases, and havent tried
> in
> > any other branch.
> > Perhaps I am misunderstanding the command, but it appears to do nothing
> >
> > # rec_control dump-cache /tmp/cache-dump
> > dumped 1970 records
>
> Thank you for your detailed reporting! You are likely running into a
> systemd
> feature called private tmp. Your dump is somewhere in /var/run, which is
> the
> private tmp directory for the recursor process.
>
> https://www.freedesktop.org/software/systemd/man/systemd.exec.html has
> details.
>
> Good luck!
>
> Bert
>
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

Re: [Pdns-users] rec_control dump-cache not dumping to file

[David]

On 2018-04-24 1:37 PM, Eric Raymond wrote:

Aloha,

I have found this to be not working in 4.1.X releases, and havent tried 
in any other branch.

Perhaps I am misunderstanding the command, but it appears to do nothing

# rec_control dump-cache /tmp/cache-dump
dumped 1970 records

# ls -l /tmp/cache-dump
ls: cannot access /tmp/cache-dump: No such file or directory


Do you have systemd doing private /tmp?



I verified that the file is non-existent before running, and still is 
non-existent after.  Am I missing something?


Even the version flag doesnt seem to work

[eraymond@infdcpdns02:~] $ rec_control ---version
syntax: rec_control [options] command, options as below:
   .. output truncated
   --version
         Show the version of this program

In addition, 'rec_control help' can be used to retrieve a list
of available commands from PowerDNS

I am running from the rpm repo with pdns-recursor-4.1.2-1pdns.el7.x86_64

Any help appreciated

Thanks
Eric


___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users



___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

Re: [Pdns-users] rec_control dump-cache not dumping to file

[bert hubert]

On Tue, Apr 24, 2018 at 07:37:11PM +, Eric Raymond wrote:
> I have found this to be not working in 4.1.X releases, and havent tried in
> any other branch.
> Perhaps I am misunderstanding the command, but it appears to do nothing
> 
> # rec_control dump-cache /tmp/cache-dump
> dumped 1970 records

Thank you for your detailed reporting! You are likely running into a systemd
feature called private tmp. Your dump is somewhere in /var/run, which is the
private tmp directory for the recursor process.

https://www.freedesktop.org/software/systemd/man/systemd.exec.html has
details.

Good luck!

Bert
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

[Pdns-users] rec_control dump-cache not dumping to file

[Eric Raymond]

Aloha,

I have found this to be not working in 4.1.X releases, and havent tried in
any other branch.
Perhaps I am misunderstanding the command, but it appears to do nothing

# rec_control dump-cache /tmp/cache-dump
dumped 1970 records

# ls -l /tmp/cache-dump
ls: cannot access /tmp/cache-dump: No such file or directory

I verified that the file is non-existent before running, and still is
non-existent after.  Am I missing something?

Even the version flag doesnt seem to work

[eraymond@infdcpdns02:~] $ rec_control ---version
syntax: rec_control [options] command, options as below:
  .. output truncated
  --version
Show the version of this program

In addition, 'rec_control help' can be used to retrieve a list
of available commands from PowerDNS

I am running from the rpm repo with pdns-recursor-4.1.2-1pdns.el7.x86_64

Any help appreciated

Thanks
Eric
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

Re: [Pdns-users] Using PowerDNS with Plesk/cPanel (Repost)

[Jackson Yap]

Hi Alejandro,
Yes that is exactly what we want! So ultimately we will have ns1 ns2 ns3 to a 
cluster of pdns dns servers setup, which is fully redundant so if any of ns is 
down, the records from plesk and cpanel can still send to rest of the ns. Is 
this like this at your end?
We also need to automate the clean up from the pdns cluster if the dns is 
removed from Plesk and cpanel servers.
If all is correct, do let us know your fee to implement for us? We already have 
1 pdns authorise+recursor server setup so far.
Warmest Regards,Jackson Yap
 Original message From: Alejandro Flores Lopez 
 Date: 24/4/18  11:08 PM  (GMT+08:00) To: Jackson 
Yap  Cc: pdns-users@mailman.powerdns.com Subject: Re: 
[Pdns-users] Using PowerDNS with Plesk/cPanel (Repost) 
i see. 
I have a setup like that
Our cpanel and plesk servers works as masters dns, sending notifications to a 
PDNS slave dns with the supermaster configuration, and using mysql replication 
to a bunch of more PDNS.
So each time we add a new cpanel or plesk, we modify the configuration in bind, 
setting the notify and allow transfer to the slave.
If this configuration works for you, i can help you.
Regards




Alejandro Flores López
Gerente de Operaciones
Wingu Networks, SA de CV
aflor...@wingunetworks.com


T. +5255 8503  2600 Ex 4311


2018-04-24 0:09 GMT-05:00 Jackson Yap :
Hi Alejandro, Nope, not like this. Customers are not involved. We are trying to 
setup in such a way that, all our cPanel and Plesk servers (when records are 
added or deleted on them), they will be transferred to the PDNS cluster. Our 
PDNS cluster will work as the authoritative in such a way. So cPanel and Plesk 
servers are sort of like "invisible" name servers in operation. As main records 
will all be queried from the PDNS cluster. Warmest Regards,Jackson Yap From: 
Alejandro Flores Lopez  
Sent: Tuesday, 24 April 2018 1:04 PM
To: Jackson Yap 
Cc: pdns-users@mailman.powerdns.com
Subject: Re: [Pdns-users] Using PowerDNS with Plesk/cPanel (Repost) you mean to 
have a cpanel, plesk offering to the final user the chance to modify his domain 
using the embbeded domain control and  bind notifying to pdns, (pdns working as 
authoritative?) so in that way the final user is free to modify and pdns just 
receive the updates? and finally, a script to clean pdns based on the response 
of the master DNS (plesk and cpanel)? Regards
   Alejandro Flores López
Gerente de Operaciones
Wingu Networks, SA de CV
aflor...@wingunetworks.com

T. +5255 8503  2600 Ex 4311 2018-04-23 23:53 GMT-05:00 Jackson Yap 
:Hi! We are still looking for experienced consultant to assist 
us with PowerDNS with Plesk/cPanel using notify or a recommended solution. The 
aim is to create a single PowerDNS cluster for our DNS usage. We have already 
setup PowerDNS/Recursor/Poweradmin, but need assistance to configure and setup 
for our purpose. If you have done this before and able to help, do let us know! 
Warmest Regards,Jackson Yap 
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users  Puede consultar aquí 
la Política de Privacidad“Este mensaje es confidencial.  Si usted no es el 
destinatario de este mensaje, le suplicamos se lo notifique al remitente 
mediante un correo electrónico y que borre el presente mensaje y sus anexos de 
su computadora sin retener una copia de los mismos. No debe copiar este mensaje 
o usarlo para cualquier propósito ni divulgar su contenido. Wingu Networks se 
reserva el derecho de monitorear todas las comunicaciones de correo electrónico 
(relacionadas o no con Wingu Networks) que se transmitan a través de su 
sistema. Muchas gracias.This email is confidential and may also be privileged.  
If you are not the intended recipient please immediately advise the sender by 
reply e-mail and delete this message and its attachments from your computer 
without retaining a copy. You should not copy it or use it for any purpose nor 
disclose its contents to any other person. Wingu Networks reserves the right to 
monitor all email communications (whether related to the business of Wingu 
Networks or not) through its networks. Thank you.”





Puede consultar aquí la Política de Privacidad“Este mensaje es confidencial.  
Si usted no es el destinatario de este mensaje, le suplicamos se lo notifique 
al remitente mediante un correo electrónico y que borre el presente mensaje y 
sus anexos de su computadora sin retener una copia de los mismos. No debe 
copiar este mensaje o usarlo para cualquier propósito ni divulgar su contenido. 
Wingu Networks se reserva el derecho de monitorear todas las comunicaciones de 
correo electrónico (relacionadas o no con Wingu Networks) que se transmitan a 
través de su sistema. Muchas gracias.This email is confidential and may also be 

Re: [Pdns-users] Using PowerDNS with Plesk/cPanel (Repost)

[Alejandro Flores Lopez]

i see.

I have a setup like that

Our cpanel and plesk servers works as masters dns, sending notifications to
a PDNS slave dns with the supermaster configuration, and using mysql
replication to a bunch of more PDNS.

So each time we add a new cpanel or plesk, we modify the configuration in
bind, setting the notify and allow transfer to the slave.

If this configuration works for you, i can help you.

Regards





Alejandro Flores López
Gerente de Operaciones
Wingu Networks, SA de CV
aflor...@wingunetworks.com


T. +5255 8503  2600 Ex 4311



2018-04-24 0:09 GMT-05:00 Jackson Yap :

> Hi Alejandro,
>
>
>
> Nope, not like this. Customers are not involved. We are trying to setup in
> such a way that, all our cPanel and Plesk servers (when records are added
> or deleted on them), they will be transferred to the PDNS cluster. Our PDNS
> cluster will work as the authoritative in such a way. So cPanel and Plesk
> servers are sort of like "invisible" name servers in operation. As main
> records will all be queried from the PDNS cluster.
>
>
>
> Warmest Regards,
>
> Jackson Yap
>
>
>
> *From:* Alejandro Flores Lopez 
> *Sent:* Tuesday, 24 April 2018 1:04 PM
> *To:* Jackson Yap 
> *Cc:* pdns-users@mailman.powerdns.com
> *Subject:* Re: [Pdns-users] Using PowerDNS with Plesk/cPanel (Repost)
>
>
>
> you mean to have a cpanel, plesk offering to the final user the chance to
> modify his domain using the embbeded domain control and  bind notifying to
> pdns, (pdns working as authoritative?)
>
> so in that way the final user is free to modify and pdns just receive the
> updates? and finally, a script to clean pdns based on the response of the
> master DNS (plesk and cpanel)?
>
>
>
> Regards
>
>
>
>
>
>
>
>
> Alejandro Flores López
> Gerente de Operaciones
> Wingu Networks, SA de CV
> aflor...@wingunetworks.com
>
> T. +5255 8503  2600 Ex 4311
>
>
>
> 2018-04-23 23:53 GMT-05:00 Jackson Yap :
>
> Hi!
>
>
>
> We are still looking for experienced consultant to assist us with PowerDNS
> with Plesk/cPanel using notify or a recommended solution. The aim is to
> create a single PowerDNS cluster for our DNS usage.
>
>
>
> We have already setup PowerDNS/Recursor/Poweradmin, but need assistance to
> configure and setup for our purpose. If you have done this before and able
> to help, do let us know!
>
>
>
> Warmest Regards,
>
> Jackson Yap
>
>
>
>
> ___
> Pdns-users mailing list
> Pdns-users@mailman.powerdns.com
> https://mailman.powerdns.com/mailman/listinfo/pdns-users
>
>
>
>
>
> Puede consultar aquí la Política de Privacidad
> 
>
> *“Este mensaje es confidencial.  Si usted no es el destinatario de este
> mensaje, le suplicamos se lo notifique al remitente mediante un correo
> electrónico y que borre el presente mensaje y sus anexos de su computadora
> sin retener una copia de los mismos. No debe copiar este mensaje o usarlo
> para cualquier propósito ni divulgar su contenido. Wingu Networks se
> reserva el derecho de monitorear todas las comunicaciones de correo
> electrónico (relacionadas o no con Wingu Networks) que se transmitan a
> través de su sistema. **Muchas gracias.*
>
> *This email is confidential and may also be privileged.  If you are not
> the intended recipient please immediately advise the sender by reply e-mail
> and delete this message and its attachments from your computer without
> retaining a copy. You should not copy it or use it for any purpose nor
> disclose its contents to any other person. Wingu Networks reserves the
> right to monitor all email communications (whether related to the business
> of Wingu Networks or not) through its networks. Thank you.”*
>

-- 


Puede consultar aquí la Política de Privacidad 


*“Este mensaje es 
confidencial.  Si usted no es el destinatario de este mensaje, le 
suplicamos se lo notifique al remitente mediante un correo electrónico y 
que borre el presente mensaje y sus anexos de su computadora sin retener 
una copia de los mismos. No debe copiar este mensaje o usarlo para 
cualquier propósito ni divulgar su contenido. Wingu Networks se reserva el 
derecho de monitorear todas las comunicaciones de correo electrónico 
(relacionadas o no con Wingu Networks) que se transmitan a través de su 
sistema. **Muchas gracias.*



*This email is confidential and may also be 
privileged.  If you are not the intended recipient please immediately 
advise the sender by reply e-mail and delete this message and its 
attachments from your computer without retaining a copy. You should not 
copy it or use it for any purpose nor disclose its contents to any other 
person. Wingu Networks reserves the right to monitor all email 
communications (whether related to the business of Wingu Networks or not) 
through its networks. Thank you.”*

[Pdns-users] Announcing: Lua records, GSLB

[bert hubert]

Hi everyone,

Yesterday we merged the new "LUA Records", and they have now appeared in the
master builds you can apt-get or yum from https://repo.powerdns.com (or find
the tarballs, https://builder.powerdns.com )

Here is the first part of the blogpost:

"While PowerDNS ships with a powerful geographical backend (geoip), there
 was a demand for more broader solutions that include uptime monitoring,
 which in addition could run from existing zones.

 After several trials, we have settled on “LUA” resource records, which look 
like this:

 @   IN   LUA   A   "ifportup(443, {'52.48.64.3', '45.55.10.200'})"

 When inserted in a zone with LUA records enabled, any lookups for your
 domain name will now return one of the listed IP addresses that listens on
 port 443.  If one is down, only the other gets returned.  If both are down,
 both get returned.

 But if both are up, wouldn’t it be great if we could return the ‘best’ IP 
address for that client? Say no more:

 @IN   LUA A ( "ifportup(443, {'52.48.64.3', '45.55.10.200'}, "
  "{selector='closest'})  ")"


https://blog.powerdns.com/2017/12/15/powerdns-authoritative-lua-records/ has
this and more details.  Documentation is on
https://doc.powerdns.com/authoritative/lua-records.html

This feature is already in production in some big places, so the API is
stable. However, if you find things you need that are missing, or have
problems, now is the time to let us know!

Bert
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

Re: [Pdns-users] GLSB with Health Check Mechanism

[bert hubert]

On Tue, Apr 24, 2018 at 02:22:04PM +0430, Hamed Haghshenas wrote:
> Hello Dears,

Hi! 

> Now I want add health check, for Example, before redirect 185.131.128.0/18
> requests to I.J.K.L check the health of I.J.K.L
> 
> With ping, http or . and if is OK redirect to I.J.K.L else redirect to
> default A.B.C.D .


If you want to do that, I recommend that you take a look at 
https://blog.powerdns.com/2017/12/15/powerdns-authoritative-lua-records/

We merged this into PowerDNS yesterday and it does exactly what you want.

Good luck!

Bert
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

[Pdns-users] GLSB with Health Check Mechanism

[Hamed Haghshenas]

Hello Dears,

 

I run PDNS as traffic management for my servers, I install powerdns
Authoritative with EDNS Support and GeoIP Backend .

 

Then I create a yaml configuration file to manage my traffic based on client
subnets like bellow :

 

##

domains:

- domain: geo.web45.ir

  ttl: 30

  records:

geo.web45.ir:

unknown.geo.web45.ir:

  - a: A.B.C.D

tcea.geo.web45.ir:

  - a: W.X.Y.Z

tcwa.geo.web45.ir:

  - a: I.J.K.L

 

  services:

geo.web45.ir:

  default: [ 'unknown.geo.web45.ir' ]

# TCEA NETWORK #

  176.223.80.0/21: 'tcea.geo.web45.ir'

  176.65.160.0/19: 'tcea.geo.web45.ir'

# TCWA NETWORK #

  178.216.252.0/22: 'tcea.geo.web45.ir'

  185.131.128.0/18: 'tcea.geo.web45.ir'



 

Now I want add health check, for Example, before redirect 185.131.128.0/18
requests to I.J.K.L check the health of I.J.K.L

With ping, http or . and if is OK redirect to I.J.K.L else redirect to
default A.B.C.D .

 

Best Regards,

Hamed Haghshenas

 

___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

Re: [Pdns-users] define several IP Subnet for one service in GeoIP backend

[Hamed Haghshenas]

Thanks dears,

 

From: Brian Candler [mailto:b.cand...@pobox.com] 
Sent: Monday, April 23, 2018 6:43 PM
To: Hamed Haghshenas ;
pdns-users@mailman.powerdns.com
Subject: Re: [Pdns-users] define several IP Subnet for one service in GeoIP
backend

 

On 23/04/2018 10:36, Hamed Haghshenas wrote:

I know, it's work with your example but I have many client subnet in my
network about 150 subnets .

 

So a little hard to write every subnet in separated line,I want to find a
way to combine these in one line for every service .

The configuration is YAML, so it's very easy to write a script to convert
from some local representation (in whatever format is convenient for you to
maintain) to the format that PDNS requires.

 

#!/usr/bin/python
import yaml

s1 = yaml.load("""
193.178.201.0/24,188.158.188.0/24: tcar.geo.gadgetworld.ir
""")
s2 = {}

for k, v in s1.items():
for i in k.split(","):
s2[i] = v

print(yaml.dump(s2, default_flow_style=False))

___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users