[BlueOnyx:11375] Re: DNS Import issue

[Stephanie Sullivan]

> -----Original Message-----
> From: blueonyx-bounces at mail.blueonyx.it [mailto:blueonyx-
> bounces at mail.blueonyx.it] On Behalf Of Gerald Waugh
> Sent: Saturday, August 11, 2012 12:46 PM
> To: jon at ontarioweb.ca; BlueOnyx General Mailing List
> Subject: [BlueOnyx:11155] Re: DNS Import issue
> 
> On 08/10/2012 03:29 PM, Jon McCauley wrote:
> >> Hi Jon,
> >>
> >>> Aug 10 14:19:02 BO25 named[12762]: /etc/named.conf:299: zone
> >>> '26/32.135.xxx.xxx.i
> >>> n-addr.arpa': already exists previous definition:
> /etc/named.conf:39
> >>> Aug 10 14:19:02 BO25 named[12762]: reloading configuration
> failed: failure
> >>>
> >>> So I remove it from the /etc/named.conf and named restart and all
> is
> >>> fine but this file is automatically re-generated...where would I
> go to
> >>> resolve this issue....
> >> It's probably listed twice in CODB as well. Go to the GUI for DNS
> >> management and delete the reverse record in question and see if
> that helps.
> > I have looked for it...I have tried tar up the file and then
> exacting it
> > I seem to get TAR issue
> > tar: Skipping to next header
> > tar: Child returned status 1
> > tar: Error is not recoverable: exiting now
> >
> > I have tried a few times now and get a different result every time
> seems
> look in the GUI setting top level 'network'
> I have found such listed there and deleting cures it
> 
> Gerald

This old thread is relevant to what I have seen. I recently migrated DNS
from a really old RaQ to BX5108 using DNSImport.pl. It worked great except
EVERY reverse (ptr) record was created twice. If I went into any ptr (many
had a "0" last octet in the mask) record in the DNS UI and edited it,
everything got straightened out. Removing and recreating the ptr had the
same effect.

While it's possible to work around it really was kind of a PITA with about
45 of them to fix. It should probably be noted as a bug in DNSImport.pl,
though not high priority.

I'm also catching up on the list so if I haven't gotten to the message that
announced the fix, forgive me! :-)

	Thanks,
		-Stephanie