NAPTR issue with HPUX

[Chris Buxton]

Did you really mean to write BIND 9.0? Really?

I can't say for sure, but I'm going to guess that BIND 9.0 (if that's  
really what you're using) is the problem. RHAS 4 uses BIND 9.2.4, a  
much more recent vintage that has a much better chance of supporting  
NAPTR records.

The NAPTR record is relatively new. You should see error messages in  
your logs on the HP/UX server that tell you why the zone is being  
rejected. For example, an unknown record type.

Chris Buxton
Men & Mice

On Mar 12, 2007, at 11:33 PM, Mohamed Navas V wrote:

> Hi list,
> We are running 2 dns servers with bind 9.0 and HP 11i as the OS. We
> are failing with NAPTR records to resolve as per the below entries.But
> this is working with RedHat Linux AS4.
> Is there any bugs with HPUX for NAPTR records ?
> ---------------------------------------------------------------------- 
> ------------------------------------
> IN NAPTR 150  50  "s"  "SIPS+D2T"     ""   
> _sips._tcp.cps1.ims.test.com.
>  IN NAPTR 90   50  "s"  "SIP+D2T"      ""   
> _sip._tcp.cps1.ims.test.com.
>  IN NAPTR 100  50  "s"  "SIP+D2U"      ""   
> _sip._udp.cps1.ims.test.com.
> ---------------------------------------------------------------------- 
> ------------------------------------
> thanks,
>
> Br
> Navas
>
>