Currently Being ModeratedMar 22, 2011 7:01 AM (in response to chrisn81)My experience about DNS problems indicate that if you manage to rebuild the records just the same way, the services should work like before. My DNS went nuts some time ago and I just rebuild it, and all worked again
First I would recommend you stop all the services if possible, and then configure the DNS, and test it. When it's back up and working like before, with the same names and records, then start up the services one at a time and test them.iMac 27"
Currently Being ModeratedApr 13, 2011 12:07 PM (in response to chrisn81)Starting and Stopping the DNS Service
To start DNS service:
$ sudo serveradmin start dns
Got me running again.Macbook, Mac OS X (10.5.4), In our office we have a Mac Mini Server, and about 10 macs of various flavors
Currently Being ModeratedApr 13, 2011 12:24 PM (in response to chrisn81)This statement is a key detail:
So I started the service, this time it started, but something went wrong.
We really need to know what went wrong here. That's probably going to generate some details into the DNS server logs, but it could be something else that's causing the problems here.
Do you have another box on your LAN that you can promote to at least temporary duty as a DNS server while you fix this? (That's likely the easiest approach. Get a DNS server online on another LAN box that need only know about the busted host, and aim the busted host at it.)
If you don't and you really want to try the reset (and I'd definitely look for what went wrong here before a low-level reset), you can rename or can edit the underlying and low-level DNS configuration files, but I'd not recommend that approach as a first or second-line technique. (You'd need to have some comfort with the Terminal.app shell environment, with the DNS configuration files and with a shell text editor, as a starting point. That's far from unsurmountable, of course.)
Currently Being ModeratedFeb 4, 2012 5:52 AM (in response to chrisn81)
Some time ago I experienced several DNS service crashes in Lion server 10.7.2 (and also 10.7.3).
This may help:
- Stop DNS service in Server Admin or with shell-command "sudo serveradmin stop dns"
- Open Terminal
- Change to /var/named/
- rename all db.* files to db.*.backup
- Rebuild DNS settings in Server Admin
- Start DNS service in Server Admin or with shell-command "sudo serveradmin start dns"
Currently Being ModeratedFeb 4, 2012 9:59 AM (in response to AtzeP)
Before renaming files (been there, tried that, then ran into problems due to have Snow Leopard Server and Lion Server can re-establish settings), I'd encourage a look at the DNS server logs to see why the server is tipping over.