Hi,

I'm running a fully updated FC5 (as of yesterday), but recently
when I connect to my VPN using NM-VPNC my split-DNS doesn't work.
Named is run with -D:

[EMAIL PROTECTED] ~]$ ps auxww | grep named
named     1608  0.0  0.2  37228  3680 ?        Ssl  Oct16   0:01 
/usr/sbin/named -u named -D

When the VPN comes up, resolv.conf gets updated with a search path,
but perhaps it's not exactly the proper search path..  The search path
is just "corp.mycorp.com", but when I try to resolve a host
"hostname.mycorp.com" it fails.  I'm wondering if this is because the
split-DNS doesn't know that "mycorp.com" should use the internal
nameservers, too?

Is there some way to augment the VPN config so I can add "mycorp.com"
to the search list?  I don't quite understand how split-DNS knows
which domains to search through the internal (VPN) nameservers, but
the behavior seems to be that if it's not on the search list then it's
not using the split-DNS.

There doesn't seem to be enough debugging from the VPNC plugin, so I
can't see what DNS configuration is being passed down from the server.

Help?

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       [EMAIL PROTECTED]                        PGP key available
_______________________________________________
NetworkManager-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/networkmanager-list

Reply via email to