[prev in list] [next in list] [prev in thread] [next in thread] 

List:       djbdns
Subject:    Re: Local DNS for certain hosts in domain
From:       Seth Kurtzberg <seth () cql ! com>
Date:       2006-10-05 23:43:35
Message-ID: 20061005194335.71763a03.seth () cql ! com
[Download RAW message or body]

There is a specific syntax for distinguishing between local requests and external requests.  It's better, actually, to point the internal boxes to a different DNS server than the external boxes; that's the way I handle it.  If you don't want to designate an internal machine as the local DNS server, the internal/external syntax may be a method to do what you need to do.  I say may because I don't know the specifics of your network topology.

On Thu, 05 Oct 2006 23:20:36 +0000
"Mooky Mooksgill" <starman7@hotmail.com> wrote:

> I've certain hosts on my network that I'd like djbdns to resolve -  the way 
> our routing is setup,
> maybe something with NAT, these hosts  cannot be accessed by their public 
> ips from within our LAN,
> and some apps only accept access via FQDN - I've currently dealt with this 
> via individual hosts files -
> but I want to try a better solution ...
> 
> I want to make records for these hosts in djbdns, so our internal users can 
> address them by their FQDN,
> but still be referred to their internal ips. Is this possible?
> 
> I tried adding entries like:
> 
> +moose.moose.com:192.168.1.91:86400
> 
> in djbdns -
> 
> but when queries, djbdns is giving the actual public ip - which as I said
> (for some reason outside of our control) doesn't work on the internal LAN.
> 
> How can I tell djbdns for certain hosts on moose.com to refer to itself for 
> resolution?
> 
> Thanks,
> S7
> 
> _________________________________________________________________
> Find a local pizza place, music store, museum and more_then map the best 
> route!  http://local.live.com
> 
> 
[prev in list] [next in list] [prev in thread] [next in thread]