Re: [opensuse] Have a separate resolv.conf per interface

Doctor Who wrote:
On 2/14/08, Philippe Andersson <pan@xxxxxxxxxxxxx> 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@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

Relevant Pages

  • Re: Windows 2K3 and Virtual Server 2005 guests NAT problem
    ... these machines are not able to connect to our ... internal network. ... If you want to have the two or three VMs on a private ... If you have configured DNS on the host and have set your vms to use this ...
    (microsoft.public.windows.server.networking)
  • Re: Windows 2K3 and Virtual Server 2005 guests NAT problem
    ... these machines are not able to connect to our ... internal network. ... Ethernet adapter "MS Loopback Adapter": ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.networking)
  • Re: Big problem....Big Question
    ... One primary difference is that in going into the DNS Server settings on ... > the machines that work and those that don't. ... Cannot login to the Network Domain after having added the ...
    (microsoft.public.win2000.dns)
  • Re: Not connecting to Domain
    ... The machines are all running windows XP Professional with service pack 2. ... The odd thing is this has suddenly happened on two machines in a network of 30, with no other PCs reporting the same problem. ... is your DNS configured properly? ...
    (microsoft.public.windowsxp.network_web)
  • Local DNS Propagation Question
    ... I have a small home network sitting behind a Linksys Router. ... successfully set up Apache and Local DNS for my network on an Ubuntu ... already belongs to an active site on the internet. ... do not resolve to that site though they resolve to my local one (which ...
    (comp.os.linux.networking)