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

List:       djbdns
Subject:    Re: resolving domain.com
From:       Brian T Glenn <glenn-dns () delink ! net>
Date:       2004-02-06 13:07:18
Message-ID: 20040206130717.GG4200 () delink ! net
[Download RAW message or body]

On Thu, Feb 05, 2004 at 08:06:36PM -0500, Matthew J. Fanto may have written:
> 
> .domain.com:external-ip:a:259200

Does your registrar have your nameserver listed as "a.ns.domain.com"? If
not, you will run into problems using this line.

Also, do you have more than one nameserver? Many registrars require two,
so you should have a "." line for each of them.

> =machine1.domain.com:local-ip1:86400

If you are creating PTR records, you should also have a "." stating your
authority over in-addr.arpa zone you will be serving. Had you not
obscured your DNS data, we would be able to give you the exact line.

> =domain.com:external-ip:86400

Are you also serving the in-addr.arpa zone from your system? If so, you
should have a "." line for each zone you have been delegated. Otherwise,
switch the "=" to a "+" to avoid making records you won't use.

> +www.domain.com:external-ip:86400
> +ns1.domain.com:external-ip:86400

Aha! it looks like you are using ns1.domain.com as your nameserver's
hostname. Fix the "." line so it matches what your registrar says.

You could also look into using location codes in tinydns to provide
split horizon service. Here is a new data file for you, assuming the
following:

1. you are using 192.168/16 as your local network
2. your external IP is 1.2.3.4
3. The server you are NATting to is 192.168.1.2
4. machine1 on your local LAN is at 192.168.1.3

%LU:192.168
%EX
.domain.com:1.2.3.4:ns1.domain.com:259200::EX
.domain.com:192.168.1.2:ns1.domain.com:259200::LU
.168.192.in-addr.arpa::ns1.domain.com:259200::LU
=machine1.domain.com:192.168.1.3:86400::LU
+www.domain.com:1.2.3.4:86400::EX


This can be tweaked to your needs. Just make sure you have LU as the
location code for internal names, and EX for external names. You can
then use a single hostname and use your DNS on your local LAN (just
throw dnscache on your gateway and point the two zones you are
authoritative for into root/servers/.

HTH,
-- 
Brian T Glenn
delink.net Internet Services
[prev in list] [next in list] [prev in thread] [next in thread]