On Sun, 05 Dec 2004 17:01:07 +0000, Salvador Peralta wrote:
> I would've posted this to cp.dns.bind, but my message would not post to
> that group.
>
> I'm changing from a hosting company that I've used for the past several
> years. They used to handle the DNS on my co-located machine. Now I'm
> trying to set it up to handle it myself, and I'm having a few problems:
>
> First, I'd like for ns1 and ns2 to handle DNS requests. For some reason,
> when I dig with the following configuration, I get a "Couldn't find server
> 'ns1.progressivetrail.org': Name or service not known" error. This will
> resolve properly if I dig @jefferson.progressivetrail.org, but not
> @ns1.progressivetrail.org.
>
> Second, the following configuration will resolve
> scoobydoo.progressivetrail.org, but not the TLD progressivetrail.org.
>
> Third, what is the purpose of the Serial line?
>
> What changes should I make to this configuration to get things working
> properly to set this up as a master for this zone?
>
> $TTL 3D
> @ IN SOA ns1.progressivetrail.org.
> ns2.progressivetrail.org. (
> 200211152 ; serial#
> 3600 ; refresh, seconds
> 3600 ; retry, seconds
> 3600 ; expire, seconds
> 3600 ) ; minimum, seconds
>
> NS ns1 ; Inet Address of nameserver
> progressivetrail.org. MX 10 mail ; Primary Mail Exchanger
> ;
> localhost A 127.0.0.1
> jefferson A 67.19.14.187
> ns2 A 67.19.14.188
> mail CNAME jefferson
> ns1 CNAME jefferson
> www CNAME jefferson
> * CNAME jefferson
>
> Thx, Salvador
The value of an NS record cannot be a CNAME. Make ns1 an A record. That is
the main problem.
If ns2 is also a nameserver for the domain, add an NS record for it too.
If you want "progressivetrail.org" itself to resolve to an address you
have to add an A record for it (label "@"). This cannot be a CNAME either.
The serial number enables slaves to tell if the zone file has been
updated. If the value they get from the master is not greater than their
own they assume it has not been and do not transfer it. Normally it is
expressed in format YYYYMMDDnn where the nn is a sequence number you
increment each time you update the file the same day. Yours appears to be
over 2 years old. It should probably be "2004120500". The date format is
just a (convenient) convention; the only thing that is important is that
it is incremented if an update is made so that the slaves know to
transfer it again.
Your expire value is the same as your refresh which is perverse. Your
slaves will keep losing the domain. Make it much much bigger - 2-4 weeks
is typical. Your refresh is rather low too, especially compared to your 3
day default TTL, which is rather high, but that's not serious. Retry is
typically lower than refresh.
The second field of the SOA isn't a second nameserver, it is an email
address in a rather ancient format ("@" replaced by "."). Is your
administrative contact email address really
(E-Mail Removed)? This
won't stop anything working, it's more of a comment really.
The localhost entry isn't needed.
That 3 day default TTL may make it take some time before your changes take
effect over the whole Internet. I would reduce it now, to say 1 hour, and
perhaps increment it again later when you have things stable. But that
won't stop servers which have already cached your data from hanging on to
the old values for 3 days - there isn't anything you can do about that now.
Regards, Ian
Similar Threads
Linear Mode
