NSLint and PTR Record

[David Cost]

Yes, it is in the RRs record:
first this:
borage.com.  IN A 161.184.118.115
mail.borage.com. IN A 161.184.118.115  ; EXTREF
here is the offending line:
115.118.184.161.in-addr.arpa.,type = PTR  host = mail.borage.com

Here is the NSLINT error:
Go back and fix these errors:
nslint: .//tmp/borage.com.959147732:28 "115.118.184.161.in-addr.arpa.,type"
outside zone borage.com.
nslint: .//tmp/borage.com.959147732:28 unknown record type "="
nslint: .//tmp/borage.com.959147732:29 unknown record type "="
nscheck: illegal RR class:
	host = mail.borage.com


Thanks for your look at this.
"Tilman Schmidt" <Tilman.Schmidt at sema.de> wrote in message
news:4.3.1.0.20000523080823.00b0b570 at igate.sema.de...
> At 20:23 22.05.00 +0000, David Cost wrote:
> >Thanks. When I try to create a PTR record using standard syntax for a
> >PTR record in the zone NSLINT rejects it. I was hoping someone may have
> >in fact successfully created a PTR record at Granite that worked for
> >them and did not get rejected by NSLINT.
>
> It might be helpful to see the actual nslint message, but as a wild
> guess, you aren't by any chance trying to put the PTR record in the
> same zone file as your forward (A, MX, etc.) records?
>
> --
> Tilman Schmidt          E-Mail: Tilman.Schmidt at sema.de (office)
> Sema Group Koeln, Germany       tilman at schmidt.bn.uunet.de (private)
>
>
>
>