Originally posted by: GregGraham
Well, I see their are a lot of people monitoring and helping on this forum. /sarcasm_off.
The F40 Lives. named is now working again.
Although I had no posts to help me, in the interest of recording resolutions to problems....
Here is what happened:
AIX 4.3.3 uses named4 which from what i gather around year 2000 was being phased out. (replaced by named8).
named4 uses /etc/named.boot, a text file defining the zones for named. A security conscious partner, with no UNIX experience at all let alone AIX and its subtleties, decided to move to named8. Created named.conf and REMOVED named.boot. Then he was totally confused by symbolic links and dropped the ball. That was 18 months ago.
Last Monday, a planned power interruption took place. I assumed (never do that) our Liebert UPS would hold for the 4-5 hour outage. I was wrong. The outage was about 12 hours and the datacenter had to be shut down. On restart, named crashed.
named4 does not like starting without a named.boot file in /etc.
The resolution was simply to recreate /etc/named.boot
I hope this helps somebody down the line sometime.
In the past IBM manufactured good solid systems. I can't speak for the hardware they build today. This is one box that has been rock solid. The only reason it is still in a production environment is because it is still running. One of the two RAID5 arrays have failed. The Backplane and controller are fine, I just can not find drives(affordable). I will keep power to this old reliable lady until she has a major failure. I like old stuff because it works, lasted a very long time, and did not need updated just for the sake of updating. The new mantra of "lets fix this because it works" is sad. Windows 98, Vista and 8 come to mind.
But i digress.
Greg