unbound behind NAT: I think you should be more specific

Ron Varburg ronvarburg at yahoo.com
Wed Nov 27 10:58:59 UTC 2019


 Would you like all queries, no matter what, to be forwarded to 10.0.1.20?
If not all queries, by which criteria do you decide what should be forwarded to 10.0.1.20 and what not?
Have you currently a working unbound server? If yes, can you post its configuration?
Is it running at 10.0.1.20?     On Wednesday, November 27, 2019, 10:35:17 AM GMT, Felipe Gasper <felipe at felipegasper.com> wrote:  
 
 Hello,

    What I’d like is for any query that would otherwise go to “11.22.33.44” (i.e., the public IP) to go to “10.0.1.200” (the private IP) instead.

    Thank you!

-FG

> Le 27 nov. 2019 à 03:03, Ron Varburg via Unbound-users <unbound-users at nlnetlabs.nl> a écrit :
> 
> I couldn't understand what exactly are you asking for. Referring to your example,
> when would you like to forward queries to 11.22.33.44, and when to 10.0.1.200?
> On Tuesday, November 26, 2019, 5:36:00 PM GMT, Felipe Gasper via Unbound-users <unbound-users at nlnetlabs.nl> wrote:
> 
> 
> Hello,
> 
>    Is it possible to give unbound a lookup of public-to-local IP addresses so that it can work with non-loopback NAT setups?
> 
>    We have domains whose DNS is hosted from behind the same NAT where unbound runs. Currently we don’t know of a way for unbound to resolve queries to these domains unless the server has loopback NAT set up, which many do not.
> 
>    Ideally, we’d like for there to be a way to tell unbound that instead of resolving against, e.g., 11.22.33.44, to send the same query to a private address like 10.0.1.200 instead.
> 
>    Thank you!
> 
> -FG
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/unbound-users/attachments/20191127/629e872c/attachment.htm>


More information about the Unbound-users mailing list