resolv.conf for certains domains

Hi,

Im wondering if its possible to tell resolv.conf (or any other if it
exist) that for certain domain use one DNS server, and for all the
others (like a default gateway in a network environment) use other DNS
server.
Its that possible?.

Tnx!

On Tue, 19 Sep 2006 02:35:02 -0700, tonia wrote:

> Hi,
>
> Im wondering if its possible to tell resolv.conf (or any other if it
> exist) that for certain domain use one DNS server, and for all the
> others (like a default gateway in a network environment) use other DNS
> server.
> Its that possible?.
>
> Tnx!


nope.

you can use pdnsd to act as a local DNS server.
Point your boxes to your pdnsd server and configure
it so that it uses differne DNSes for different
domains.

--
D.A.M. - Mothers Against Dyslexia

see http://www.jacksnodgrass.com for my contact info.

jack - Grapevine/Richardson

On 19 Sep 2006, in the Usenet newsgroup comp.os.linux.networking, in article
<(E-Mail Removed) .com>, tonia wrote:

>Im wondering if its possible to tell resolv.conf (or any other if it
>exist) that for certain domain use one DNS server, and for all the
>others (like a default gateway in a network environment) use other DNS
>server.

Using DNS, no. DNS works under the concept that the name server you ask
knows all (or can ask the right remote servers). The resolver code believes
the first answer it receives - even if that answer is "I don't know".

The usual cause of this problem is a local (more correctly, a "non-public")
domain, such as "tonia_s.casa". If you ask the Internet name servers from
your ISP, no one has heard of that domain - the answer is NXDOMAIN - and
your application is told "unknown host".

The usual solutions are to use the functions of /etc/nsswitch.conf
(/etc/host.conf for old applications) to cause the resolver to look in the
/etc/hosts file first. For larger domains, the Sun Yellow Pages (NIS) may
substitute for the hosts file.

Another solution is to run a forwarding name server on the local domain.
It answers DNS queries for "tonia_s.casa", and forwards _other_ queries
to the ISP name servers. Or, the name server may recursively resolve the
external addresses using a root hints file. See the DNS-HOWTO.

Old guy

On Tue, 19 Sep 2006 14:56:39 -0500, (E-Mail Removed) (Moe Trin) wrote:

>Another solution is to run a forwarding name server on the local domain.
>It answers DNS queries for "tonia_s.casa", and forwards _other_ queries
>to the ISP name servers. Or, the name server may recursively resolve the
>external addresses using a root hints file. See the DNS-HOWTO.

I use dnsmasq, it does local lookups first, then forwards remaining DNS
queries, it avoids the recursive lookups that running a full name server
involves.

Plus, dnsmasq provides DHCP services for a small network, couple years
in operation -- I like it.

Grant.
--
http://bugsplatter.mine.nu/

Grant <(E-Mail Removed)> writes:

> On Tue, 19 Sep 2006 14:56:39 -0500, (E-Mail Removed) (Moe Trin) wrote:
>
> >Another solution is to run a forwarding name server on the local domain.
> >It answers DNS queries for "tonia_s.casa", and forwards _other_ queries
> >to the ISP name servers. Or, the name server may recursively resolve the
> >external addresses using a root hints file. See the DNS-HOWTO.
>
> I use dnsmasq, it does local lookups first, then forwards remaining DNS
> queries, it avoids the recursive lookups that running a full name server
> involves.

Also, it can be configured to do exactly what was asked for -- it can
forward queries to different DNS servers depending on domain. I use
it set up so that queries to the top-level domain ".vpn" go to a
machine that's running a DNS server and openvpn server (so I can get
to my vpn by machine name, not IP address), and all else goes to
whatever dns server the network I'm currently on wants it to go to.
--
Joseph J. Pfeiffer, Jr., Ph.D. Phone -- (505) 646-1605
Department of Computer Science FAX -- (505) 646-1002
New Mexico State University http://www.cs.nmsu.edu/~pfeiffer

great!
gonna try that.

Thanks all for the responses!


Joe Pfeiffer wrote:
> Grant <(E-Mail Removed)> writes:
>
> > On Tue, 19 Sep 2006 14:56:39 -0500, (E-Mail Removed) (Moe Trin) wrote:
> >
> > >Another solution is to run a forwarding name server on the local domain.
> > >It answers DNS queries for "tonia_s.casa", and forwards _other_ queries
> > >to the ISP name servers. Or, the name server may recursively resolve the
> > >external addresses using a root hints file. See the DNS-HOWTO.
> >
> > I use dnsmasq, it does local lookups first, then forwards remaining DNS
> > queries, it avoids the recursive lookups that running a full name server
> > involves.
>
> Also, it can be configured to do exactly what was asked for -- it can
> forward queries to different DNS servers depending on domain. I use
> it set up so that queries to the top-level domain ".vpn" go to a
> machine that's running a DNS server and openvpn server (so I can get
> to my vpn by machine name, not IP address), and all else goes to
> whatever dns server the network I'm currently on wants it to go to.
> --
> Joseph J. Pfeiffer, Jr., Ph.D. Phone -- (505) 646-1605
> Department of Computer Science FAX -- (505) 646-1002
> New Mexico State University http://www.cs.nmsu.edu/~pfeiffer

tonia <(E-Mail Removed)> wrote:
> Im wondering if its possible to tell resolv.conf (or any other if it
> exist) that for certain domain use one DNS server, and for all the
> others (like a default gateway in a network environment) use other DNS
> server.

If you use DHCP then it should already do that - I had to tweak my laptop
to /stop/ it changing resolv.conf.

If you don't use DHCP then you need to think about how you tell your PC
which domain it's in, but you could probably automate the resolv.conf
change with a script in ifup.d (or equivalent).

Chris