HOWTO: bind for Internet and 192.168.x.x
Christopher Kings-Lynne
chriskl at nospam.familyhealth.com.au
Wed Feb 2 05:27:58 UTC 2000
Weeeell I have the same sort of setup as you and we have the following to
resolve internal names. This should work independently of resolving
external names I think...:
in named.conf:
zone "internal" {
type master;
file "internal";
};
in 'internal':
@ IN SOA gateway.internal. root.gateway.internal. (
19991116 ; Serial
3600 ; Refresh
900 ; Retry
3600000 ; Expire
3600 ) ; Minimum
IN NS gateway.internal.
; Servers go here
gateway IN A 192.168.0.1
test IN A 192.168.0.1
; DHCP Workstations
work-1 IN A 192.186.0.31
work-2 IN A 192.186.0.32
work-3 IN A 192.186.0.33
work-4 IN A 192.186.0.34
work-5 IN A 192.186.0.35
etc....
Chris
<w00dy at my-deja.com> wrote in message news:874m8g$ve2$1 at nnrp1.deja.com...
> I am running a network that using 192.168.x.x behind the firewall/NAT
> server. Presently I am letting my ISP be my primary and secondary DNS
> server and only using host files on the inside to resolve all the
> 192.168.x.x address.
>
> I would like to host the primary DNS myself. In hosting the DNS
> myself, I would really like to get it setup where it also resolves all
> the machines in the 192.168.x.x network also. How do I set it up that
> way? Especially with the machines that are seen from the outside via
> net? I don't want someone getting my 192.168.x.x, but internally I
> do. How do I control this?
>
> P.S. The firewall/NAT is also the DHCP server (Linux box). Is there
> some why to have DHCP update the DNS server about the dynamic IP
> address of the clients on the inside?
>
> Woody
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>
>
>
More information about the bind-users
mailing list