-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ... The Thursday 2008-02-14 at 14:14 -0500, Aaron Kulkis wrote:
Right now it appears as though when each interface needs to resolve a name, they are both referencing /etc/resolv.conf which will resolve fine for one interface, but not the other.
Which is proper... the DNS reference goes out, and then the the request is ultimately fulfilled by the proper server, which comes to you via the Ethernet or the Wireless, but never BOTH for the same request.
Get yourself a network book, and learn this material, because you're obviously having some difficulty with the basic concepts of how the whole DNS fabric works.
For ANY DNS resolution, there is one, and ONLY one Domain server with the authoritative answer.
The problem is not his, but the network admin's on where he is a guest. Some people setup the local DNS as master of the local network, with no knowledge of the outside world, because the server does not ask outside. Somehow, windows can bypass this at the clients by asking the local server, failing, then asking the outside server. Linux doesn't, because that is contrary to the standard. So what? Since when has windows followed standards? But it works for them. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHtffAtTMYHG2NR9URApcWAJ9C2dp3hLC7AL59mvO4zhuZ6fUcWACfev1f pcencx0LTV8gESZ6IkGUVsA= =Vz6Y -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org