Skip to main content

Posts

Automating Ethereum node management tasks using Ansible

SlingNode has released a new Ansible role. The role is designed to automate Ethereum node management tasks. The first release of the role supports the following tasks: Validator keystore import using command line  Validator keystore import using the standard Ethereum key manager API Slashing protection DB import and export The following Validator clients are supported: Lighthouse Prysm Teku Nimbus slingnode.ethereum_node_mgmt Ansible role seamlessly works with slingnode.ethereum role enabling full node deployment in a single playbook! The best place to start is by reading the comprehensive documentation: https://docs.slingnode.com/slingnode.ethereum_node_mgmt/ View the role on Ansible-Galaxy: https://galaxy.ansible.com/slingnode/ethereum_node_mgmt Review the source code and contribute on GitHub: https://github.com/SlingNode/slingnode-ansible-ethereum-node-mgmt Check out examples: https://github.com/SlingNode/slingnode-ethereum-examples
Post a Comment
Read more
Recent posts

Managing Ethereum nodes using Ansible

Our friends as SlingNode have just released their first Open Source project. We know how much work goes into projects like this and wanted to share this on our blog. The slingnode.ethereum Ansible role, can be used to deploy and configure Ethereum nodes. The role utilizes Docker Compose to deploy the Ethereum Clients.  The first release supports the following clients: Execution clients: Geth Nethermind Besu Erigon Consensus clients: Lighthouse Prysm Teku Nimbus  Validator clients: Lighthouse Prysm Teku Nimbus From what we can tell this is the first and only Open Source project that allows for deploying Ethereum servers using Ansible with a focus towards DevOps Teams managing hundreds of servers.  Check out the documentation: https://docs.slingnode.com/slingnode.ethereum/ View the role on Ansible-Galaxy: https://galaxy.ansible.com/slingnode/ethereum Contribute on GitHub: https://github.com/SlingNode/slingnode-ansible-ethereum They have a comprehens
Post a Comment
Read more

DNS response and error types

In this post we explore common DNS response codes. We will cover the following responses: NOERROR SERVFAIL NXDOMAIN NODATA REFUSED Throughout article we’ll refer to the following RFCs: RFC 1034 - DOMAIN NAMES - CONCEPTS AND FACILITIES RFC 2308 - Negative Caching of DNS Queries (DNS NCACHE) RFC 2136 - Dynamic Updates in the Domain Name System (DNS UPDATE) RFC 8914 - Extended DNS Errors Response Codes - RCODEs The DNS RCODES are best defined in RFC2316 .  They signify what type of response was sent by the server. “RCODE   Response code - this four bit field is undefined in requests and set in responses.”   The table below shows the summary of the currently defined RCODEs. Mnemonic Val Description NOERROR 0 No error condition.
Post a Comment
Read more

DNS poisoning in Indonesia - deep dive

DNS blocking in Indonesia article was an introduction to DNS based censorship in Indonesia. This article will be a deep dive into the DNS censorship landscape in Indonesia based on a defined research methodology. This post covers: Overview of our large scale DNS research methodology Statistics on Indonesian DNS servers List of blocking IP addresses used by various ISPs in Indonesia Large scale DNS research methodology DNS servers To facilitate the research we have scanned the Indonesian IP space and collected the list of IP addresses responding to recursive DNS queries on port 53 UDP. We have collected over 10000 IP addresses. 6935 of them have been consistently responding to our queries. 474 of those have been classified as located outside of Indonesia based on geoip lookup during data post processing. In the end we have tested 6461 DNS servers. Test domains In the course of our research we have tested 9 public domain second level domains (SLDs). In addition we pre-fixed each domain
Post a Comment
Read more