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.
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)
Hi Alex,
I don’t think stub-host supports @, only stub-addr does.
Regards,
Jan.
What works for me with @port also is stub-addr resp. forward-addr.
Sorry. I read sloppyly. jo