DNS (named.conf) configuration

DNS (named.conf) configuration

Post by Cheno » Thu, 19 Sep 2002 16:32:22



Helo.

I'm in the process of setting up a DNS Server for our office.

The setup:
a Small office using a Dailup acc for intern access.
Using Redhat 7.3, with bind 9.
Clients include Linux, and Windows machines.

I need the win and linux clients on our lan to make use of the local
DNS Server (that I am setting up) for browsing the net, but also for
Name resolution for the local clients.

ISP's DNS ip's: Primary 196.2.45.101
                Secondary 196.2.16.3

DNS Server on lan's ip: 192.168.0.3

On the DNS Server the only thing in resolv.conf is: "nameserver
127.0.0.1"

And this is how I've changed my named.conf, but named fails to
start...

##########################################

// generated by named-bootconf.pl

options { forward first
          forwarders { 196.2.45.101;
                       192.2.16.3;
                     }

Quote:};

//
// a caching only nameserver config
//
controls {
        inet 127.0.0.1 allow { localhost; } keys { rndckey; };
Quote:};

zone "." IN {
        type hint;
        file "named.ca";

Quote:};

zone "localhost" IN {
        type master;
        file "localhost.zone";
        allow-update { none; };

Quote:};

zone "0.0.127.in-addr.arpa" IN {
        type master;
        file "named.local";
        allow-update { none; };

Quote:};

include "/etc/rndc.key";

################end######################

My questions are:
1. Can anyone see anything wrong?
2. With this setup (when its fixed) Will I be able to run a IMAP
server for our lan only.

Any help would be appreciated.

Thanks!

Derek Chenome Pienaar.

 
 
 

DNS (named.conf) configuration

Post by Jeroen Geilma » Fri, 20 Sep 2002 05:21:29




Quote:> Helo.

> I'm in the process of setting up a DNS Server for our office.

> The setup:
> a Small office using a Dailup acc for intern access.
> Using Redhat 7.3, with bind 9.
> Clients include Linux, and Windows machines.

> I need the win and linux clients on our lan to make use of the local
> DNS Server (that I am setting up) for browsing the net,

Erm.
As far as I can tell, nobody has *ever* browsed the net with a DNS
server...you'd want a browser for that :)
You want (and need!) Squid: www.squid-cache.org.
You'll thank me later.

Quote:> but also for
> Name resolution for the local clients.

Why ? Do you have special requirements that make this necessary ?
It usually isn't needed, since these machines aren't connected to the
Internet anyway, and Windoze uses its own name server "scheme" (yes I
use the term loosely here).

Quote:> ISP's DNS ip's: Primary 196.2.45.101
>                 Secondary 196.2.16.3

> DNS Server on lan's ip: 192.168.0.3

> On the DNS Server the only thing in resolv.conf is: "nameserver
> 127.0.0.1"
> And this is how I've changed my named.conf, but named fails to
> start...

Error logs, show error logs ! furrfu...

<snipd>

Answers:
1. If you want to resolve names for your LAN, then you need to have a
domain - where is it? Create a fake domain that only works from the
inside.
2. You can always run an IMAP server - why would you need a DNS server
for this ? Oh sure, it's NICE - but not necessary.

J

 
 
 

1. help: DNS 4.1.2, named.boot, resolv.conf


directory /etc/named.d
cache   .       named.cache
secondary add.your.domain <IP addr. of primary NS>
secondary 12.34.56.IN-ADDR.ARPA <IP addr. of primary NS> ; Reverse DNS resolv.

etc....

Regards,
Luca Polo.
--
+-----------------------------------------++---------------------------+


| address and phone numbers)              || Universita` di Padova.    |

2. Quake2 can't find ref*.so files

3. /etc/resolv.conf and DNS --- *must* named be running?

4. help /w iptables

5. How to setup named.conf to forward request to dynamic DNS servers ?

6. Laptop : Top 5 Buying Tips

7. FreeBSD 3.1 DNS named.conf

8. killing zombied processes

9. DNS how-to named.conf

10. DNS name different from rc.conf hostname... is that okay?

11. Newbe qusetion about DNS configuration Need Help - named.fil (0/1)

12. probs DNS named configuration

13. Problem with DNS named configuration.