Benny Amorsen wrote:
The default device's DNS information gets added first, and each active
device's DNS information is appended.
In the near future when most providers close their DNS relays, this
probably won't work very well. At that point you can only reach the
DNS of a provider if your source address is from that provider.
It's just the wrong thing to do in any case. One set of servers may
resolve your private zones and there's no way for anything to guess
which one.
I don't see a way around implementing a DNS relay daemon. DNS is
getting too complicated for a resolver library (and the limit of 3 DNS
servers is way too low.)
We already have a dns relay daemon... But again there is no information
that would tell you how to splice the forwarders in dynamically. And
you have the same situation with routing. DHCP can only provide a
default gateway which isn't sufficient for multiple connections and
particularly for a mix of public and private subnets that require
specific routes toward additional private subnets. I think the best you
can do in this regard is to provide the tools to easily create stable
fixed servers that understand your private topology and DNS views that
can then offer DNS and NAT forwarding to any desktops plugged in behind
them.
--
Les Mikesell
lesmikesell@xxxxxxxxx
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
