One place for hosting & domains


      How to Transfer Your Domain Registration to DreamHost (4 Steps)

      So you’ve got a website. Or maybe you juggle multiple websites and domain names. Perhaps you’re unsatisfied with your current registrar, or you’ve found you’re managing too many different things in too many different places.

      If so, it might be time to consider transferring your domain registration. And you might want to consider transferring it to DreamHost.

      Wondering How to Move a Domain Name to a New Host?

      We can help! Subscribe to our monthly newsletter and get domain insights directly in your inbox.

      Why You Should Consider Transferring Your Domain to DreamHost

      1. You Want to Manage Everything in One Place 

      A while back, we surveyed some of our customers, and they told us the No. 1 benefit of using DreamHost was that it gave them the ability to manage as much as possible in one place. 

      More specifically, 60% of customers we asked said the main benefit of using DreamHost was the ability to manage several websites and domains from a single location

      So if you are running several websites under several different registrars, moving them all to one place would make life a whole lot easier.

      2. You’re Being Charged Too Much for Renewals 

      Like any service, prices vary, and those costs can increase when it’s time to renew. If you feel you’re being charged too much for domain registration renewals, the obvious solution is to change registrars.

      3. Support is Lacking 

      As with price, the support offered by different service providers varies a lot. If you’re not getting the help you need from your current registrar, it may be worth moving to one that can fill the gap (like DreamHost). 

      4. You’d Like to Move a Domain from One DreamHost Account to Another

      If you run many websites, there’s always a chance you’re going to be taking over a domain owned by someone using DreamHost. Should this happen, we allow you to transfer domain ownership from one person to another quickly and with minimal effort. 

      In this situation, the easiest solution is just to continue using DreamHost (and potentially move your other domains over too).

      Need-to-Knows When Transferring a Domain

      Understanding what is and isn’t possible when transferring domains can save you tons of time further down the line and help ensure a smooth and pain-free domain transfer. 

      With that in mind, here are a few things you need to know before you start the process of transferring a domain registration.

      1. Only Certain TLDs Are Allowed

      At DreamHost, we support certain TLDs for transfer. However, it’s actually only a handful of TLDs that cannot be transferred. These are: .AM, .AT, .BZ, .FM, .JP, .NET.NZ, .ORG.NZ, .NGO, .ONG, .OOO, and .WS. 

      For more information, you can check out DreamHost’s TLD page for a current list of domain extensions with pricing.

      Additionally, there are also some New TLDs and ccTLDs which are considered premium domains — for example, .LIVE, .ME, and others. DreamHost cannot accept transferring premium domains due to the pricing structures that vary from one registrar to another. 

      If you’d like to use a premium domain for your website, you’ll need to register it directly with Enom or another registrar that sells premium domains. Then you can host the site on your DreamHost account like any other domain. 

      2. Beware of the ICANN 60-day Transfer Lock

      Did you know you can’t transfer your domain during the first 60 days of registration? You need to wait until day 61.

      It’s also worth remembering that you cannot transfer a domain if your last transfer took place within the previous 60 days.

      And remember, transferring a registration only moves your domain. If you’d like to transfer your web hosting service to DreamHost, we can help with that too.

      3. Downtime Can Happen If You Don’t Get Your Nameservers Sorted First

      It’s important to know that if you decide to change your nameservers to DreamHost after completing a transfer, you may experience some downtime. Changes to the nameservers cannot be made while the domain is pending transfer. 

      We recommend that you start the transfer at least a month in advance — this will make sure your domain registration does not expire during the transfer. 

      What Should You Do Before You Request a Domain Transfer?

      We recommend completing three super simple steps before you make your transfer request. This is because of ICANN’s Transfer Policy, which means that following a transfer, changes made to the registrant’s name, organization, or email address will be put on a 60-day lock

      1. Unlock the domain registration. This is done with your current registrar.
      2. Obtain the auth code, also known as the EPP. You can get this from your current registrar.
      3. Remove WHOIS privacy. This is done through your current registrar. This allows your new registrar to recognize the new owner.

      Now you’ve completed all the preparation, it’s time to transfer your domain to DreamHost. The whole process is pretty simple, but just to be sure, here’s what you need to do. 

      How to Transfer Your Domain to DreamHost in 4 Steps

      Four steps — it’s that easy! Let’s walk you through the process of transferring your domain to DreamHost.

      1. Request the Transfer-In With Dreamhost

      Start by logging in to your DreamHost account. You can do that here. If you don’t have an account yet, you can create one here

      From there, you are going to need to navigate to the Reg Transfer page. There you will find a button labeled Start Transfer to DreamHost — click that. 

      DreamHost’s list of info for what you need to know before starting a domain transfer.

      Have you done that? Cool. You should now see this:

      Requesting a domain transfer in the DreamHost panel. 

      In this section, all you need to do is add the domain(s) you would like to transfer to DreamHost and click Request Transfer

      2. Enter your Auth Code, WHOIS Info, and Nameservers

      Now you need to fill in details to show you are the owner of that domain(s). If you want your contact details to stay hidden, just tick the I want all my contact information private button.

      This is free, by the way. We don’t like unnecessary charges!

      Checkbox for making WHOIS contact info private

      You should now see a section asking you to enter all your WHOIS information. As you might suspect, you need to make sure all your details are valid and correct and that you have followed the ICANN policy we mentioned earlier.

      The WHOIS section looks like this:

      Empty WHOIS information fields to be filled out.

      See that little checkbox at the top? If you click that, it will use these details to automatically fill in the four contact fields on the domain registration’s internal ownership details. These are:

      • Admin
      • Billing
      • Registrant
      • Technical details

      The following section is the Auth Code field.

      Your current registrar should have provided you with either an Auth Code or EPP code. Make sure you fill in the fields with the code exactly as provided to you.

      Once that’s done, you should see the following:

      Filling out nameserver information with the “Use another host’s nameservers” option clicked.

      Choose either Use DreamHost’s nameservers (this automatically sets DreamHost’s nameservers for you) or Use another host’s nameservers (you should choose this if you’d like to enter outside name servers manually). 

      Make sure you have read the Registration’s Terms, and click Continue

      You now need to pay for the transfer. 

      3. Pay for Your Domain Transfer

      If you have a free domain registration with your current registrar, you won’t be charged by DreamHost. If you don’t have a free domain registration, you will need to pay for it here. 

      To complete this step, you first need to review your order. 

      Reviewing order total for ‘Transfer + 1 year registration’

      If you need to pay for the transfer, you will know because the fee will appear in the Order Summary. 

      Click the Proceed to Payment Entry button. You then need to confirm the payment, so press the Submit Transfer Request button. 

      Notification showing ‘Transfer Initiated’ submitted and next steps. 

      On the next screen, you simply need to enter your payment details and click the confirmation button. You should now see that the transfer has been initiated.

      Notification showing ‘Transfer Initiated’ submitted and next steps.

      Navigate to the Reg Transfer page, and if all is well, you will be able to see confirmation that the transfer is pending. 

      Example of a pending transfer in the DreamHost panel. 

      When the transfer has completed, payment will be taken from your bank account. 

      Let’s move on to the last step. 

      4. Check That the Domain Status and EPP Code Are Verified, and Transfer Request Is Submitted to the Current Registrar

      Once the transfer is completed, the authorization code and EPP are verified with your current registrar. 

      The registrar then has five days to release the domain to DreamHost, and the transfer will complete within the seven days after. 

      You can confirm the status by running a quick WHOIS check. If the transfer fails, you can get more help by contacting our support team

      There you go — four simple steps as promised!

      That said, there are little things that can go wrong. Let’s discuss some of the most common domain transfer problems our team here at DreamHost comes across and how they can be fixed without needing to contact support. 

      Ready to Switch Your Domain Registrar?

      Search DreamHost’s 400+ TLDs to find the perfect URL for your website.

      3 Common Domain Transfer Issues

      While the steps involved in transferring a domain are simple, that doesn’t guarantee everything will run without a hitch. There are several factors involved, and if you have issues, it could be for one of the following reasons. 

      1. Some domains update their auth code internally. For example, the .org registry has many security measures and can often change EPP codes automatically. If you see this happening, you need to contact your current registrar. You’ll then need to reset the auth code and resubmit the domain transfer request. 
      2. Some domains are transfer locked. You can establish whether this is an issue by looking at the WHOIS information and checking for the following: Domain Status: clientTransferProhibited. If you see this, you’ll have to contact your current registrar to have it unlocked. Once that’s done, you then need to resubmit the domain transfer in DreamHost.
      3. Intermittent issues with the DNS. After a transfer, you may see this issue. This is usually down to domains having previously used DNSSEC. Find out how to fix it in this article. 

      Still running into issues? Check our Knowledge Base or contact support.

      Master Your Domain at DreamHost

      It’s not uncommon for website owners to start with one domain registrar and later move to another. Over time many of us realize we rushed the initial registration process, didn’t do due research, and wound up being charged too much for too little.

      If this includes you, moving your domain registration — to DreamHost or any other registrar — is much simpler than you might at first think.

      In short, you simply need to:

      1. Request the Transfer-In with DreamHost (or your chosen registrar)
      2. Enter the auth code, WHOIS, and nameservers 
      3. Pay for your transfer 
      4. Wait for your domain status and EPP code to be verified and for your transfer request to be submitted to your current 

      If you’d like to register a new domain, we can help with that too! DreamHost .COM domains cost $7.99 a year and come with free, private registration, while other domains start from less than $1/year. Find out more here.

      Source link

      How to Choose the Right Domain Name

      Which is harder: Naming your kid or choosing a domain? 

      Sure, your bambino is stuck with the moniker you choose until they can get a judge to change it, but you won’t need to reinvent the wheel to come up with something to call them. You can look to historical figures, literary characters, or even your favorite TV show for inspiration. 

      However, when it comes to a domain, you’ve got to make sure your digital baby is truly unique. No repeats allowed.

      So what makes a good domain name? 

      Generally speaking, you’ll want something memorable, brandable, and easy for people to type and pronounce. It’s also smart to avoid anything too long or overly specific. By following a few simple guidelines, you can pick out a name that helps to drive more traffic your way. 

      In this guide, I’ll explain why your domain name matters and share 11 factors to consider when making this decision. I’ll also discuss the best places to register a domain and how you can get a free one along with your web hosting. Let’s get started!

      Your Great Idea Starts with a Domain Name

      Don’t let someone else register your dream URL. Search DreamHost’s 400+ TLDs to find the perfect match for your website.

      Why Your Domain Name Matters

      Your domain name is as much a part of your brand as your business name or logo. Even if you’ve nailed your branding in every other respect, if there’s something about your domain name that puts potential customers off, they’ll likely go elsewhere.

      The opposite is also true. If your web address is accurate and as fun to say as it is to use, people will be eager to check it out and share it. First impressions matter, and sometimes your domain is the initial experience people will have of your brand. 

      It’s also not easy to change your domain name after your site is online. You can do it, but it can be time-consuming and does have consequences. It can lead to a loss of traffic and unnecessary downtime. In other words, life will be a lot easier if you take your time now and come up with a name you love.

      11 Important Factors to Consider When Choosing a Domain Name

      As with most big business decisions, you’ll find plenty of opinions about how to select the right domain name. To make it easier, let’s take a look at eleven key points to consider.

      1. Choose Your Top-Level Domain Extension Carefully

      A Top Level Domain (TLD) is the piece of your domain that comes after the site’s name. The most common TLDs are .com, .net, and .org.

      There are plenty of newer TLD options, but it’s usually best to keep it old school and stick to .com if possible. It’s been around the longest and is the most popular, so people are very familiar with it.

      Of course, it’s possible you won’t be able to secure a decent domain name with a .com TLD since many are already taken. However, it’s not the end of the world if you have to use an alternative.

      Alternative TLD options.

      You’ll find tons of available options that can add personality to your web address. Just make sure that whatever you select makes sense for your website and audience.

      2. Incorporate Keywords Strategically

      Keywords aren’t just for content. Search engines use your domain name to understand what your site is about and help determine search rankings. So it’s essential to include keywords where possible. 

      The keywords you choose for your domain name should be relevant to your website. It’s much more important to represent your content accurately than to add keywords for their own sake. If you’re stuck for ideas, you can give Google Keyword Planner a try.

      The Google Keyword Planner home page.

      This free tool lets you explore keywords by search volume and other factors to identify terms people actually use. Don’t get too carried away, though. Using too many keywords, especially popular ones, can make your site seem boring and maybe even a little untrustworthy.

      3. Make Sure Your Domain Is Easy to Pronounce and Spell

      You probably want your domain name to be memorable. However, if you’re thinking of going the Elon Musk baby-naming route, don’t. No matter how cool it looks spelled out, there will come a time when you’ll have to give someone your website or email address verbally.

      Word-of-mouth is still powerful advertising. What’s more, it only works when people can actually pronounce your domain. This also makes the name easier to remember, increasing the odds that people will visit and pass the site along to their networks.

      4. Avoid Hyphens

      Using hyphens may seem like a creative way to get the domain name you want. Unfortunately, they’re tough to express verbally. They also make the domain more difficult to type. Some people will likely forget about them entirely and end up on someone else’s website.

      Generally, when you’re brainstorming domain name ideas, try to avoid anything that isn’t a letter. That includes replacing letters with numbers. Those kinds of touches make the name a lot easier for people to misremember and mistype.

      5. Avoid Using Doubled Letters

      Using doubled letters in a domain name is practically asking for typos. Doubled letters are hard to read and even harder to type correctly.

      If mistakes happen often enough, you may end up with someone typosquatting and stealing your traffic. Plus, having to spend even a few seconds longer than necessary trying to figure out how to spell your domain is an unnecessary distraction.

      6. Keep Your Domain Name Short

      There are several reasons short domain names work better. First, shorter names are easier to remember and type. Therefore, they are beneficial for branding purposes.

      Also, an overly long domain name is yet another way to look suspicious. If you don’t use too many keywords and make your name easy to pronounce, on the other hand, your domain will probably be short naturally.

      7. Stay Unique and Brandable

      A unique domain name can help your business stand out and potentially help you avoid legal trouble. It can also contribute to your marketing efforts, so you’ll want it to be brandable. 

      StitchFix is an excellent example of a unique, brandable name.

      The StitchFix homepage.

      StitchFix checks all the boxes when it comes to marketable domain names. It’s fun to say, doesn’t have any inherent meaning, and is easy to remember and spell.

      8. Pick a Domain Name That’s Flexible

      Your domain name is one area where you don’t want to paint yourself into a box. While you should be specific enough to attract an audience, you don’t want to be so precise that there’s no room for your website to grow. 

      For example, “” might be perfect for a photography blog. However, if you decide to write about other art forms as well, you’ll be stuck with an inaccurate domain name. So it’s smart to consider upfront how your site or business may expand over time.

      9. Do Your Domain Name Research

      Once you’ve narrowed your search down to a few candidates, you can use a research tool to determine if it’s available.

      DreamHost’s domain name research tool.

      However, just because the domain name is available doesn’t mean someone else doesn’t have a valid claim to it. To be safe, you’ll want to perform a trademark search before making your choice.

      It’s also best to make sure you can secure appropriate social media handles. If you can’t get an exact match, try finding something that makes sense with your domain name.

      10. Don’t Get Analysis Paralysis

      Chances are that if you want a domain name, someone else probably wants it too. If you’re sure about your choice, go ahead and buy the domain.

      This is especially recommended if it’s reasonably inexpensive. Plus, if you come up with something better later on, you can always let the registration lapse. You don’t want to end up in a dispute because you didn’t act fast.

      11. Protect Your Brand With Multiple Domains

      Have you ever heard: “If the shoe fits, buy it in every color?” Well, if the domain name fits, buy it in every TLD.

      Even if you manage to snag a coveted .com address, you might consider purchasing other options and setting up redirects. You can even go a step further and buy common misspellings of your domain name.

      Additional domain name suggestions using different TLDs.

      This is a smart strategy to apply to social media as well. Even if you don’t think you’ll use Twitter, you might want to grab a decent handle if one is available. You’ll be ready if you ever decide to tweet, and you’ll prevent anyone else from taking that username.

      Picking the Best Place to Register Your Domain

      Once you’ve picked out a domain name, you need to choose a domain registrar, which is the company where you’ll purchase it. When shopping around for a registrar, here are a few things to keep an eye on:

      • Domain transfers. Check out the registrar’s transfer policy. If it’s complicated or expensive, keep looking.
      • Pricing. Some companies offer lower prices for the first year and then increase them when it’s time for renewal. You may even be locked into a multi-year contract.
      • Expiration policy. You don’t buy a domain so much as rent it. If you forget to renew the lease, someone else can take it from you. Look for a registrar that offers automatic renewals and a grace period.
      • Domain privacy protection. As a website owner, you’re required to add your personal information to a public database. Domain privacy protection hides your primary contact information to help keep your identity secure.
      • Subdomains. You don’t have to register subdomains separately. However, you’ll want to ensure that your registrar makes it easy to add subdomains to your site.

      There are plenty of registrars you can use. However, sometimes it makes sense to register your domain through your hosting provider.

      How to Get a Free Domain With Your Web Hosting

      Some web hosts offer a free domain name when you sign up for a hosting plan. You may have to pay for renewal at the end of the first year, but it’s not typically expensive. You also won’t have to worry about migrating your domain if you register it through your hosting provider.

      At DreamHost, we offer a free domain name when you sign up for one of our Shared or DreamPress hosting plans. Once you’ve selected the right option for you, just click on Register a new domain.

      DreamHost’s free domain with annual web hosting.

      You’ll be prompted to search for your desired domain name. Simply add your domain to your cart and complete the checkout process!

      So Many Potential Domain Names . . .

      There’s a lot to think about when choosing a domain name. After all, it’s one of the first major decisions you’ll make when establishing your online presence. Putting some time and care into this selection can help set the stage for success down the road.

      Fortunately, there’s lots of information you can rely on to help you make your choice. Keeping your domain name short, pronounceable, and easy to remember will get you off to a strong start. Once you have a name in mind, you can follow our suggestions for choosing a registrar and getting a free domain with your web hosting provider.

      Have you settled on the perfect domain name for your website? Get a free private domain registration when you sign up with DreamHost!

      Source link

      Apache Configuration Error AH00558: Could not reliably determine the server’s fully qualified domain name

      Part of the Series:
      Common Apache Errors

      This tutorial series explains how to troubleshoot and fix some of the most common errors that you may encounter when using the Apache web server.

      Each tutorial in this series includes descriptions of common Apache configuration, network, filesystem, or permission errors. The series begins with an overview of the commands and log files that you can use to troubleshoot Apache. Subsequent tutorials examine specific errors in detail.


      An Apache AH00558: Could not reliably determine the server's fully qualified domain name message is generated when Apache is not configured with a global ServerName directive. The message is mainly for informational purposes, and an AH00558 error will not prevent Apache from running correctly.

      In this tutorial you will learn how to detect an AH00558 message using the methods described in the How to Troubleshoot Common Apache Errors tutorial at the beginning of this series. You will also learn how to set a ServerName directive to resolve the message.

      If you have already determined that your Apache server is affected by an AH00558 message and you would like to skip the troubleshooting steps, the Setting a Global ServerName Directive step at the end of this tutorial explains how to resolve the message.

      Troubleshooting Using systemctl

      The first step when you are troubleshooting an AH00558: Could not reliably determine the server's fully qualified domain name message is to check Apache’s status using systemctl. The output from systemctl will in many cases contain all the information that you need to resolve the message.

      On Ubuntu and Debian-derived Linux distributions, run the following to check Apache’s status:

      Ubuntu and Debian Systems

      • sudo systemctl status apache2.service -l --no-pager

      On CentOS Fedora, and RedHat-derived systems, use this command to examine Apache’s status:

      CentOS and Fedora Systems

      • sudo systemctl status httpd.service -l --no-pager

      The -l flag will ensure that systemctl outputs the entire contents of a line, instead of substituting in ellipses () for long lines. The --no-pager flag will output the entire log to your screen without invoking a tool like less that only shows a screen of content at a time.

      You should receive output that is similar to the following:


      ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/apache2.service.d └─apache2-systemd.conf Active: active (running) since Wed 2020-07-29 14:30:03 UTC; 33min ago Process: 34 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS) Main PID: 46 (apache2) Tasks: 55 (limit: 2344) CGroup: /system.slice/apache2.service ├─46 /usr/sbin/apache2 -k start ├─47 /usr/sbin/apache2 -k start └─48 /usr/sbin/apache2 -k start Jul 29 14:30:03 68e2cf19f3f1 systemd[1]: Starting The Apache HTTP Server... Jul 29 14:30:03 68e2cf19f3f1 apachectl[34]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using Set the 'ServerName' directive globally to suppress this message Jul 29 14:30:03 68e2cf19f3f1 systemd[1]: Started The Apache HTTP Server.

      The highlighted line that contains the AH00558 message is the important one. Essentially, it informs you that Apache couldn’t find a valid ServerName directive in its configuration file, so it will use the first IP address it detects. In this example, it’s the server’s public IP address: 172.17.02. If you are troubleshooting an AH00558 message, the IP address that is detected may be different, or it may be a human readable DNS name.

      If your systemctl output contains an auto-detected value of any IP address or hostname, skip to the last section of this tutorial, Setting a Global ServerName Directive to resolve the issue. In that section you will configure Apache with a safe default ServerName value using the IP address for localhost:

      If your systemctl output does not indicate a value that you can use for the ServerName directive, the next section of this tutorial explains how to examine the systemd logs using journalctl to locate an AH00558 message.

      Troubleshooting Using journalctl

      To examine the systemd logs for Apache you will use the journalctl command. When invoking journalctl, there are two specific flags that will help you locate specific messages if there is a large volume of log entries.

      The first flag that you will add to the journalctl invocation is the --since today flag. It will limit the output of the command to log entries beginning at 00:00:00 of the current day only. Using this option will help restrict the volume of log entries that you need to examine when checking for errors.

      The second flag that you will use is the same --no-pager option that you used with systemctl, which will output the entire log to your screen at once.

      On Ubuntu and Debian-derived systems, run the following command:

      • sudo journalctl -u apache2.service --since today --no-pager

      On CentOS, Fedora, and RedHat-derived systems, use this command to inspect the logs:

      • sudo journalctl -u httpd.service --since today --no-pager

      If your Apache server is generating an AH00558 message, look through the journalctl command output for lines like the following:


      -- Logs begin at Wed 2020-07-29 14:30:02 UTC, end at Wed 2020-07-29 14:45:03 UTC. -- . . . Jul 29 14:30:03 68e2cf19f3f1 systemd[1]: Starting The Apache HTTP Server... Jul 29 14:30:03 68e2cf19f3f1 apachectl[34]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using Set the 'ServerName' directive globally to suppress this message Jul 29 14:30:03 68e2cf19f3f1 systemd[1]: Started The Apache HTTP Server.

      The second line of output is the AH00558 message. The line includes the server’s public IP address, which is the address that Apache automatically detects and sets as a default at runtime. With this message as confirmation of an AH00558 error, you can proceed to the Setting a Global ServerName Directive to resolve the issue.

      Otherwise, the next section explains how to diagnose an AH00558 error message using the apachectl command.

      Troubleshooting using apachectl

      An AH00558: Could not reliably determine the server's fully qualified domain name error can be detected using Apache’s apachectl utility. With apachectl you can catch messages like these before reloading or restarting Apache, and you can avoid having to search through systemctl and journalctl logs to locate errors.

      To check your Apache configuration for an AH00558 message, run the following command:

      • sudo apachectl configtest

      You should receive output like the following if your server is affected by an AH00558 error message:


      AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using Set the 'ServerName' directive globally to suppress this message Syntax OK

      As with the previous sections in this tutorial that used systemctl and journalctl to locate AH00558 messages, the line that contains the AH00558 message, highlighted in the previous example, is the important one. Again note that the IP address in this example may be different on your server.

      The next section of this tutorial explains how to set the ServerName directive to resolve AH00558 error messages.

      Setting a Global ServerName Directive

      To resolve an AH00558: Could not reliably determine the server's fully qualified domain name error message, you will need to add a ServerName directive to your Apache configuration. Apache uses the ServerName directive to map incoming HTTP requests to an IP address or DNS hostname using VirtualHost directives in order to handle requests for multiple sites using a single server.

      The error message notes that a global ServerName directive should also be set. Doing so will ensure that Apache can gracefully handle incoming requests that do not map to a VirtualHost without generating additional errors.

      For maximum compatibility with various Apache configurations, use the value of for your global ServerName directive. You can use a different IP address or DNS name that corresponds to your server’s configuration if you need to, but it is safest to use

      On Ubuntu and Debian-derived systems, open the /etc/apache2/apache2.conf file with root privileges using nano or your preferred text editor:

      • sudo nano /etc/apache2/apache2.conf

      Add a line containing ServerName to the end of the file:


      . . .
      # Include the virtual host configurations:
      IncludeOptional sites-enabled/*.conf
      # vim: syntax=apache ts=4 sw=4 sts=4 sr noet

      On CentOS, Fedora, and RedHat-derived systems, open the /etc/httpd/conf/httpd.conf file with root privileges using nano or your preferred text editor:

      • sudo nano /etc/httpd/conf/httpd.conf

      Add the ServerName line to the end of the file:


      . . .
      # Supplemental configuration
      # Load config files in the "/etc/httpd/conf.d" directory, if any.
      IncludeOptional conf.d/*.conf

      Save and close the file when you are finished. If you used nano, do so by pressing CTRL + X, Y, and then ENTER.

      Once you have added the ServerName directive to your configuration, run apachectl to test that the configuration is valid.

      • sudo apachectl configtest

      A successful apachectl configtest invocation should result in output like this:


      Syntax OK

      You can now restart Apache using the appropriate systemctl restart command for your Linux distribution.

      On Ubuntu and Debian-derived systems, run the following:

      • sudo systemctl restart apache2.service

      On CentOS, Fedora, and RedHat-derived systems use this command to restart Apache:

      • sudo systemctl restart httpd.service

      After you restart Apache, the AH00558 error message will no longer appear in your logs. You can confirm the messages are silenced by running any of the three systemctl, journalctl, or apachectl commands that are demonstrated in this tutorial.


      In this tutorial you learned about AH00558: Could not reliably determine the server's fully qualified domain name error messages. While these messages do not prevent Apache from running, they can be resolved by setting a global ServerName directive.

      You learned how to search for AH00558 error messages using the systemctl, journalctl, and apachectl commands. Finally, you learned how to edit your Apache configuration on various Linux distributions to silence the messages.

      If you would like to learn more about how Apache uses ServerName directives, the Apache documentation about Name-Based Virtual Hosts explains the directive in more detail.

      Source link