bind/named no found DNS on clients - Redhat

This is a discussion on bind/named no found DNS on clients - Redhat ; hello one and all, i am setting up a centos 5 server and i can't quite get bind/named to work properly. actually, it works great on the linux server, but the other private intranet computer behind the linus server do ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: bind/named no found DNS on clients

  1. bind/named no found DNS on clients

    hello one and all,

    i am setting up a centos 5 server and i can't quite get bind/named to
    work properly. actually, it works great on the linux server, but the
    other private intranet computer behind the linus server do not resolve
    domain names. i have the client computers default gateway and DNS
    server pointing to the linux server ip, i.e., 192.168.0.3. but the
    client computer are not seeing the dns service on server.

    so basically, bind/named is working fine on the server itself, however,
    the client computer accessing the dns server are not able to resolve
    domain names. iptables and routing are working and not the cause on the
    server and also, pinging a hard ip off the client computers is working
    fine. just dns is not working on the client computers. please help.
    thank you in advance.

    lucas

  2. Re: bind/named no found DNS on clients

    On Sun, 13 Jul 2008, in the Usenet newsgroup alt.os.linux.redhat, in article
    , lucas wrote:

    >i am setting up a centos 5 server and i can't quite get bind/named to
    >work properly. actually, it works great on the linux server, but the
    >other private intranet computer behind the linus server do not resolve
    >domain names.


    Fire up a packet sniffer, and see what the query/response look like on
    the wire. Look at the DNS server setup, and make sure it is listening
    on the _network_ interface - eth0 or eth1 as appropriate (and not just
    the loopback interface).

    Old guy

  3. Re: bind/named no found DNS on clients

    well,

    under the file

    /var/named/chroot/etc/named.caching-nameserver.conf

    i added the line

    acl localnet { 127.0.0.1; 192.168.0.1/24; }

    and then changed the following two lines to use this acl localnet as:

    options {
    listen-on port 53 { localnet; };
    ...
    allow-query { localnet; };
    }

    also under:

    view localhost_resolver {
    match-clients { localnet; };
    match-destinations { localnet; };
    ...
    }

    these changes to this file did the trick. very tricky, really. thanx
    for your help.

    lucas

    Moe Trin wrote:
    > On Sun, 13 Jul 2008, in the Usenet newsgroup alt.os.linux.redhat, in article
    > , lucas wrote:
    >
    >> i am setting up a centos 5 server and i can't quite get bind/named to
    >> work properly. actually, it works great on the linux server, but the
    >> other private intranet computer behind the linus server do not resolve
    >> domain names.

    >
    > Fire up a packet sniffer, and see what the query/response look like on
    > the wire. Look at the DNS server setup, and make sure it is listening
    > on the _network_ interface - eth0 or eth1 as appropriate (and not just
    > the loopback interface).
    >
    > Old guy



+ Reply to Thread