<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Chris Gebhardt - VIRTBIZ Internet wrote:
<blockquote cite="mid:4B70491D.4070908@virtbiz.com" type="cite">
<pre wrap="">Hi Bret,
Bret Hughes wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I am new to cobalt related boxes but do know my way around a Centos box
ok. I have a client that had a BlueQuartz (BQ) box that was hacked so
we have migrated it to BlueOnyx rather than rebuild it on BQ. For the
most part it went well but for a dns issue. Every time we make a dns
change, named.conf gets a duplicate record for the local host reverse
lookup:
zone "1/32.0.0.127.in-addr.arpa" {
type master;
file "db.1-32.0.0.127.in-addr.arpa";
};
</pre>
</blockquote>
<pre wrap=""><!----><SNIP>
</pre>
<blockquote type="cite">
<pre wrap="">I deleted the zones and the db.1-32* files as well but they get
regenerated.
</pre>
</blockquote>
<pre wrap=""><!---->
Yes, what you don't want to do is manually delete the zones from the CLI
in order to solve the problem.
What you DO want to do is go to the GUI, Server Management > Network
Services > DNS > Edit Primary Services. Then open up the reverse
zone and click REMOVE RECORDS. Get rid of them. You don't need them.
That will fix the problem.
</pre>
</blockquote>
Chris,<br>
<br>
Yep, that did it! Thanks a ton. I was pulling my hair out but
unwilling to just start clicking on stuff without some inkling of what
it would do. <br>
<br>
Bret<br>
</body>
</html>