Hello!
No, you are definitely not having a deja vu. That thread, however
deals with a separate issue. I've already made the necessary
modifications, so now the stack can decide, which interface to send
the packets through if there is no default interface. This one is
about DNS not being aware of
Oh yes! And you were the OP of that thread! I do need vacations...
My mistake, I don't see a difference. Sorry, don't want to inject noise
in your thread, I just don't see how DNS is different from other
applications. This to me is the same source routing issue and you will
face it for every
Sergio R. Caprile wrote:
This to me is the same source routing issue and you will
face it for every application in which you need some specific
destination associated to a specific source address/interface.
It is, but this one is an additional problem to make one application use the
source
Hi Mark,
I am completely missing what this has to do with DNS.
We obviously must make sure, that the DNS query is
made through the ethernet interface.
No. A DNS query is not made through an interface. A query
is made to a configured name server, wherever the name server is,
on whatever
Can you pass a nameserver to use to resolving functions normally?
No. As you suspect the name server is never passed to these functions.
The reason for that is that in context of a DNS query the name server address
is static, independent of the query.
Of course for debugging purposes, when
