[opensuse] Have a separate resolv.conf per interface
I'd like to know if it's possible with openSUSE to have a separate resolv.conf per interface. As way of example, if I'm one one network with wireless and another with my wired connection, I'd like to setup separate DNS entries for each of these interfaces. Is this possible and, if so, how? Thanks! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-02-13 at 11:27 -0500, Doctor Who wrote:
I'd like to know if it's possible with openSUSE to have a separate resolv.conf per interface. As way of example, if I'm one one network with wireless and another with my wired connection, I'd like to setup separate DNS entries for each of these interfaces.
Is this possible and, if so, how?
Using profiles. Set them up with Yast. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHszWJtTMYHG2NR9URAqzkAJ0VjKY4hXYkkqVVUVvpHy51suF81ACfSaJK 55I2BJBXFNgEQ1WefkESmGQ= =N+fI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2008-02-13 at 19:22 +0100, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Wednesday 2008-02-13 at 11:27 -0500, Doctor Who wrote:
I'd like to know if it's possible with openSUSE to have a separate resolv.conf per interface. As way of example, if I'm one one network with wireless and another with my wired connection, I'd like to setup separate DNS entries for each of these interfaces.
Is this possible and, if so, how?
Using profiles. Set them up with Yast.
- -- Cheers, Carlos E. R.
Carlos, Can you please elaborate on how to do this? ___________________________________________________________ The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2008-02-14 at 06:00 -0000, Sudhir wrote:
Is this possible and, if so, how?
Using profiles. Set them up with Yast.
Carlos,
Can you please elaborate on how to do this?
Well, in Yast, select System / Profile Manager, and folllow the wizzard. What this does is store a copy of the configuration files somewhere, and you name it "home" and "office", for instance. When you change the active profile, the changes you did to any configuration files are saved, and the other profile is copied over your configuration. The profile can be choosen at boot somehow. All this is much better explained in the suse manual :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHtCZbtTMYHG2NR9URArGHAJ4+LQMn3xdL1TTlvuiKuLk5UOLeUgCfRJOZ B2U75U3bvMxsPkN2Wnf/86Y= =PQZX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2/14/08, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Thursday 2008-02-14 at 06:00 -0000, Sudhir wrote:
Is this possible and, if so, how?
Using profiles. Set them up with Yast.
Carlos,
Can you please elaborate on how to do this?
Well, in Yast, select System / Profile Manager, and folllow the wizzard.
What this does is store a copy of the configuration files somewhere, and you name it "home" and "office", for instance. When you change the active profile, the changes you did to any configuration files are saved, and the other profile is copied over your configuration. The profile can be choosen at boot somehow.
All this is much better explained in the suse manual :-)
Perhaps I misunderstand. I don't want separate profiles for roaming (one profile for office, one for home, etc.). I was wondering if there was a way to be at one location and have 2 interfaces up simultaneously (such as eth0 and ppp0) and each interface would be on 2 separate networks with each interface having a 'separate, unique' /etc/resolv.conf it is referencing for name resolution. 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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Doc, I think what you're looking for is routing. I'm assuming you have 2 NICs for broandband/internet and 1 NIC for LAN? You'll might find your solution for here: http://lartc.org/howto/. I used to have the same problem also but I don't use linux for my firewall & routing :). Regards, Tommy --- Doctor Who <whodoctor@gmail.com> wrote:
On 2/14/08, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Thursday 2008-02-14 at 06:00 -0000, Sudhir wrote:
Is this possible and, if so, how?
Using profiles. Set them up with Yast.
Carlos,
Can you please elaborate on how to do this?
Well, in Yast, select System / Profile Manager, and folllow the wizzard.
What this does is store a copy of the configuration files somewhere, and you name it "home" and "office", for instance. When you change the active profile, the changes you did to any configuration files are saved, and the other profile is copied over your configuration. The profile can be choosen at boot somehow.
All this is much better explained in the suse manual :-)
Perhaps I misunderstand. I don't want separate profiles for roaming (one profile for office, one for home, etc.).
I was wondering if there was a way to be at one location and have 2 interfaces up simultaneously (such as eth0 and ppp0) and each interface would be on 2 separate networks with each interface having a 'separate, unique' /etc/resolv.conf it is referencing for name resolution.
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 14 February 2008 15:51:44, Doctor Who wrote :
I was wondering if there was a way to be at one location and have 2 interfaces up simultaneously (such as eth0 and ppp0) and each interface would be on 2 separate networks with each interface having a 'separate, unique' /etc/resolv.conf it is referencing for name resolution.
That's a chicken and egg problem. The name has not been resolved yet, but you'd want the system to do the resolution based on the IP address it resolves to... Maybe someone will come with another solution for you, but what you suggest does not seem possible to me. -- *Amand Tihon* Unix System Administrator IBA Particle Therapy | Tel: +32-10-487.724 Fax: +32-10-487.707 http://www.iba-worldwide.com The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation.
Doctor Who wrote:
I was wondering if there was a way to be at one location and have 2 interfaces up simultaneously (such as eth0 and ppp0) and each interface would be on 2 separate networks with each interface having a 'separate, unique' /etc/resolv.conf it is referencing for name resolution.
Why don't you take a look at dnsmasq, it's on the 10.3 DVD. I "think" you can tailor it to treat each interface separately if you get clever with its configuration file. I've used it in other contexts and it works very well. Regards, Lew Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Doc, Are you having problems connecting to *certain* DNS server for resolving because you're connecting to it via a different connection? The problem I had was my ISP refuses connection that doesn't originate from their subscribed line/network because their server doesn't use authentication. If your ISP's DNS server(s) are doing the same also, you can route all traffic to certain (DNS server) IP via certain gateway. That's how I can connect to both of my ISP's servers and still manage to _load balance_ the 99% of the out going connections via 2 connection. Regards, Tommy --- Lew Wolfgang <wolfgang@sweet-haven.com> wrote:
Doctor Who wrote:
I was wondering if there was a way to be at one location and have 2 interfaces up simultaneously (such as eth0 and ppp0) and each interface would be on 2 separate networks with each interface
having a
'separate, unique' /etc/resolv.conf it is referencing for name resolution.
Why don't you take a look at dnsmasq, it's on the 10.3 DVD. I "think" you can tailor it to treat each interface separately if you get clever with its configuration file. I've used it in other contexts and it works very well.
Regards, Lew Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2/14/08, Tommy Pham <tommyhp2@yahoo.com> wrote:
Doc,
Are you having problems connecting to *certain* DNS server for resolving because you're connecting to it via a different connection? The problem I had was my ISP refuses connection that doesn't originate from their subscribed line/network because their server doesn't use authentication. If your ISP's DNS server(s) are doing the same also, you can route all traffic to certain (DNS server) IP via certain gateway. That's how I can connect to both of my ISP's servers and still manage to _load balance_ the 99% of the out going connections via 2 connection.
Regards, Tommy
The problem is this: I'm at a client and need to be on their network to access their machines. I connect to their network via eth0 and am assigned an address via DHCP. However, I cannot get out to the Internet on their network. They have a proxy in place and do not give vendors access. So to get on the WWW, I have a Sprint Wireless card seen as ppp0. I have setup routing such that all traffic goes through the Sprint card with the exeception of traffic bound for their network which uses a different gateway. This works well except for the name resolution piece. Right now resolv.conf is set to use DNS servers provided by Sprint to resolve WWW names, but I want to be able to resolve machine names on their network as well using *their* nameservers. I cannot add that to resolv.conf...doesn't work that way. As long as a nameserver is not down, it will not go on to try other nameservers just because it can't resolve the name you're looking for. I could add a whole bunch of names to my /etc/hosts file, but I'd rather not do that. Windows appears to handle this situation well, I'm just not sure how it does it. Hope this helps to better explain my question. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Doctor Who wrote:
The problem is this:
I'm at a client and need to be on their network to access their machines. I connect to their network via eth0 and am assigned an address via DHCP.
However, I cannot get out to the Internet on their network. They have a proxy in place and do not give vendors access. So to get on the WWW, I have a Sprint Wireless card seen as ppp0. I have setup routing such that all traffic goes through the Sprint card with the exeception of traffic bound for their network which uses a different gateway.
This works well except for the name resolution piece. Right now resolv.conf is set to use DNS servers provided by Sprint to resolve WWW names, but I want to be able to resolve machine names on their network as well using *their* nameservers. I cannot add that to resolv.conf...doesn't work that way. As long as a nameserver is not down, it will not go on to try other nameservers just because it can't resolve the name you're looking for. I could add a whole bunch of names to my /etc/hosts file, but I'd rather not do that. I understand your problem.
Can you not then specify just the DNS of the client ? Their DNS server should be able to resolve Internet names in addition to their internal hosts, and you won't need the proxy to get its answers. HTH Cheers. Bye. Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan@iba-group.com <http://www.iba-worldwide.com> The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation.
On 2/14/08, Philippe Andersson <pan@iba-group.com> wrote:
Doctor Who wrote:
The problem is this:
I'm at a client and need to be on their network to access their machines. I connect to their network via eth0 and am assigned an address via DHCP.
However, I cannot get out to the Internet on their network. They have a proxy in place and do not give vendors access. So to get on the WWW, I have a Sprint Wireless card seen as ppp0. I have setup routing such that all traffic goes through the Sprint card with the exeception of traffic bound for their network which uses a different gateway.
This works well except for the name resolution piece. Right now resolv.conf is set to use DNS servers provided by Sprint to resolve WWW names, but I want to be able to resolve machine names on their network as well using *their* nameservers. I cannot add that to resolv.conf...doesn't work that way. As long as a nameserver is not down, it will not go on to try other nameservers just because it can't resolve the name you're looking for. I could add a whole bunch of names to my /etc/hosts file, but I'd rather not do that. I understand your problem.
Can you not then specify just the DNS of the client ? Their DNS server should be able to resolve Internet names in addition to their internal hosts, and you won't need the proxy to get its answers.
HTH
Cheers. Bye.
Ph. A.
Their DNS boxes only serve to resolve names for internally hosted machines. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Doctor Who wrote:
On 2/14/08, Philippe Andersson <pan@iba-group.com> wrote:
Doctor Who wrote:
The problem is this:
I'm at a client and need to be on their network to access their machines. I connect to their network via eth0 and am assigned an address via DHCP.
However, I cannot get out to the Internet on their network. They have a proxy in place and do not give vendors access. So to get on the WWW, I have a Sprint Wireless card seen as ppp0. I have setup routing such that all traffic goes through the Sprint card with the exeception of traffic bound for their network which uses a different gateway.
This works well except for the name resolution piece. Right now resolv.conf is set to use DNS servers provided by Sprint to resolve WWW names, but I want to be able to resolve machine names on their network as well using *their* nameservers. I cannot add that to resolv.conf...doesn't work that way. As long as a nameserver is not down, it will not go on to try other nameservers just because it can't resolve the name you're looking for. I could add a whole bunch of names to my /etc/hosts file, but I'd rather not do that. I understand your problem.
Can you not then specify just the DNS of the client ? Their DNS server should be able to resolve Internet names in addition to their internal hosts, and you won't need the proxy to get its answers.
HTH
Cheers. Bye.
Ph. A.
Their DNS boxes only serve to resolve names for internally hosted machines.
Bzzt! Wrong. Their DNS boxes only hold records for the names of their internally hosted machines. For any other machine, their DNS boxes pass the query on to another "higher level" DNS box. The process continues, all the way up to the "root level" servers if need be, and possibly down to other lower-level DNS servers until either an authoritative answer is provided, or the server which "should" have the answer replies that it has no such record. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Have you ever thought that they are trying to make it so anyone can use it not just us geeks? Most people I know just know how to turn on the computer. I've use KDE 4 and I like what I see, but it still needs plenty of work. -----Original Message----- From: Doctor Who [mailto:whodoctor@gmail.com] Sent: Thursday, February 14, 2008 1:47 PM To: Philippe Andersson Cc: opensuse@opensuse.org; Tommy Pham Subject: Re: [opensuse] Have a separate resolv.conf per interface On 2/14/08, Philippe Andersson <pan@iba-group.com> wrote:
Doctor Who wrote:
The problem is this:
I'm at a client and need to be on their network to access their machines. I connect to their network via eth0 and am assigned an address via DHCP.
However, I cannot get out to the Internet on their network. They have a proxy in place and do not give vendors access. So to get on the WWW, I have a Sprint Wireless card seen as ppp0. I have setup routing such that all traffic goes through the Sprint card with the exeception of traffic bound for their network which uses a different gateway.
This works well except for the name resolution piece. Right now resolv.conf is set to use DNS servers provided by Sprint to resolve WWW names, but I want to be able to resolve machine names on their network as well using *their* nameservers. I cannot add that to resolv.conf...doesn't work that way. As long as a nameserver is not down, it will not go on to try other nameservers just because it can't resolve the name you're looking for. I could add a whole bunch of names to my /etc/hosts file, but I'd rather not do that. I understand your problem.
Can you not then specify just the DNS of the client ? Their DNS server should be able to resolve Internet names in addition to their internal hosts, and you won't need the proxy to get its answers.
HTH
Cheers. Bye.
Ph. A.
Their DNS boxes only serve to resolve names for internally hosted machines. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2008-02-14 at 13:47 -0500, Doctor Who wrote:
Can you not then specify just the DNS of the client ? Their DNS server should be able to resolve Internet names in addition to their internal hosts, and you won't need the proxy to get its answers.
Their DNS boxes only serve to resolve names for internally hosted machines.
Set up your own dns server as cache, with "forwarders" set to their DNS, and "forward first". The external addresses will fail, and your DNS will then ask the root servers. Another one, could be the option "rotate" in resolv.conf, with two dns defined (man resolv.conf). I haven't tried. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHtJ+ZtTMYHG2NR9URAlgeAKCNrHiybFW2XwsvKFbL6MPOkOkdmwCfZtZe NT6k9RHjNwIShaBN+9IEqaE= =HeI9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 14 February 2008 12:07:52 Carlos E. R. wrote:
The Thursday 2008-02-14 at 13:47 -0500, Doctor Who wrote:
Can you not then specify just the DNS of the client ? Their DNS server should be able to resolve Internet names in addition to their internal hosts, and you won't need the proxy to get its answers.
Their DNS boxes only serve to resolve names for internally hosted machines.
Set up your own dns server as cache, with "forwarders" set to their DNS, and "forward first". The external addresses will fail, and your DNS will then ask the root servers.
Another one, could be the option "rotate" in resolv.conf, with two dns defined (man resolv.conf). I haven't tried.
This is essentially what I suggested a week ago: On Thursday 07 February 2008 12:52:33 Jim Cunning wrote:
| The reason for the behavior you describe is that the resolver is actually | only | calling the first name server in the list, which returns a "No such domain" | (NXDOMAIN) for the FQDNs it does not know about. The list of name servers | is | only used if there is no reply from the first nameserver | queried. From "man | resolv.conf": | | "The algorithm used is to try a name server, and if the query times out, | try | the next, until out of name servers, then repeat trying all the name | servers | until a maximum number of retries are made." | | Unfortunately, I think this means a negative response from any name server | causes the search to terminate. I don't know of any set of resolv.conf | parameters that would do what you want. You might consider trying "option | rotate", however. | | This seems like your client's name server is misconfigured. Apparently it | is | only returning names for its local hosts, and not forwarding queries to any | upstream name servers. It might be possible to put a caching name server on | your laptop, and then have it forward queries to your client's server or | your | ISP's. See http://www.bind9.net/BIND-FAQ. The example they give isn't | quite | your situation, but might give you a clue.
-- Jim
Doctor Who wrote:
On 2/14/08, Tommy Pham <tommyhp2@yahoo.com> wrote:
Doc,
Are you having problems connecting to *certain* DNS server for resolving because you're connecting to it via a different connection? The problem I had was my ISP refuses connection that doesn't originate from their subscribed line/network because their server doesn't use authentication. If your ISP's DNS server(s) are doing the same also, you can route all traffic to certain (DNS server) IP via certain gateway. That's how I can connect to both of my ISP's servers and still manage to _load balance_ the 99% of the out going connections via 2 connection.
Regards, Tommy
The problem is this:
I'm at a client and need to be on their network to access their machines. I connect to their network via eth0 and am assigned an address via DHCP.
Why isn't DHCP assigning DNS as well? That's your problem. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2008-02-14 at 09:51 -0500, Doctor Who wrote:
Perhaps I misunderstand. I don't want separate profiles for roaming (one profile for office, one for home, etc.).
I was wondering if there was a way to be at one location and have 2 interfaces up simultaneously (such as eth0 and ppp0) and each interface would be on 2 separate networks with each interface having a 'separate, unique' /etc/resolv.conf it is referencing for name resolution.
Ah! No, the resolv file is unique, system wide.
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.
No... there are two solutions. a) use a different dns server that resolves any IP. b) adjust routing so that the query goes to the proper DNS, as Tommy Pham suggests. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHtGOhtTMYHG2NR9URAkCPAJ45xidKhMz4SKaDfo18cmrRee9FzACfVAOO 6JzAFzVcsfDqebADL0sztdU= =QsNI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Doctor Who wrote:
On 2/14/08, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Thursday 2008-02-14 at 06:00 -0000, Sudhir wrote:
Is this possible and, if so, how? Using profiles. Set them up with Yast.
Carlos,
Can you please elaborate on how to do this? Well, in Yast, select System / Profile Manager, and folllow the wizzard.
What this does is store a copy of the configuration files somewhere, and you name it "home" and "office", for instance. When you change the active profile, the changes you did to any configuration files are saved, and the other profile is copied over your configuration. The profile can be choosen at boot somehow.
All this is much better explained in the suse manual :-)
Perhaps I misunderstand. I don't want separate profiles for roaming (one profile for office, one for home, etc.).
I was wondering if there was a way to be at one location and have 2 interfaces up simultaneously (such as eth0 and ppp0) and each interface would be on 2 separate networks with each interface having a 'separate, unique' /etc/resolv.conf it is referencing for name resolution.
Then how do you guarantee UNIQUE domain name resolution? With your idea, it's possible to get two DIFFERENT answers -- one from the Ethernet interface, and another from the wireless interface, which is a fundamental violation of the Internet routing model (both for TCP/IP and UDP)
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----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
On 02/16/2008 04:36 AM, Carlos E. R. wrote:
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. You can tell dhcpcd or dhclient to append DNS servers rather than replace, thus giving you access to the whole lot. Presumably, if one doesn't work, it would cycle through the others before giving an error. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2008-02-16 at 07:20 +0800, Joe Morris wrote:
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. You can tell dhcpcd or dhclient to append DNS servers rather than replace,
On 02/16/2008 04:36 AM, Carlos E. R. wrote: thus giving you access to the whole lot. Presumably, if one doesn't work, it would cycle through the others before giving an error.
No, linux doesn't cycle. If the first dns says the name is unknown, it doesn't ask the next. I understand it uses the second server if the first doesn't answer (it is down), which is not the same as saying there is no answer, no ip. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHtibttTMYHG2NR9URAmURAJ9vlR7rXczU7+2KHD1HftVuv2IVEgCgixpQ 6rQDxxNx3FfYdvajbA8HDbc= =0Q7/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 02/16/2008 07:57 AM, Carlos E. R. wrote:
The Saturday 2008-02-16 at 07:20 +0800, Joe Morris wrote:
On 02/16/2008 04:36 AM, Carlos E. R. wrote:
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. You can tell dhcpcd or dhclient to append DNS servers rather than replace, thus giving you access to the whole lot. Presumably, if one doesn't work, it would cycle through the others before giving an error.
No, linux doesn't cycle. If the first dns says the name is unknown, it doesn't ask the next. I understand it uses the second server if the first doesn't answer (it is down), which is not the same as saying there is no answer, no ip.
I think the answer then is to run your own local bind, and add all the possible dns servers as forwarders. Bind definitely can cycle. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-02-17 at 11:55 +0800, Joe Morris wrote:
No, linux doesn't cycle. If the first dns says the name is unknown, it doesn't ask the next. I understand it uses the second server if the first doesn't answer (it is down), which is not the same as saying there is no answer, no ip. I think the answer then is to run your own local bind, and add all the possible dns servers as forwarders. Bind definitely can cycle.
Which is what we told him to do days ago ;-) It seems you can add a "rotate" option to the resolve file. But I think it means that it will rotate on the next query, not on the current one. Ie, one query to server 1, next query to server 2, etc - which is not what he needs. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHuCBGtTMYHG2NR9URAscFAJ9z1OCd4+lz9z0WzuKhdr+or5CgegCeKvPY ORbyki4qVb00VUFFFcMXNhk= =izKJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Doctor Who wrote:
I'd like to know if it's possible with openSUSE to have a separate resolv.conf per interface. As way of example, if I'm one one network with wireless and another with my wired connection, I'd like to setup separate DNS entries for each of these interfaces.
You can do it, but they can't multiple resolv.conf files active at the same time. Multiple resolv.conf files active on different interfaces simultaneously contradicts some of the basic assumptions of the Internet and domain name resolution.
Is this possible and, if so, how?
Thanks!
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (11)
-
Aaron Kulkis -
Amand Tihon -
Carlos E. R. -
Doctor Who -
James R Thompson -
Jim Cunning -
Joe Morris -
Lew Wolfgang -
Philippe Andersson -
Sudhir -
Tommy Pham