[PR #95] [CLOSED] Add forwarder capability #130

New issue

Closed

opened 2026-02-28 14:16:30 +03:00 by kerem · 0 comments

kerem commented

2026-02-28 14:16:30 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/abh/geodns/pull/95
Author: @faide
Created: 5/27/2016
Status: ❌ Closed

Base: master ← Head: master

📝 Commits (2)

7b03400 Adding support for forwarder
0fdf185 Remove uninteresting logging

📊 Changes

2 files changed (+56 additions, -1 deletions)

View changed files

📝 geodns.go (+8 -0)
📝 zones.go (+48 -1)

📄 Description

Hi there,

I added a simplistic forwarder support and I would like to discuss of its usefulness and design with you. This is by no way a final implementation.

My aim through this PR and the previous one is to be able to use geodns as a DNS server for internal networks. This kind of use case obviously needs forwarding (more than geocoding)

If you are interested in this allowing me to support this use case I think I'll need to implement caching for the forwarded request (using the TTL as an expiration timer) to improve performance and lower the burden on the upstream DNS.

What do you think?

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/abh/geodns/pull/95 **Author:** [@faide](https://github.com/faide) **Created:** 5/27/2016 **Status:** ❌ Closed **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (2) - [`7b03400`](https://github.com/abh/geodns/commit/7b034003f5a8e2192309fea2ab085f70592af63c) Adding support for forwarder - [`0fdf185`](https://github.com/abh/geodns/commit/0fdf185eb659b13ab6766c9e4bc9690110354406) Remove uninteresting logging ### 📊 Changes **2 files changed** (+56 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `geodns.go` (+8 -0) 📝 `zones.go` (+48 -1) </details> ### 📄 Description Hi there, I added a simplistic forwarder support and I would like to discuss of its usefulness and design with you. This is by no way a final implementation. My aim through this PR and the previous one is to be able to use geodns as a DNS server for internal networks. This kind of use case obviously needs forwarding (more than geocoding) If you are interested in this allowing me to support this use case I think I'll need to implement caching for the forwarded request (using the TTL as an expiration timer) to improve performance and lower the burden on the upstream DNS. What do you think? --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>