I am searching for assistance with named and httpd problems on my DirectAdmin VPS at Ramnode. Ideally, I would like to work with someone in the Pacific time zone, but a 3 to 4 hour difference from that is also acceptable.
Previously, I have used Proalix support, but their location in Russia has caused issues as their responses occur when I am typically awake.
Greetings,
I am located in the UK but willing to assist you if location is not a concern. If you find another solution, I wish you the best of luck.
Sincerely,
Andrew
P.S. If this service has been resold to you, have you attempted to request assistance from your provider?
Greetings,
Have you resolved the issue you were experiencing or are you still facing it? If it persists, I suggest reaching out to DirectAdmin support for assistance. Alternatively, if you can provide a clear explanation of the problem, perhaps we can try to assist you.
I am new to this field, but I have gained some experience and now have a few questions. In the past, I purchased hosting, reselling services, VPS|VDS, and a dedicated server. Currently, I want to sell hosting and reselling services again, and my goal is to organize VPS|VDS for resale.
From my understanding, each physical server requires one VDSManager license, which allows you to create multiple virtual root servers on a single physical server. Is this correct? Additionally, can I use VDSManager to limit the traffic flow for future customers' accounts (packages)? My concern is that if one customer uses too much bandwidth, it will affect the other customers' ability to work properly. Is it possible to set different bandwidth limits for each client when creating service packages?
The named issues could stem from a number of causes, like misconfigured DNS records, conflicts with other services, or even firewall settings blocking DNS queries. I'd recommend first checking the configuration files in /etc/named.conf or /etc/named/named.conf depending on your setup. Look for any obvious syntax errors or misconfigurations. Also, ensure that your DNS zones are correctly set up in /var/named/ directory. Running named-checkconf and named-checkzone can also help identify any potential issues in your config files.
For the httpd (Apache) problems, these often involve misconfigurations in your virtual hosts or issues with file permissions. Start by checking the Apache error logs, usually located at /var/log/httpd/error_log or /var/log/apache2/error.log, depending on your distro. These logs are incredibly useful in diagnosing what's going wrong. Common issues include incorrect dоcumentRoot paths, missing index files, or conflicts in your .htaccess files. You can also run httpd -t to test your Apache config for any syntax errors.
Since you're on a VPS at Ramnode, I'd suggest also checking your server's resource usage. Sometimes, issues with named and httpd can be linked to high CPU or memory usage, which can cause these services to fail or become unresponsive. Tools like top or htop can give you a real-time view of what's going on with your server's resources.
If you're looking for ongoing support, given your preference for someone within the Pacific time zone or nearby, you might want to consider a support team based on the West Coast of the US or Canada. There are plenty of managed services companies that offer 24/7 support and can align their response times better with your schedule.
Since Proalix has been an issue due to their location in Russia, you might want to try reaching out to other well-known support providers like Liquid Web or KnownHost. Both have good reputations and might be more aligned with your timezone needs. Alternatively, you could try working with freelance sysadmins on platforms like Upwork or Freelancer, where you can specifically filter for professionals in your desired timezone.
Also, keep in mind that if your issues are frequent, it might be worth investing in some automated monitoring tools that can alert you to problems with named or httpd before they become critical. Something like Nagios or Zabbix could be very useful.
Getting someone in the right timezone who understands your specific setup and issues can make all the difference. Hopefully, these steps and suggestions help you get closer to resolving the issues on your DirectAdmin VPS. If you need any further advice or someone to look over your configs, don't hesitate to reach out.
While Proalix may have provided decent service, their timezone mismatch can be a significant bottleneck in resolving urgent issues. You might want to consider looking for a local hosting specialist or a web administrator who can provide real-time support during your working hours.
Platforms like Upwork or Freelancer have professionals who can assist you. However, be cautious; not all freelancers have the requisite expertise in DNS configurations or Apache server management. Relying on overseas support can lead to delayed responses, which is frustrating when your server is down.