apps
/
hosts-translator
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Translating HOSTS file into other things.
4 Commits 1 Branch 0 Tags 92 KiB
Go 100%
Go to file
Stanislav Nikitin 8869dc8b75
continuous-integration/drone/push Build is failing Details
Add Drone CI configuration. Expect pipeline to fail. 		2022-06-29 00:13:57 +05:00
cmd/hoststranslator Initial commit. 2021-06-06 23:13:55 +05:00
internal Linting. 2021-06-07 12:14:21 +05:00
.drone.yml Add Drone CI configuration. Expect pipeline to fail. 2022-06-29 00:13:57 +05:00
.gitignore Update gitignore. 2021-11-20 04:38:04 +05:00
.gitlab-ci.yml Initial commit. 2021-06-06 23:13:55 +05:00
.golangci.yml Initial commit. 2021-06-06 23:13:55 +05:00
README.md Initial commit. 2021-06-06 23:13:55 +05:00
go.mod Initial commit. 2021-06-06 23:13:55 +05:00

README.md

Hosts translator

This repository contains hosts file to different DNS systems translator.

Why

While it may sound crazy - why do anyone need to translate hosts file? - it has own specific use case.

I have some internal DNS servers powered by PowerDNS and actually do not want to tinker with hosts file for adding ability to use systems and servers at work. So instead of modifying hosts file on every system I have I just launching hosts translator and it seamlessly (more or less) updating DNS server data with provided hosts file.

Caveats

PowerDNS storage provider

  1. It assumes that server ID is 'localhost'. It is 'kind-of-default', especially if native database replication is used for zones distribution.
  2. It assumes that every domain has only one address.
  3. It assumes IPv4 usage. Some additional love is required for proper AAAA support.

Installation

TBW

Configuration

TBW