NAPTR issue with HPUX

Mohamed Navas V abusam at gmail.com
Wed Mar 14 04:05:14 UTC 2007


Yes, whitespace is there before IN, also same syntax is working fine
with Redhat Linux AS4..!!

On 3/14/07, Mark Andrews <Mark_Andrews at isc.org> 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
>
>        There are changes of significance in how NAPTR records are
>        process by named between 9.1.0 and current.
>
>        Does you test zone have white space in front of the first IN
>        or not?  If it don't you have accidently create "IN.zone" rather
>        than adding NAPTR records at the current ownername.
>
>        Mark



More information about the bind-users mailing list