How to specify custom port for "forward-host/stub-host"?

Jan Komissar (jkomissa) jkomissa at
Mon Feb 5 14:12:37 UTC 2018

Hi Alex,

I don’t think stub-host supports @<port>, only stub-addr does.



From: Unbound-users <unbound-users-bounces at> on behalf of "unbound-users at" <unbound-users at>
Reply-To: Alex Simenduev <shamil at>
Date: Monday, February 5, 2018 at 7:39 AM
To: Over Dexia <over at>
Cc: "unbound-users at" <unbound-users at>
Subject: Re: How to specify custom port for "forward-host/stub-host"?

Unbound 1.6.7

This doesn't work for me:

    domain-insecure: "consul.internal"

   name: "consul.internal"
   stub-host: at 8600 #

This will work:

    domain-insecure: "consul.internal"

   name: "consul.internal"
   stub-addr: at 8600

I'd like to mention that resolving of the host set in `stub-addr` works as expected. Only port is problematic part.
So If I remove @PORT part from it I can see in unbound debug logs that it can successfully resolve the  "<>" host,  but adding @PORT resolving fails, in the log I see it tries to resolve "<>?8600" (the ?8600 part is wrong IMO)

On Mon, Feb 5, 2018 at 10:41 AM, Over Dexia via Unbound-users <unbound-users at<mailto:unbound-users at>> wrote:
Am 04.02.2018 um 15:47 schrieb Alex Simenduev via Unbound-users:
> Adding @port-number doesn't work like for "forward-addrs/stub-addr". Is
> there any way?

Works for me.
Unbound version? Platform? Full config stanza?
Error message? Symptoms?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Unbound-users mailing list