Member Avatar for Ghost

Hi,

I already set up apache. How do I set it to a domain name? Do I have to buy the name?

Thanx.

  • 6 Contributors
  • 10 Replies
  • 224 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by a1whs.com

Dani AI

Generated

Thread already has the right high‑level points from , and . The missing piece is a short, practical checklist for Apache 1.3 that explains common pitfalls and how to verify each step so the host name actually resolves to the correct site.

For name‑based vhosts on Apache 1.3.x the common working config looks like this:

NameVirtualHost *:80

<VirtualHost *:80>
    ServerName www.alexlolololo.com
    ServerAlias alexlolololo.com
    DocumentRoot /var/www/alexlolololo
    ErrorLog logs/alexlolololo-error_log
    CustomLog logs/alexlolololo-access_log common
</VirtualHost>

Notes: ServerName must be the hostname only (no http:// or trailing slash — see ’s example), and NameVirtualHost *:80 is required in Apache 1.3. DocumentRoot must exist and be readable by the webserver.

Quick verification & troubleshooting checklist:

  • Test the Apache config: apachectl -t (fix any errors before restart).
  • Restart gracefully: apachectl graceful or the distro’s service command.
  • If the domain isn’t yet resolvable, simulate it locally by adding a line to the workstation’s /etc/hosts that maps the name to the server IP, or test against the IP while sending a Host header:
    curl -H "Host: www.alexlolololo.com" http://<server-ip>/
  • Verify DNS with dig/nslookup to confirm an A/CNAME points to the server IP and allow time for propagation.
  • Inspect Apache error and access logs (commonly /var/log/httpd/error_log or /var/log/apache2/error.log) for clues.
  • Ensure firewall/router allows incoming TCP/80 (and 443 if HTTPS).

Common causes of “it doesn’t work”: ServerName includes the scheme, NameVirtualHost missing, vhost ordering (first vhost is default), DNS not pointing at the server, or local firewall rules. If a control panel like cPanel is in use (as mentioned), most of these steps are automated.

Recommended Answers

All 10 Replies

Member Avatar for YUPAPA

Yes, you must first buy a domain name
And then you setup a domain name server and zone file for that domain
Next you setup apache and add a virtualHost directive to apache conf file

Member Avatar for ihostdev

if you have cpanel on the server all that will be done by just creating a new account after you purchase the domain

Member Avatar for alexrom

But why I must buy the domain? :!:

Member Avatar for YUPAPA

That is because a domain name cost $$ :sad:

Member Avatar for alexrom

But how can to the domain name provider provide domains??

:!: :!:

:evil:


Alex

Member Avatar for YUPAPA

They pay fees to another provider ... :-|

Member Avatar for blud

There is a body known as internic which has been assigned the responsability of assigning domain names, every provider that sells domain names must purchase them from internic and pay the associated charges.

Here is a list of people that are allowed to sell domains and are Internic Authorized registrars:
http://www.internic.net/alpha.html

Member Avatar for alexrom

I'm a beginner! Apologize me , if my questions are stupid. But how can internic make the domain names work?


:?: I'm working with Apache 1.3.23 and I want to set the ServerName at a Virtual Host with this:

Why it doesn't work? :?: :rolleyes:

Member Avatar for alexrom

Please hepl me!

I'm a beginer so, I don't know very much ..... so please help me!

Thank you ,

Alex

Member Avatar for a1whs.com

Cause u have not purchased that domain u cannot just make a name and call it domain and put a .com after it you have to register so go register it first.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.