[dnsdist] send command from command line

Remi Gacogne remi.gacogne+dnsdist at powerdns.com
Thu Mar 17 09:22:37 UTC 2016


On 03/17/2016 10:09 AM, Alejandro Adroher Mellado wrote:
> Also if I'm executing the command on the server I need so set that
> key? I thought that the use of setKey and makeKey was not really
> important if I had no plan to set secured communication with dnsdist.
> Maybe I'm wrong.

No, you are right, if the console is only accessible from the local host
(and this host is not shared), you don't need to worry too much about
using a secret key. Of course, you still have to make sure you have the
same configuration on the client and on the server.

> Question: There is possible to access dnsdist from another computer?
> I execute the client connection always from the server computer.

Yes, you can use controlSocket() to bind the console socket to a
remotely accessible address, but please make sure that you have dnsdist
compiled with libsodium support enabled and that you use a secure secret
key before doing that.

> I have just installed libsodium-1.0.8 and restarted dnsdist, but I'm
> still getting the same result.
>> makeKey()
> setKey("plaintext")

Ok, your dnsdist version is compiled without libsodium support, so your
issue is not a key mismatch because console encryption is not supported
at all. Don't you have anything in your logs?


-- 
Remi Gacogne
PowerDNS.COM BV - https://www.powerdns.com/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.powerdns.com/pipermail/dnsdist/attachments/20160317/8c45146d/attachment.sig>


More information about the dnsdist mailing list