Changing DNS cache on home LAN?
Kevin Darcy
kcd at daimlerchrysler.com
Wed Nov 14 03:08:23 UTC 2001
I'm confused. If you're serving 168.192.in-addr.arpa locally then you shouldn't be
getting demand-dialups *regardless* of what your TTL settings are. Everything you need
to resolve those lookups should be local; nothing should require Internet
connectivity. Perhaps some specifics of how you have set up your servers would help...
- Kevin
The Good Doctor wrote:
> In the interest of being able to telnet into my firewall for admin
> purposes w/out causing demand-dial to kick in for a local process, I have
> a caching only nameserver on my home LAN. I finally got everything up and
> running correctly, with one very minor glitch: The reverse lookups for my
> LAN expire too quickly and end up causing a dial-up anyway after all
> things being idle for a day.
> Now, I am going to _guess_ that I need to change one of the TTL's in the
> 192.168.0.rev master zone file in /var/named(this is on a Slackware 8.0
> box running bind 9.1.2). My problem is not knowing which one to change, or how long
> it will allow me to keep my local adresseses in the cache. Preferably I
> would like these to never expire as it is only a small LAN with 4 machines and
> static (192.168.0.x) addresses.
> Any help would be greatly appreciated if this is actually possible,
>
> Doc
More information about the bind-users
mailing list