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

2018-02-05 Thread Over Dexia via Unbound-users 
Am 05.02.2018 um 15:12 schrieb Jan Komissar (jkomissa):
> Hi Alex,
> 
>  
> 
> I don’t think stub-host supports @, only stub-addr does.


What works for me with @port also is stub-addr resp. forward-addr.
Sorry. I read sloppyly. jo

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

2018-02-05 Thread Jan Komissar (jkomissa) via Unbound-users 
Hi Alex,

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

Regards,

Jan.

From: Unbound-users  on behalf of 
"unbound-users@unbound.net" 
Reply-To: Alex Simenduev 
Date: Monday, February 5, 2018 at 7:39 AM
To: Over Dexia 
Cc: "unbound-users@unbound.net" 
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 
mailto:unbound-users@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?

jo.

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

2018-02-05 Thread Alex Simenduev via Unbound-users 
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" host,  but adding @PORT
resolving fails, in the log I see it tries to resolve
"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@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?
>
> jo.
>

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

2018-02-05 Thread Over Dexia via Unbound-users 
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.

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

2018-02-04 Thread Alex Simenduev via Unbound-users 
Adding @port-number doesn't work like for "forward-addrs/stub-addr". Is
there any way?