A record in zone X, PTR record in zone Y ?

[Jason Mitchell]

Hi Timo,

This is pretty common out in the wild. A lot of ISP's are loathe to 
delegate reverse dns to customers, so it's common to find reverses on 
one NS and forwards on another.

Personally I find it a PITA from an administrative perspective, but it's 
perfectly workable.

Regards,

Jason

Timo Veith wrote:

>Hello bind users,
>
>how common/uncommon is the following scenario:
>
>The A record of a webserver shall be defined on a certain name server.
>Lets call it ns.example.com, The record may look like so
>
>webserver.example.com	IN A	1.2.3.4
>
>The PTR record for this same webserver would be defined on a completly
>different name server. One that is normally responsible for other zones
>that have nothing to do with the one above.
>
>4.3.2.1.in-addr.arpa	IN PTR	webserver.example.com.
>
>Is this a bad habbit or is it ok to do this? At least it seems to be a
>little ugly to me, which is why I ask this here.
>
>The reason behind: Someone of our organisation wants to host a web page
>which shall be accessible under the url of a different organisation. Of
>course, this is arranged with the others before. Normally I would say
>the others have to set up a CNAME, which points to the hostname of the
>webserver at our site. BUT:
>
>The guy at ours wants to use HTTPS and the webserver already uses
>multiple vhosts. Now I know that named based vhosts don't work with SSL.
>    I have to use another IP address for that which leads me to the upper
>question.
>
>TIA and kind regards,
>
>Timo
>
>
>
>
>  
>