DNS woes resolved!
2008-Jun-08, Sunday 10:55 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
ssurgulFeel the power ..... of Attorney!!
So I finally figured out what seemed to be the issue of my domain no longer responding nor seeming to be registered ANYwhere on the 'nets. Turns out it's relatively important to make sure you keep a valid host name in the zone record for the outside world. If the SOA line doesn't have such a valid host name, curiously no server will really know where to look for the rest of the record, including the machine it's all hosted on. So, problem solved, weeks of frustration resolved though displeasurably so as this was a simple fucking thing to work on, and resolve, and apparently to overlook as well. Now to just get Courier completely configured as the MTA of choice on this bad boy, with the MySQL interface as well, so I can get my receipt of mail working properly again, and then the webmail interface working and I'll be done with the server.
Well, once the fix for Samba 3.0.28a's little problems rolls out, and I'll be able to actually use the 'force-user' and 'force-group' options properly again in the configure file.
So I finally figured out what seemed to be the issue of my domain no longer responding nor seeming to be registered ANYwhere on the 'nets. Turns out it's relatively important to make sure you keep a valid host name in the zone record for the outside world. If the SOA line doesn't have such a valid host name, curiously no server will really know where to look for the rest of the record, including the machine it's all hosted on. So, problem solved, weeks of frustration resolved though displeasurably so as this was a simple fucking thing to work on, and resolve, and apparently to overlook as well. Now to just get Courier completely configured as the MTA of choice on this bad boy, with the MySQL interface as well, so I can get my receipt of mail working properly again, and then the webmail interface working and I'll be done with the server.
Well, once the fix for Samba 3.0.28a's little problems rolls out, and I'll be able to actually use the 'force-user' and 'force-group' options properly again in the configure file.