On Tue, 2008-09-16 at 11:23 -0500, Les Mikesell wrote: > For private ranges/domain views, you'd normally either have a local DNS > server configured as primary or secondary for those zones that can > also resolve public addresses, or for roaming vpn users you'd use a > similar central private server that can resolve everything, public or > private while you are connected. You'll quickly go insane if you try to > mix unrelated private connections (for example, if there really are > different parts of your 10.x.x.x range that don't know about each > other). If there isn't some 'other' part of your 10.x range, you can > point the whole /8 to a server that knows about the part you use. I have a private network which has its own non-public name server. I connect to a VPN with "similar" addresses (10.x.y.z) that doesn't know a thing about my home network (and neither should it). From my POV, that bind still doesn't allow to properly separate responsibilities here is an oversight that needs fixing. Nils -- Nils Philippsen "Those who would give up Essential Liberty to purchase Red Hat a little Temporary Safety, deserve neither Liberty nils@xxxxxxxxxx nor Safety." -- Benjamin Franklin, 1759 PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011 -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
