[TriLUG] Help with caching dns server

[Aaron Joyner]

Yep, that'll work.

The gist of my last message was that you could also replace
'lmr.gotdns.com.' inside the zone file with @, rename the zone file to
something generic, like 'override.gotdns.com', and then just have 4
zone entries with different 'zone "foo.gotdns.com" {' stanzas, which
would cause the name of the zone (foo.gotdns.com, in my above example)
to resolve to 192.168.0.2.

Aaron S. Joyner


On Wed, Sep 24, 2008 at 2:05 PM,  <rvestal at trilug.org> wrote:
> Ok, just for clarification, I need to add an additional zone file for each
> of the 4 websites I host, all using dyndns "free" names, correct?
>
> Ex:
> <snip>
> zone "lmr.gotdns.com" {
>   type master;
>   file "lmr.gotdns.com.zone"
> };
> </snip>
>
> Then create a new zone file:
>
> <snip>
>
> $TTL 900
> @       IN      SOA     ns.mydomain.local. my.email.address. (
>                        200809160 ; serial, todays date + todays serial #
>                        8H    ; refresh, seconds
>                        2H    ; retry, seconds
>                        4W    ; expire, seconds
>                        900 )   ; minimum, seconds
> ;
>                NS      ns    ; Inet Address of name server
>
> @                        IN   A  127.0.0.1
> ns                         IN   A  192.168.0.1
> lmr.gotdns.com.   IN   A   192.168.0.2
>
> </snip>
>
> I'm using virtual directories on one server, so each zone file will be
> pointing to the same IP. The nameserver and the webserver are different
> machines.
>
> Do I understand you correctly?
>
>> Mm... good call!  :D  As an added bonus, for hostnames sharing the
>> same IP, you could share zone files with liberal use of @ and relative
>> naming.
>>
>> Aaron S. Joyner
>>
>>
>> On Thu, Sep 18, 2008 at 10:10 AM, Aaron Schrab <aaron at schrab.com> wrote:
>>> At 09:36 -0400 18 Sep 2008, Aaron Joyner <aaron at joyner.ws> wrote:
>>>>the behavior you want.  The behavior I suspect you really want is to
>>>>just overload the name 'lmr.gotdns.com' internally, and resolve other
>>>>names in the 'gotdns.com' domain from the 'gotdns.com' authoritative
>>>>nameservers.  To the best of my knowledge, this is not possible with
>>>>the standard compile of BIND.  You can do it on the client, via
>>>
>>> This could be done by configuring BIND to be authoritative for a zone
>>> called "lmr.gotdns.com".  If there are other hosts in that same domain
>>> that are to be redefined, each would need to be put in its own zone.
>>>
>>> If this is done, it's especially important to include the trailing dot
>>> in names:
>>>
>>> lmr.gotdns.com. IN A 127.0.0.1
>>>
>>> Alternatively, the @ sign can be used to refer to the zone name:
>>>
>>> @  IN A 127.0.0.1
>>> --
>>> TriLUG mailing list        :
>>> http://www.trilug.org/mailman/listinfo/trilug
>>> TriLUG FAQ  : http://www.trilug.org/wiki/Frequently_Asked_Questions
>>>
>> --
>> TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
>> TriLUG FAQ  : http://www.trilug.org/wiki/Frequently_Asked_Questions
>>
>>
>
>
> --
> TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
> TriLUG FAQ  : http://www.trilug.org/wiki/Frequently_Asked_Questions
>