Bind Caching Nameserver <was: Re: [CentOS] Caching nameserver--Name Services Cache Daemon (nscd)>
Feizhou
feizhou at graffiti.net
Wed Aug 10 18:05:33 UTC 2005
> >> How can i fix the revrese resolving issue?
>
>
> Number to name resolution is exactly the same as name to
> number, except that the actual names involved are constructed by
> reversing the IP number octets and appending in-addr.arpa.
> If your server isn't configured to answer for your private
> address ranges itself, it will pass the query off to the
> root servers like everything else, and of course no one
> else is going to know anything about your private ranges.
>
> If you look at the entry for zone 0.0.127.in-addr.arpa
> noting that the filename must be different for each zone
> and lives in the directory mentioned at the top (relative
> to the chroot location if your version does a chroot),
> you will see what you need to do. If you have webmin,
> it will offer to build the reverse zones for machines you
> put in forward lookup zones but you can do it by hand or
> find a script that does it if you prefer. To fix your
> nslookup issue you only have to make 192.168.0.200 work,
> so try adding that to understand the principle.
>
> *super dns newb here. How would i go about making it work? i'll take a
> gander inside webmin and see if i can figure it out though*
geez. all this trouble....install djbdns and you will forget about its
existence. Things just work.
In bind, you need to define a 0.168.192.in-addr.arpa zone and create the
stuff similar to the 0.0.127.in-addr.arpa
200 IN PTR your.name.
With djbdns, you can just install and run walldns and
forward/split-horizon queries for 0.168.192.in-addra.arpa to the walldns
instance if you don't need names. or you install tinydns if you want names.
More information about the CentOS
mailing list