[lug] Re: reverse DNS info

[Nate Duehr]

Actually, coming from the ISP side, I can say that I've had more
problems getting customers to follow this RFC than getting myself to do
so! :)

Either way, they should use the CNAME method of aliasing described in
this RFC.  Some ISP's get amazingly lazy and set up NS records to do the
delegation and that causes the customer to have a "blind spot" in DNS to
the other users of that Class-C, because the NS and SOA records get
answered incorrectly for the delegated zone.

On Mon, Aug 28, 2000 at 11:00:24AM -0600, John Hernandez wrote:
> There's an RFC 2317 which applies to non-classful boundary delegation of
> reverse DNS records:
> 
> http://www.ietf.org/rfc/rfc2317.txt
> 
> Convincing your ISP to follow these guidelines could be a tricky
> matter.  They will usually prefer the maintenance-free homogenous
> solution, yielding results like 10-9-8-7.customer.isp.com.
> 
> -- 
> 
> John Hernandez, Network Engineer --------------------------------------
> US Department of Commerce                             tel: 303-497-6392
> NOAA/OAR - Mailstop R/OM12                            fax: 303-497-6005
> 325 Broadway                            e-mail: John.Hernandez at noaa.gov
> Boulder, CO 80303                               http://boulder.noaa.gov
> -----------------------------------------------------------------------
> 
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug

-- 
Nate Duehr <nate at natetech.com>

GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
Public Key available upon request, or at wwwkeys.pgp.net and others.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20000829/83ef3424/attachment.pgp>