Hi Alex, I don’t think stub-host supports @<port>, only stub-addr does.
Regards, Jan. From: Unbound-users <[email protected]> on behalf of "[email protected]" <[email protected]> Reply-To: Alex Simenduev <[email protected]> Date: Monday, February 5, 2018 at 7:39 AM To: Over Dexia <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Re: How to specify custom port for "forward-host/stub-host"? Unbound 1.6.7 This doesn't work for me: server: domain-insecure: "consul.internal" stub-zone: name: "consul.internal" stub-host: consul.mydomain.com@8600 # This will work: server: domain-insecure: "consul.internal" stub-zone: name: "consul.internal" stub-addr: 1.2.3.4@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 <[email protected]<mailto:[email protected]>> 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? jo.
