Knowledgebase : Domains

If you didn’t add the ‘www’ prefix at the time of setting up the domain, even adding it back in later does not seem to work.

Solution:
To work around this problem, firstly – turn on the ‘www’ prefix again within the Plesk control panel.

Go to Plesk CP > Domains > yourdomain.xxx > 'Domain Administration' drop-down menu > Rename domain. It will force IIS to configure www.yourdomain.com hostheader for your domain.


Also, make sure your www.yourdomain.com resolves to the same IP adress as yourdomain.com.

You have created a FTP Account through Plesk Control Panel, but when you try to connect your FTP site you get this error "error 530 User cannot log in, home directory inaccessible."

Server Configuration:

  • Windows Server 2008 or 2008 R2
  • Plesk Control Panel
  • IIS 7 or 7.5
  • Microsft SQL Server 2005, 2008, 2008R2

Solution:

  1. Connect to your server using RDP
  2. Connect to SQL Server using Microsft Management Studio Express
  3. Expend Datatbases
  4. Expand Plesk Database
  5. Expend Tables
  6. Right Click on dbo.domains and Click Edit  Top 200 Rows
  7. Check if your domain "Status" has any other status than 0, if the status is already set to 2, 4, 16, 64, 256 set it ot "0".
  8. Close the table and recreate the FTP Account in Plesk Control Panel.
  9. Now try to connect your FTP site. You should be able to login and browse site's Files and Folders.

Feel Free to leave your comments.

Applies to Paralle's Plesk 10.x.x & 11.x.x

If you have a production website and want to improve it, it is advised to clone it and let your designers and programmers work on the copy of the site without interrupting the operations of your production site. Cloning is done by creating a copy of your site files and databases attached to it.

1. Prepare development environment.
You are advised to decide where you will host your development copy before copying site files and databases. Depending on your security and production isolation policy, you may choose to create a development copy of your site under the same hosting account, under a different hosting account on the same server if you have FTP access to its files, or on another server. If you decide to go with development site under the same account, add a site (domain or subdomain), or designate one that already exists. If you want to use another server or another account, make sure FTP access to your development site is correctly configured. In all cases, you may follow regular site creation procedures to prepare your development instance.

2. (Optional) Install APS applications

Install the desired site applications in your development environment in the same subdirectory as you have on your production site.

This step is needed if you set up your development environment under your account in the Panel and your production site has APS applications installed via the Panel (at the Applications tab). The reason is that copying site files will not register a new instance of APS application on your site copy. The application copy will still work, but it won't be listed among Installed Applications on the Panel Aplications tab, so you will not be able to change its settings from the Panel. In such a case, you will have to change all database connection settings manually in the application scripts. So perform this step to avoid such manual operations and take advantage of the APS management on your development instance.

3. Copy site files.
To copy your site content, go to the production subscription and select the "Website Copying" operation. You are advised to decide where you will host your development copy before going to that page and preparing the destination for the site content (see Step 1).

4. Copy databases.
In the production subscription, go to Websites & Domains tab > Databases. Click the name of the database with which your site works and select the "Make a Copy" operation. If your site works with more than one database, repeat the procedure for each database. If your production site produces a substantial load on the database server, it is advised to install a separate database instance for development purposes. Create and register the new databases with your development workspace. Then copy your production databases to the development server.

5. Change database connection settings in the scripts.
Be sure to change the database connection settings in the scripts in your development version. Remember that after the files are copied, they are still pointing at the production database. Make sure that your developers will work with the cloned instance instead.

6. (Optional) Complete APS applications setup.
Go to the Applications tab for your development site, locate the application in the list of installed applications, open its Settings screen and re-save the parameters. With this operation, the APS scripts should stop pointing at the production database and reconnect the application to the database copy.

This step is needed if your production site has APS apps installed via the Panel and you performed Step 2 of the current instruction.

"There is a bug with the Windows Parallels Plesk Control Panel that can sometimes cause a domain to get added to the BIND service twice.  This would prevent the domain from being accessible and would show no DNS records even though the Blacknight Control Panel shows the domain as being added to Plesk successfully and though all the DNS settings in the Plesk Control Panel are correct."

 

Open a command prompt and go to the Plesk admin bin directory. Most likely: C:\Parallels\Plesk\admin\bin or C:\SWSoft\Plesk\admin\bin. E.g:
cd C:\Parallels\Plesk\admin\bin

 
Run the following command:
dbclient.exe --direct-sql "--sql=select id,name,status from dns_zone"


This will show you a list of all the domains in the BIND service on your server (i.e. domains added to the VPS). Any entry with a 2 beside it usually means an error. In this case there would be two entries for your_domain_name.com, one with a 2 beside it, as it was an incorrect duplicate entry.


What you need to do then is note down the ID number to the left of the entry for the duplicated domain name (the one with the 2 instead of 0 at the end) and then run the following commands:

dbclient.exe --direct-sql "--sql=delete from dns_recs where dns_zone_id=XX"
dbclient.exe --direct-sql "--sql=delete from dns_zone where id=XX"
where XX is the ID number. In this case it is 10.


Then finally run one last command to update BIND on the server:

DNSMng.exe update *

Overview
DomainKeys Identified Mail (DKIM) lets an organization take responsibility for a message while it is in transit. The organization is a handler of the message, either as its originator or as an intermediary. Their reputation is the basis for evaluating whether to trust the message for delivery. Technically DKIM provides a method for validating a domain name identity that is associated with a message through cryptographic authentication.


What is the purpose of DKIM?
DKIM allows an organization to take responsibility for transmitting a message, in a way that can be verified by a recipient. The organization can be the author's, the originating sending site, an intermediary, or one of their agents. Their reputation is the basis for evaluating whether to trust the message for delivery. 

 
What does DKIM Do?
The responsible organization adds a digital signature to the message, associating it with a domain name of that organization.  Typically, signing will be done by an service agent within the authority of the message originator's Administrative Management Domain (ADMD). Signing might be performed by any of the functional components, in that environment, including: Mail User Agent (MUA), or Mail Submission Agent (MSA), Internet Boundary MTA. DKIM permits signing to be performed by authorized third-parties.


Who validates the signature?
After a message has been signed, any agent in the message transit path can choose to validate the signature. Typically, validation will be done by an agent in the ADMD of the message recipient. Again, this may be done by any functional component within that environment. Notably this means that the signature can be used by the recipient ADMD's filtering software, rather than requiring the recipient end-user to make an assessment. 



What does the DKIM signature mean?
The owner of the domain name being used for a DKIM signature is declaring that they are accountable for the message. This means that their reputation is at stake.

Receivers who successfully validate a signature can use information about the signer as part of a program to limit spam, spoofing, phishing, or other undesirable behavior, although the DKIM specification itself does not prescribe any specific actions by the recipient.

 

Will using DKIM imporve deliverability?
Whether this improves deliverability or bypasses filters is entirely at the discretion of the validating receivers. When a message has been signed using DKIM, a receiver uses their knowledge about the signer to determine the most appropriate treatment of the message. It is expected that messages from a signer who has a good reputation will be subject to less scrutiny by the receiver's filters. 


 Implementation Details: 
Upon request, DNN4Less will generate and implement DKIM Signatures for Domains owned by the customer.
Signatures will have the following attributes:

  • Signing Algorithm: RSA-SHA256
  • Key Size: 1024
  • Selector: UE(YEAR)(MONTH)

Once the DKIM Signature has been generated, the customer will receive a text file containing the Public Key Record.

It is the customer's responsibilty to have their Domains DNS updated with (2) TXT entries: Policy Record & Public Key Record

 

Example DKIM TXT Entries:

 

  1. _domainkey.(YourDomain). IN TXT "o=~; r=postmaster@(YourDomain)"
  2. (Selector)._domainkey.(YourDomain). IN TXT "v=DKIM1; p=MIGfMA0GCSqGSIb4DQ(.....)z2nJSPOxvGGznkcY25w5lIYpxpVwZ/IwIDAQAB;"


DKIM Policy Record:

A domain name using DomainKeys should have a single policy record configured. 
This is a DNS TXT-record with the name "_domainkey" prefixed to the domain name - for example "_domainkey.yourdomain.com". 
The data of this TXT-record contains the policy which is basically either "o=-" or "o=~".

 

  • o=- 
    Means "all e-mails from this domain are signed"
  • o=~ 
    Means "some e-mails from this domain are signed". 
  • t=
    Means "Test" 
  • r=postmaster@(YourDomain.com)
    Responsible e-mail address 
  • n=
    Allows you specify a note.



DKIM Public Key Record (Domain Signature Record):

DKIM uses a simple "tag=value" syntax in several contexts, including in messages and domain signature records.

 

Values are a series of strings containing either plain text, base64 text (as defined in [RFC2045], Section 6.8), qp-section (ibid, Section 6.7), or dkim-quoted-printable (as defined in Section 2.6). The name of the tag will determine the encoding of each value. Unencoded semicolon (";") characters MUST NOT occur in the tag value, since that separates tag-specs.

 

  • v=
    Version of the DKIM key record (plain-text; RECOMMENDED, default is "DKIM1"). If specified, this tag MUST be set to "DKIM1" (without the quotes). This tag MUST be the first tag in the record. Records beginning with a "v=" tag with any other value MUST be discarded. Note that verifiers must do a string comparison on this value; for example, "DKIM1" is not the same as "DKIM1.0".Version (MUST be included). This tag defines the version of this specification that applies to the signature record. 
  • g=
    Granularity of the key (plain-text; OPTIONAL, default is "*"). This value MUST match the Local-part of the "i=" tag of the DKIM-Signature header field (or its default value of the empty string if "i=" is not specified), with a single, optional "*" character matching a sequence of zero or more arbitrary characters ("wildcarding"). An email with a signing address that does not match the value of this tag constitutes a failed verification. The intent of this tag is to constrain which signing address can legitimately use this selector, for example, when delegating a key to a third party that should only be used for special purposes. Wildcarding allows matching for addresses such as "user+*" or "*-offer". An empty "g=" value never matches any addresses.
  • h=
    Acceptable hash algorithms (plain-text; OPTIONAL, defaults to allowing all algorithms). A colon-separated list of hash algorithms that might be used. Signers and Verifiers MUST support the "sha256" hash algorithm. Verifiers MUST also support the "sha1" hash algorithm.
  • k=
    Key type (plain-text; OPTIONAL, default is "rsa"). Signers and verifiers MUST support the "rsa" key type. The "rsa" key type indicates that an ASN.1 DER-encoded [ITU.X660.1997] RSAPublicKey[RFC3447] (see Sections 3.1 and A.1.1) is being used in the "p=" tag. (Note: the "p=" tag further encodes the value using the base64 algorithm.)
  • n=
    Notes that might be of interest to a human (qp-section; OPTIONAL, default is empty). No interpretation is made by any program. This tag should be used sparingly in any key server mechanism that has space limitations (notably DNS). This is intended for use by administrators, not end users.
  • p=
    Public-key data (base64; REQUIRED). An empty value means that this public key has been revoked. The syntax and semantics of this tag value before being encoded in base64 are defined by the "k=" tag.
  • s=
    Service Type (plain-text; OPTIONAL; default is "*"). A colon-separated list of service types to which this record applies. Verifiers for a given service type MUST ignore this record if the appropriate type is not listed.
  • t=
    Flags, represented as a colon-separated list of names (plain-text; OPTIONAL, default is no flags set). The defined flags are as follows:

    • This domain is testing DKIM. Verifiers MUST NOT treat messages from signers in testing mode differently from unsigned email, even should the signature fail to verify. Verifiers MAY wish to track testing mode results to assist the signer.
    • s
      Any DKIM-Signature header fields using the "i=" tag MUST have the same domain value on the right-hand side of the "@" in the "i=" tag and the value of the "d=" tag. That is, the "i=" domain MUST NOT be a subdomain of "d=". Use of this flag is RECOMMENDED unless subdomaining is required.

When you create a domain in Plesk Panel you get the following error:

Failed domain creation: Unable to update domain data: Failed mail post-configuration: Can't create mail domain service: mailManager->addDomain() failed: mailmng failed: Empty error message from utility.

---------------------- Debug Info -------------------------------
0: htdocs\domains\create_domain.php:160

SOLUTION:

This error occurs because the entry for yourdomain.xxx is already present in the Mail Enable Administrator, to solve this issue do the following:

  1. Login to your server
  2. Go to MailEnable \ Management \ Messaging Manager \ PostOffices, check the mailbox at this location to make sure that domain name is not already exist, if the domain name is already exist, delete it and then recreate the Domain in Plesk Panel.

Note: Deleting the domain will also delete all the mailboxes.

Domain name forwarding lets you automatically direct your domain name's visitors to a different website.

Masking prevents visitors from seeing your domain name forwarding by keeping your domain name in the Web browser's address bar.

To forward or mask your domain name, you must use default nameservers.

Setting DefaultNameservers for Your Domain Names

  1. Log in to your Account Manager.
  2. In the My Products section, select Domains/Domain Manager.
  3. Select the domain name(s) you want to modify.
  4. From  (Nameservers), select Set Nameservers.
  5. I have a hosting account with these domains — Use this option when your domain name is hosted with us.

Forwarding or Masking Your Domain Name

  1. Log in to your Account Manager.
  2. In the My Products section, click Domain Manager.
  3. Select the domain name you want to forward.

 

NOTE: You cannot forward or mask .tk domain names.


  1. Click Forward, and then select Forward Domain.
  2. Select http:// or https:// depending on your server settings. 
  3. In the Forward to field, enter the URL you want to forward your domain name to.
  4. To automatically update your nameservers to accommodate your forwarding changes, select Update my DNS setting to support this change.

 

NOTE: Activating this setting updates your domain name's nameservers and IP address. If you are currently hosting a website for a domain name and you forward it, visitors can no longer access your website. Instead, forwarding redirects your website's visitors to the URL you enter.


  1. To view additional options, including masking, click Advanced Options.
  2. Select one of the following:
    • Forward Only — Specifies the length of time for this forwarding setting. Select one of the following Redirect types:
      • I am permanently forwarding my domain — Redirects to the site you specified in the Forward To field using a "301 Moved Permanently" HTTP response. The HTTP 301 response code tells user-agents (including search engines) that the location has permanently moved.
      • I am only temporarily forwarding my domain — Redirects to the site you specified in the Forward To field using a "302 Found" HTTP response. The HTTP 302 response code tells user-agents (including search engines) that the location has temporarily moved.
    • Forward with Masking — Prevents the forwarded domain name URL from displaying in the browser's address bar, and lets you enter Meta Tags for search engine crawlers in the following fields:
      • Title — Displays at the top of the browser window and in search results.
      • Description — A short description of your website to display in search engine results.
      • Keyword — A list of comma-separated keywords that describes the content and purpose of your website.
  3. Click OK.


It is easy to setup and host a new website on your dedicated server through Plesk. You may be limited to the number of domains you can host, depending on the Plesk licence you have chosen.

 

Step 1
Log in to the Plesk control panel on your server.

Step 2
Click on Domains in the menu on the left.

 
 

Step 3
Click on the Create Domain icon.

 
 

Step 4
Enter the domain name you're adding in the Domain name text box, and make sure the WWW box is selected.

Select one of the IP addresses assigned to your server from the Assign IP address drop down menu.

Select Default Domain from the Use domain template settings drop down menu.

 
 

Step 5
Ensure the Mail and DNS boxes are selected, then choose the Web Site Hosting option from the Hosting type group.

 
 
Step 6
Choose a username to use to connect to the FTP for this domain and enter it in the Login text box. You also need to enter a password in the Password text box, and retype it in the Confirm password text box.
 
 
Click the Finish button when you are done. You will receive an on-screen message to let you know the domain has been added successfully.

1. Point your web browser to http://www.godaddy.com/.

Logging into your account
2. Log into your account by clicking on the "My Account" link located just below the menubar of the webpage. If you don't have an account yet, you will have to create one.
3. Enter your login name or customer number in the entry box labelled "Login Name or Customer Number".
4. Enter your password in the "Password" entry box located below the "Login Name" entry box.
5. Click on the "LOGIN" button located below the "Password" entry box.

Choosing a domain
6. Good! Now that you have logged into your account, select the "Manage Domains" menu item from the "Domain Names" drop down menu located on the left side of the webpage.
7. Below the "Domains Names" menu, select the domain for which you will be creating nameservers. If you do not have any domains, you will have to register one. For example, awebsite.com.

Creating the first nameserver
8. In the bottom right hand corner of the webpage (you may have to scroll down), expand the "Domain Host Summary" box by clicking on the "+" icon.
9. Click on the "Click here to see details or to modify" link below to begin creating the your nameservers.
10. On the right side of the webpage, enter the host name of your first name server in the entry box labelled "Host". The most common names are "ns1" or "dns1". For example, ns1.awebsite.com or dns1.awebsite.com.
11. Just below, add the IP of the nameserver in the "IP Address" entry boxes. For example, 192.168.0.1.
12. Now create the nameserver by clicking on "Add New Host".

Creating the second nameserver
13. You will need to create at least 2 nameservers. To create a second nameserver, repeat steps 10 to 12. Common practice dictates that the second nameserver will be named "ns2" or "dns2". For example, ns2.awebsite.com or dns2.awebsite.com.
14. By convention, the last part of the ip address of the second nameserver will be incremented by 1. For example, 192.168.1.1.
15. At this point you could add additional nameservers but it is not required. To save your nameservers, click on "Save Changes".

Final thoughts
16. Excellent! You have successfully created private nameservers at GoDaddy.com! Remember that your changes may take up to 72 hours to take effect (propagate).

If your domain name is registered in your control panel and is using DNN4Less Nameservers, you can access the advanced DNS section of your control panel. This will allow you to point different services on your domain name elsewhere.

 

Using your control panel, you can change the following records for your domain:

  • A Records: An A Record allows you to point the website of a domain name towards a specific IP address, allowing you to host a domains website in a different location than its other services.
  • CNAME record: Canonical Name records (CNAME for short), allow you to set up alias of your domain name to point towards another A record. This could be on your domain name, or on a separate domain name.

 

You cannot point a CNAME record towards an IP address.

 

  • X Records: Mail eXchange (MX) records allow you to point your email towards different mail servers. Adding multiple MX records allows you to send email to an alternate mail server if your primary server fails.
  • TXT Records: Text (TXT) records can be added to a domain name to add additional information for anyone looking up your domain. In recent times they have also been used to store data to be used by other protocols, such as SPF records.

  • AAAA Records: AAAA records work in the same way as A records, however, rather than pointing a website towards an IPv4 IP address (213.171.111.2 for example), they will point a website towards an IPv6 address (such as : c32:2214:ff2a)

  • Glue Records: These records are used if you are creating your own nameservers. By creating glue records, you will be registering these new nameservers with the global registry’s.

 

A Records

  • Host name: This is the sub domain name you would like to use for your A record. sales.domainname.com for example.

  • IP Address: Enter the IP address you would to point the new host name towards. 213.171.114.55 for example.

 

If you are pointing the A record towards your DNN4Less webserver, the IP address of your website can be found within your control panel. Don’t forget to update the root and the www record. Additional A records can be set up for other services.

 

CNAME Records

  • Host Name: This is the name of the alias you would like to set up. sales.domainname.com for example.
  • Points To: This is the A record that you would like to point your CNAME record to. signup.domainname.com for example.

 

MX Records

  • Points To: Enter the name of the mail server you would like to send email to. mail.ralphsdomain.com for example
If you have mailboxes set up with DNN4Less, our mailserver is mail.yourdomain.xxx
   
  • Priority: This sets the order in which servers will attempt to send email to your domain name. The lower the number the higher the priority. This will not send copies of your emails to multiple mail servers, and making the MX record a higher priority will not deliver email to the domain faster.

  • The addition of multiple MX records is designed purely to enable some fault tolerance within your email. If your main mailserver should fail for any reason, your emails will be directed to the next mail server on the list and so on.

 

TXT Records

  • Hostname: This is the name you would like to give to your Host record. This could be anything you like. If you are adding an SPF record, this should be the name of your domain name (without the www.)

  • Value: This is the content of your TXT record. This could be a comment, or an SPF record.

 

If you are using only DNN4Less Advanced or Exchange mailboxes to send email you can use “v=spf1 a ip4:213.171.216.0/24 mx ~all” as your SPF record, where;
  • V = Version of SPF
  • A = The A record of the domain is authorized to send mail
  • MX = the MX record (mail server) is authorized to send mail
  • Ipv4:213.171.216.0/24 approves our SMTP servers
  • ~all = Any email servers sending email from your domain name that are not listed ‘softfail’ – this means they will still be allowed , however we’re advising that it’s not an authorized server.  Changing this to –all will stop servers not listed from sending mail, provided the end mailbox checks SPF records associated with your domain name.
   

AAAA Records

  • Hostname: This is the name you would like to use for your A record. sales.domainname.com for example.
  • IP Address: Enter the IPv6 address you would like to point the new host name towards. 5fd4:0044:a3b1:526a for example.

Log in to the Network Solutions Account Manager at https://www.networksolutions.com/manage-it/index.jsp

  1. After logged into your NetworkSolutions account, click on View Domain Name List link on left.
  2. Click on the domain name you want to change.
  3. The Domain Details section displays different options. Select the radio button next to Custom DNS Setting and click on the Apply Change button. (Note: If radio button DNS Settings was already selected, then click on Edit DNS.)
  4. Next you will see Edit DNS page. On this page click on the Continue button (under the section Move DNS to a New Name Server). In the next page, after reading the confirmation warning, click on the Continue button.
  5. Enter the primary name server (NS1.DNN4Less.com) & secondary nameserver (NS2.DNN4Less.com) in the text boxes.
  6. When finished click on the Continue button, and then click on the Save DNS button
  7. You will see a confirmation page.  Please note that this can take up to 96 hours to be propagated all over the internet.

Please do the following to change your name servers at Tucows:

  1. Log into your Domain Management Interface, and click the Name Servers link.
  2. You will see a screen displaying the existing name servers.
  3. Enter the nameservers for the domain name into the Nameserver entry boxes.
  4. After the changes are made, click Save Configuration.

Please realize that it can take 24-72 hours for the domain name server information to be updated.

DNN4Less Name Servers:
NS1.DNN4Less.com
NS2.DNN4Less.com

This article will go through the steps on how to change name servers on your domain registered through Godaddy.

  1. Login to your GoDaddy Account using the Username and Password given to you by GoDaddy when you opened your account with them.
  2. In the left hand menu sidebar of the Account Overview window displayed to you click on Domain Manager below My Products.
  3. A list of your domains will be displayed.Click on the Domain Name for which you wish to change the Name Servers.
  4. A page will then be displayed showing all the details for that domain.Click on the NameServers icon on the top then click Setnameservers.
  5. A new pop-up window will be displayed. Check the radio button “I have specific nameservers for my domains” and enter/replace nameservers to NS1.DNN4Less.com and NS2.DNN4Less.com
  6. click OK.

This article will go through the steps on how to change name servers on your domain registered through 1and1.

  1. Login to your 1and1 admin panel >> select the package >> in the administration page, click on the link Manage Domains
  2. Click on DNS.
  3. Select the domain name from drop down list >> Click the Next button.
  4. Click on the edit button next to Name Server Setting.
  5. Select name server to My name server, enter Primary and Secondary name server fields, Click Ok.
    1. Enter Primary Name Server as NS1.DNN4Less.com
    2. Enter Secondary Name Server as NS2.DNN4Less.com
    3. Click OK
  6. You will see another message asking you to wait while the changes take effect. Please note that this can take up to 72 hours to be propagated all over the internet.

Please login to your EasyDNS account page and click the "whois" in the sidebar or domain administration when you are managing your domain name.

Click "edit" underneath the current nameservers to get blanks to add nameservers. Enter the two/three DNN4Less name server names in the nameserver fields in the top most blanks on the form and click "next" to confirm the changes.

Please realize that it can take 24-72 hours for the domain name server information to be updated.

 

DNN4Less Name Servers:
NS1.DNN4Less.com
NS2.DNN4Less.com

This article will go through the steps on how to change name servers on your domain registered through yahoo.

  1. Login to your domain control panel. Click on Domain Control Panel link.
  2. Click on Manage Advanced DNS settings link.
  3. Before you changes name server on yahoo.com, you need to unlock the domain. So scroll down and click on Unlock the Domain button.
  4. Click the Unlock Domain button in next 2 windows.
  5. After Unlocking the domain, let’s go back to Domain Control Panel by clicking on Domain Control Panel ink on the top to change the name server.
  6. Click on Manage Advanced DNS settings link.
  7. Scroll down and click on Change NameServers button.
  8. Enter Primary and Secondary name server fields NS1.DNN4Less.com & NS2.DNN4Less.com
  9. Click Submit.
  10. Any domain name servers change can take up to 72 hours to be propagated all over the internet. Next you need to re-lock the domain. Let’s go back to Domain Control Panel by clicking the domain control panel link.
  11. Click on Lock Domain button in next 2 windows.

 

This article will take you through the steps to change name servers ( DNS ) settings of your domain name registered with Enom.com.

  1. First you will need to visit www.enom.com and click login in the upper right hand corner of the screen. Enter in your username and password in the boxes shown.
  2. Click on Registered Domains link.
  3. Now click on the domain name you want to manage.
  4. Here you can see the current DNS setting for this domain. Click on Configure to change these setting.
  5. Enter the NS1.DNN4Less.com in Name Server 1 field.
  6. Enter the NS2.DNN4Less.com in Name Server 2 field.
  7. Then click save changes and you are DONE.

 

You will need to log into your DNN4Less control panel by doing the following:

  1. Open up a web browser and navigate to the following URL: https://control.DNN4Less.com/cp
  2. Enter in your username and password that were sent to you when your hosting package was created and click “Sign In” (the username will be the primary contact email address of the hosting package administrator).
  3. Once you have logged into your control panel, Click “Subscriptions /Domains”
  4. Select and click a Subscription
  5. Click “Website & Domains”
  6. Click “Backup Manager”
  7. Click “Back Up”
  8. As you cannot specify the file name for the backup, please add a prefix for further searching. You can also write the brief comments for the backup.
  9. Set the volume size of backup and select the location of the backup. By default, the backup will be stored in the same server. If you want to perform a remote backup, please select “Personal FTP repository”.
  10. Enter the email address to receive the notification upon task completion
  11. Select the backup content then click “Back Up”

Note: When you will delete the website in plesk 10 or 11, then the all data associated with the user account will be deleted from the server. One thing more, the first website which is created for your account can not be deleted; however you can rename the account.

Follow below steps to delete a website from the Plesk 10 / 11.

Step 1: Login in to plesk with correct user name and the password.

Step 2: Go to the subscription menu.

Step 3: Now click on the “WebSites & Domain” Tab.

Step 4: Now tick the domain which you want to remove.

Step 5: Confirm the removal and now click OK.

Log files show a running list of every time the site is accessed with information like the operating system, device type, and
browser accessing it, files loaded, and how they got there (what search engine, etc.) They can be useful if you’re interested 
in drawing statistics on who your customers or visitors are, and for investigating certain types of problems with the site.
However, if not properly managed, excessive log files can cause resource usage overages. 

You will need to log into your DNN4Less control panel by doing the following:

  1. Open up a web browser and navigate to the following URL: https://control.DNN4Less.com/cp
  2. Enter in your username and password that were sent to you when your hosting package was created and click “Sign
    In” (the username will be the primary contact email address of the hosting package administrator).
  3. Once you have logged into your control panel, Under Statistics, click on Log Manager.
  4. Once you’re in the Log Manager, click on Log Rotation.
  5.  In the Log Rotation, you can maintain logs at a certain size, or rotate them out on a time-basis (for example,
    discard anything older than 1 month)

This should allow you to maintain your log files at a potentially useful level, rather than 
keeping them infinitely and using up your available hosting space.

On Windows Server 2008 IIS 7.5

You can add rewrite rule in web.config file to redirect domain.com to www.domain.com

Option 1:

<system.webServer>
<rewrite>
   
<rules>
     
<rule name="Canonical host name">
       
<match url="^(.*)" />
         
<conditions>
           
<add input="{HTTP_HOST}" pattern="^www\.domain\.com$" negate="true" />
         
</conditions>
       
<action type="Redirect" url="http://www.domain.com/{R:1}" />
     
</rule>
   
</rules>
</rewrite>
</system.webServer>

Option 2:

<system.webServer> <rewrite> <rules> <clear /> <rule name="WWW Rewrite" enabled="true"> <match url="(.*)" /> <conditions> <add input="{HTTP_HOST}" negate="true" pattern="^www\.([.a-zA-Z0-9]+)$" /> </conditions> <action type="Redirect" url="http://www.{HTTP_HOST}/{R:0}" appendQueryString="true" redirectType="Permanent" /> </rule> </rules> </rewrite> <system.webServer>

Applies to Plesk 10.x.x & Plesk 11.x.x

To rename domain name in Plesk, Please follow the following settings:

  1. Login to Plesk control panel.
  2. Click on "Websites and Domains"
  3. Click on the "Domain Name" under whom you want to rename domain name.
  4. Type New Domain name
  5. Click on "Ok".

Renaming the domain name will rename DNS Settings, email addresses and all other settings related to the domain name.

If you can browse your webiste without "WWW" (yourdomain.xxx) and cannot browse with "WWW" (www.yourdomain.xxx), please ask your domain registrar to resset your Domain's Zone File.

 

This should solve the issue.

If you can browse your webiste without "WWW" (yourdomain.xxx) and cannot browse with "WWW" (www.yourdomain.xxx), please ask your domain registrar to resset your Domain's Zone File.

This should solve the issue.

When a domain is suspended via Plesk and when you try to unsuspend it, you may sometimes get an error stating.

  • Warning: The domain is still suspended for the following reason: This user account and user’s domain were suspended.
  • Warning: The domain is still suspended for the following reason: Domain is temporarily disabled for backup/restoring.

1. Try disabling the option “Suspend domain while backup is in progress” from Plesk. Domain >> Backup Manager >> Scheduled Backup

Now try to unsuspend the domain. If the error still exists.

2. Also check the resource limits, Validity period of the domain, it might have exceeded.

Plesk >> Domain >> (Limits)

If it still gives the error, even after trying the above, then you can unsuspend the domain via the command line.

cd %plesk_bin%
domain.exe –on domain.com

————————–
C:\Program Files\Parallels\Plesk\admin\bin>domain.exe --on example.com
SUCCESS: Changing status of domain ‘example.com’ completed.

domain.exe
--i domain.com >> Retreives information about the domain.
--on domain.com >> Turn On the domain
--off domain.com >> Turn Off the domain

Overview

This page takes you step by step through the procedure for transferring a domain away from Go Daddy and into an account at DNN4Less.

The transfer process involves the tasks that are described below. Following the transfer tasks, we provide information about tracking the progress of the transfer, and ICANN rules regarding rejections.

 

Transfer Task 1: Verify that the domain name is eligible for transfer

To make sure your domain name can be transferred, check the following:

  • The domain name has been registered for at least 60 days, and has been at Go Daddy for at least 60 days.
  • The Registrant contact information has not changed for at least 60 days.
  • The domain name is not in "client update prohibited" status.

Transfer Task 2: Update Administrative contact information

Before you can transfer a domain, the Administrative contact information (especially the email address) must be up-to-date at Go Daddy, because the Administrative contact receives the transfer request and okays the transfer.

Note: Go Daddy regards any changes to the Registrant contact information to be an "internal transfer" and will reject any transfer requests for 60 days after changes to the Registrant contact information. We recommend that you leave Registrant contact information as-is at Go Daddy. As long as either the Registrant or Admin email address is correct and you're using the Auto Verification method, you can make any needed changes once the domain name has successfully transferred to DNN4Less.

To update the Administrative contact at Go Daddy:

  1. Log on to your account at GoDaddy.com.
  2. On the "Domains" menu, click "My domain names".
  3. Click the domain name you want to transfer.
  4. If the Administrative contact information is incorrect, click the "edit" link next to the Administrative contact at the bottom of the page.
  5. Update the Administrative contact information and click "OK".

Transfer Task 3: Obtain the authorization code or retag the domain name

Some TLDs require that you provide an authorization code for your domain name, to provide an extra level of assurance that the transfer request comes from an authorized source.

To transfer a .com, .net, .org, .info, or .biz domain name, obtain the authorization code from Go Daddy:

  1. On the "My domain names" page, click the domain you want to transfer.
  2. In the "Domain Information" section, find the "Authorization Code" row and click "Send by email".
  3. Click "OK".

To retag a .uk domain name:

  • Contact Go Daddy and ask them to retag the domain name to IPS tag DNN4Less.
  • Alternatively, you can retag/detag directly through Nominet, for a fee.
  • When you transfer a .uk domain name, use the Auto verification transfer method.
  • You can submit the transfer requests to DNN4Less and Go Daddy in any order.
  • If you submit the transfer request to DNN4Less first, you must submit the request to Go Daddy within a week.
  • If you submit the transfer request to Go Daddy first, you must submit the request to DNN4Less by the next 8th day of the calendar month.

Transfers of TLDs other than those named above do not require any codes or tags.

Transfer Task 4: Unlock the domain name

Before you can transfer a domain name away from Go Daddy, it must be unlocked. Locking is a feature most registrars offer to prevent unauthorized transfers (hijacking) of domain names.

To unlock:

  1. On the "My domain names" page, click the domain name you want to transfer.
  2. In the "Domain Information" section, find the "Locked" row and click "Manage".
  3. Select the "Unlock domains" check box and click "OK".

 

Transfer Task 5: Transfer the domain name to DNN4Less

Once you have prepared the domain name at Go Daddy, you're ready to transfer to DNN4Less. Reply to the message you received from DNN4Less Support with the Domain Transfer Authorization Code.

When the domain name contacts receive email from DNN4Less asking them to approve the transfer, do so by following the instructions in the email.

 

Note: To decide whether to use the Auto Verification or Fax transfer method, weigh the following considerations:

  • Auto verification involves approving one domain per approval email; Fax involves assembling and faxing identity verification and a list of domains to transfer.
  • Auto verification is generally easier for transferring small numbers of domains (a dozen or so; more if you don’t have convenient access to a fax machine); Fax is easier for transferring larger numbers of domains.
  • Auto verification allows you to transfer domains with different Registrant and Admin contacts; Fax method requires the same Registrant and Admin contact information for all domains listed in the request.
  • If you plan to transfer a large number of domains, but in separate requests, ask DNN4Less’s transfer specialists to keep your proof of identity on file so you don’t have to resubmit it with every transfer request.
  • Auto verification is the easiest method if you are transferring from a registrar that does not list Registrant or Administrative email addresses.
  • For .uk and .ca names, always use the Auto verification method.


Overview

This page takes you step by step through the procedure for transferring a domain away from Network Solutions and into an account at DNN4Less.

The transfer process involves the tasks that are described below. Following the transfer tasks, we provide information about tracking the progress of the transfer, and ICANN rules regarding rejections.

Transfer Task 1: Verify that the domain name is eligible for transfer

To make sure your domain name can be transferred, check the following:

  • The domain name has been registered for at least 60 days, and has been at Network Solutions for at least 60 days.
  • The domain name is not in "client update prohibited" status.

Transfer Task 2: Update contact information for the domain name

Before you can transfer a domain, the Registrant and Administrative contact information (especially the email addresses) must be up-to-date at Network Solutions, because these contacts receive the transfer request and okay the transfer.

To update the Registrant and Administrative contacts at Network Solutions:

  1. Log on to your account at NetworkSolutions.com.
  2. Click "Edit Account Contacts".
  3. Click the account name for which you want to confirm contact information.
  4. In the "Edit WHOIS Contacts" section, click "View/Edit WHOIS Contacts".
  5. Select the check box next to the domain name you want to confirm, and click "Continue".
  6. If the Administrative contact information needs to be updated, select the "Administrative Contact" option and click "Continue".
  7. Follow the instructions in the interface. When you have successfully completed the update, the user interface displays a confirmation.
  8. Repeat for the Registrant.

Transfer Task 3: Obtain the authorization code or retag the domain name

Some TLDs require that you provide an authorization code for your domain name, to provide an extra level of assurance that the transfer request comes from an authorized source.

To transfer a .com, .net, .org, .info, or .biz domain name, obtain the authorization code from Network Solutions:

  1. Call Network Solutions 24-hour support line at 888-642-9675.
  2. Request the domain name authorization code.

To retag a .uk domain name:

  • Contact Network Solutions at 888-642-9675 and ask them to retag the domain name to ISP tag DNN4Less.
  • Alternatively, you can retag/detag directly through Nominet, for a fee.
  • When you transfer a .uk domain name, use the Auto verification transfer method.
  • You can submit the transfer requests to DNN4Less and Network Solutions in any order.
  • If you submit the transfer request to DNN4Less first, you must submit the request to Network Solutions within a week.
  • If you submit the transfer request to Network Solutions first, you must submit the request to DNN4Less by the next 8th day of the calendar month.

Transfers of TLDs other than those named above do not require any codes or tags.

Transfer Task 4: Unlock the domain name

Before you can transfer a domain name away from Network Solutions, it must be unlocked. Locking is a feature most registrars offer to prevent unauthorized transfers (hijacking) of domain names.

To unlock:

  1. In your Network Solutions account, click the domain name you want to unlock.
  2. In the "Domain Details" section, click "Edit".
  3. Select "Turn Domain Protect Off" and then click "Save".

Transfer Task 5: Transfer the domain name to DNN4Less

Once you have prepared the domain name at Network Solutions, you're ready to transfer to DNN4Less. Reply to the message you received from DNN4Less Support with the Domain Transfer Authorization Code.

When the domain name contacts receive email from DNN4Less asking them to approve the transfer, do so by following the instructions in the email.

 

Note: To decide whether to use the Auto Verification or Fax transfer method, weigh the following considerations:

  • Auto verification involves approving one domain per approval email; Fax involves assembling and faxing identity verification and a list of domains to transfer.
  • Auto verification is generally easier for transferring small numbers of domains (a dozen or so; more if you don’t have convenient access to a fax machine); Fax is easier for transferring larger numbers of domains.
  • Auto verification allows you to transfer domains with different Registrant and Admin contacts; Fax method requires the same Registrant and Admin contact information for all domains listed in the request.
  • If you plan to transfer a large number of domains, but in separate requests, ask DNN4Less’s transfer specialists to keep your proof of identity on file so you don’t have to resubmit it with every transfer request.
  • Auto verification is the easiest method if you are transferring from a registrar that does not list Registrant or Administrative email addresses.
  • For .uk and .ca names, always use the Auto verification method.

All accounts include a temporary url that you can use to test your website. You'll want to use the temporary url in the following cases:

  1. Your domain was just registered, and is not fully activated
  2. You are migrating your website from another host to DNN4Less, and have not yet updated your DNS.

What is my Temporary URL?

Your temporary URL is your-domain.xxx.dnn4less.net (replace your-domain.xxx with your actual domain name)

What does my Temporary URL do?

Your Temporary URL allows you to test your website if your domain name is not yet pointing to our servers. This is typical if you are transferring your website to DNN4Less Hosting. Your domain name will still point to your previous hosting provider while you're uploading and testing your website on our servers.

Important! The Temporary URL is not really temporary. It goes to the same location as your Web files. The difference between the temp and live site is how you access the files. You can access the server when your domain is not active or not pointing to your server with us.

How do I setup a Temporary URL?

  1. Log in to your Control Panel 
  2. Click on Domains Tab
  3. Click on the Domain Name or "Manage hosting"
  4. Click on "Websites & Domains" Tab
  5. Scroll down to the end of the page and Click "Add New Domain Alias"
  6. In "
  7. Check all the options
    1. Synchronize DNS zone with the primary domain
    2. Mail service
    3. Web service
  8. Click OK

 

How do I test my website with the Temporary URL?

To test your website using the Temporary URL, simply visit that URL your-domain.xxx.dnn4less.net You should see your website at this point. You'll want to click on various links in your site and ensure each page is loading.

Dedicated (also called ‘fixed’ or ‘static’) IP as opposed to a shared IP address when getting a broadband connection? There are plenty of advantages and here we outline a few.

Generally, having a shared IP address will not cause you any harm. However, there are a few cases when a static IP is required or simply an advantage.

  • Less downtime – Each time your IP address refreshes you run the risk of downtime from the server. While this is usually only for a very short time, it can wreak havoc on your gaming. Having a static address eliminates this risk.
  • Having your own Private SSL Certificate – Secure e-commerce websites need SSL certificates for accepting credit cards online. Web hosts usually offer a shared SSL certificate where clients can share the Web host’s SSL.
  • Anonymous FTP It means that anyone using the FTP software can access files in a special directory of your site. It’s called Anonymous FTP because the user name used to access is “anonymous.” Many Web hosting providers require a static IP for the anonymous FTP function to work properly.
  • You want to access your website by FTP or Web browser even when the domain name is inaccessible, such as domain name propagation periods.
  • Remote access – With a static IP address you can access your PC no matter where you are in the world. Using programs such as Remote Administrator and PC Anywhere you can log into your work or home PC no matter where you are. Although you can set the connection up regardless of what type of IP address you have, you need a fixed address to maintain it otherwise the program will no longer be able to find your computer when your PC refreshes its dynamic address.
  • Running an FTP server – File Transfer Protocol (FTP) is an efficient and reliable way to transfer data from one computer to another. Again, specific software must be installed in order for you to set up an FTP site, but this is easy to do and free software is available. You might want to use an FTP site to share files, such as pictures, with your friends, or you might use it to enhance your organisation. Either way, once you’ve set up the site, clients, partners or friends just need to log in to access, edit or upload files.

A glue record is the IP address of a name server held at the domain name registry.

Glue records are required when you wish to set the name servers of a domain name to a hostname under the domain name itself.

For example if you wished to set the name servers of example.com to ns1.example.com and ns2.example.com you would need to also provide the glue records (i.e. the IP addresses) for ns1.example.com and ns2.example.com.

If you did not provide the glue records for these name servers then your domain name would not work as anyone requiring DNS information for it would get stuck in a loop.

With the glue record in place the registry will hold the IP address and the loop will not occur.

When you set up your webhosting, we will automatically create some directories within your webspace for you.

  • httpdocs

  • logfiles

After connecting to your web space with an FTP program you will be automatically logged into the httpdocs folder. You can naviage up a level to see the other directories we have created.

 

  • httpdocs: All your web content should be stored in this directory, or a sub-directory of this. Your home page should be within this directory and should be named index or default. Within the httpdocs folder, you will see that another subdirectory has been created.

  • cgi-bin: The cgi-bin directory is for files that require execute permissions. For example Perl or Python scripts, or compiled CGI. HTML and PHP files will not work if placed in this directory.

  • logfiles: The logfiles directory contains the raw logfiles for your domain. This is where any monitoring software such as Matrixstats will get the information needed to show you website statistics. You should not upload any files to this directory.

 

 

FTP software will allow you to upload files in different formats. Perl and Python scripts should be uploaded in ASCII, while compiled CGI should be uploaded in binary.

 

What to Call your Home Page

When someone visits a folder on your website, the webserver will look for the default document within your httpdocs folder. Our webservers are configured to look for a file called index or default, to display as your home page.

 

While it is good practice to have just one default file within your htdocs folder, if you have more than one, the server will display whichever is highest on its precedence list. The order that it chooses a default page is slightly different, depending on the type of server you are using.

 

Below is a list of default files, with the highest priority at the top.

  • default.html

  • default.asp

  • index.htm

  • index.html

  • index.php

  • index.pl

  • default.aspx

This article explains the reasons why you might get the following message from the web server:

"You are not Authorized to View this Page"

or

"HTTP Error 403 - Forbidden; Directory Listing Denied"

The principle reasons for this message are:

There is no default page for the server to display.

  • Use FTP to access your website and check that a default web page exists.A list of default web pages is available in our article Where do I upload my website files?

Ideally you should only have one default document. If you have more than one, the web server will choose the first one in the list and ignore the others.

The page you have requested does not exist

  • Use FTP to access your website and check that the web page exists.A list of default web pages is available in our article Where do I upload my website files?