How to specify custom port for "forward-host/stub-host"?
Jan Komissar (jkomissa)
jkomissa at cisco.com
Mon Feb 5 14:12:37 UTC 2018
I don’t think stub-host supports @<port>, only stub-addr does.
From: Unbound-users <unbound-users-bounces at unbound.net> on behalf of "unbound-users at unbound.net" <unbound-users at unbound.net>
Reply-To: Alex Simenduev <shamil at bringg.com>
Date: Monday, February 5, 2018 at 7:39 AM
To: Over Dexia <over at dexia.de>
Cc: "unbound-users at unbound.net" <unbound-users at unbound.net>
Subject: Re: How to specify custom port for "forward-host/stub-host"?
This doesn't work for me:
stub-host: consul.mydomain.com at 8600 #
This will work:
stub-addr: 18.104.22.168 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 "consul.mydomain.com<http://consul.mydomain.com>" host, but adding @PORT resolving fails, in the log I see it tries to resolve "consul.mydomain.com<http://consul.mydomain.com>?8600" (the ?8600 part is wrong IMO)
On Mon, Feb 5, 2018 at 10:41 AM, Over Dexia via Unbound-users <unbound-users at unbound.net<mailto:unbound-users at unbound.net>> 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...
More information about the Unbound-users