[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: named



Giuseppe Greco wrote:

Hi all,

I use named for resolving the names of my internal
hosts... and it works fine.

Just a question: why should I also create the
1.168.192.in-addr.arpa.zone file (192.168.1.0/24)?
What should its content be?

Thanks,
j3d.



in-addr.arpa is for reverse lookup. If you want to reverse resolve 192.168.1.123 to some box, then you need the in-addr.arpa to accomplish this. If you don't want reverse resolution, then you don't need it.

However, lots of services will want to reverse resolve IP addresses, so its's a good idea to implement it.

Here's a sample:

$ORIGIN .
$TTL 86400      ; 1 day
168.168.192.in-addr.arpa IN SOA ns1.somedomain.xyz. bill.somedomain.xyz. (
                               401041028  ; serial
                               28800      ; refresh (8 hours)
                               7200       ; retry (2 hours)
                               604800     ; expire (1 week)
                               86400      ; minimum (1 day)
                               )
                       NS      ns1.somedomain.xyz.
                       NS      ns2.somedomain.xyz.
$ORIGIN 168.168.192.in-addr.arpa.
1                       PTR     firewall.somedomain.xyz.
10                      PTR     w2ksrvr.somedomain.xyz.
11                      PTR     wntsrvr.somedomain.xyz.
12                      PTR     wxpsrvr.somedomain.xyz.


-- Bill Gradwohl bill ycc com http://www.ycc.com spamSTOMPER Protected email


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]