NSAP RR: no leading 0x error near (...)

[Mark_Andrews at isc.org]

> 
> hi,
> after updating bind i get some errors with one of our slave-zone-filez:
> 
> Nov 19 10:26:06 dummy named[5443]: mydomainhere.de:2070: NSAP RR: no 
> leading 0x error near (47.0005.80FF.E100.0000.F215.10F9.0030.4456.1459.56)
> Nov 19 10:26:10 dummy named[5443]: slave zone "mydomainhere.de" (IN) 
> rejected due to errors (serial 30003632) 
> 
> can someone tell /me what this means or better how to fix it ?

	The newsgroup is gatewayed with a mailing list.  Please use
	a valid email address in future.  One would think that you didn't
	want help.

	I would have though that the error message was clear enough.

	The correct way to express a NSAP is to start the address with "0x".

	e.g.
		0x47.0005.80FF.E100.0000.F215.10F9.0030.4456.1459.56

CHANGES:
1216.   [bug]           #1180 completely broke inet_nsap_addr(),
                        inet_nsap_ntoa() still didn't emit the leading 0x.

1180.   [bug]           NSAP processing did not support leading 0x as required
                        by RFC 1706.

README:
        NSAP processing was not RFC 1706 compliant. NOTE: OLD MASTER FILES
        NEED TO BE CORRECTED (0x added to NSAP) AND CACHE FILES REMOVED.

	Mark

> fejf
> 
> -- 
> cat .signature: file not found ;)
> 
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org