|
|
 |  |
Re: Help! I''m a newbie...From: Global Homes Webmaster Date: Wednesday, May 2, 2001
Time: 12:59:42 pmOn 05/02/01 at 14:30, Sean Stephens wrote:
> Andrew
>
> The PTR record is giving me some difficulties (based on my ignorance, I
> guess). What should a PTR record consist of? The ones left over from the old
> guy are totally confusing...
A PTR record should reside in a zone that's named to correspond to the block
of IP numbers to which the PTR belongs. The zone is typically named something
like xxx.yyy.www.in-addr.arpa. and would include PTRs for IP addresses in the
block www.xxx.yyy.zzz. Note that the 'reverse zone' is _not_ the same as any
'forward' domain zone and that authority for it is delegated independently of
any 'forward' zone, usually to or through the ISP or network provider who has
assigned the IP addresses to you. Individual PTR records look like this:
123.yyy.xxx.www.in-addr.arpa. PTR hostname.domain.com.
where hostname.domain.com. is the name of the host (machine) that has the IP
address www.xxx.yyy.123. This example is the simplest case, for a zone that
encompasses an entire Class C block of addresses (www.xxx.yyy.0 -
www.xxx.yyy.255). If you've got less than a Class C block of addresses, it's a
bit more complicated, but the general idea is the same.
> > Wait 7 days for the modifications to soak through the internet and then
> > shutoff QDNS 2 on the original box.
>
> Is there any tried and true method of knowing exactly when this will switch
> over so that I know everything is working from the moment the IP switch
> happens on Network Solutions? How do I know when it has happened?
It will happen gradually as resolvers out on the 'net at large expire the old
info, according to the TTLs (Time To Live) of the records involved, and look
up the new info. Theoretically, it should take no longer than the zone's
Refresh value (the longest time your slave/secondary servers can go before
picking up the new data for the zone from a master/primary) plus the TTL of
the record (the longest time a resolver is allowed to cache the data without
looking it up again from an authoritative server). The world not being a
perfect place, however, it's not always that simple -- there are a few
resolvers out there, run by major ISPs (can you say 'AOL'?) that ignore TTLs
and can hang on to old data in their caches for days or weeks after it should
be expired. You can't really know when all resolvers on the 'net have gotten
the new data, but you can know when your secondary servers have it by querying
them non-recursively.
> P.S. What is a BIND?
Berkeley Internet Name Daemon -- probably the most widely used name server on
the internet. It does effectively the same job as QDNS, but on Unix and its
variants.
Christopher Bort
|

Return to Digital Point Solutions' Home Page |