msgbartop
Gossimer’s Premier Web Hosting and Domain Registration Knowledgebase.
msgbarbottom

01 Sep 10 Logs and Log Rotation

In order to provide you with means to track all activity for your Web hosting package, Gossimer makes available comprehensive Raw Log files in the Logs folder for your Website.

The raw log files consist of:

  • Web Log Files: These files are generated by the Web server to record all requests made to the Website. They are primarily used by your Website Statistics software to generate reports on essential marketing metrics for your website such as the number of visitors, pages viewed, visit duration, referring websites, search engines, key phrases and keywords used to find your site, visitor’s computer configurations and so on.
     
  • FTP Log Files: These files are generated by the FTP server to record all logins, uploads and downloads made to and from your hosting package.
     
  • Mail Log Files: These files are generated by the Mail server to record all Email sent using code on your website.

The Log Files Manager in the Control Panel provides extremely flexible options to manage these raw log files. Not only can you configure logs  separately for Web, FTP and Mail Log files, but also choose to disable a particular type of logging in order to save disk space.

Log Rotation

If you choose to enable logging, the system allows you to specify log rotation options. Log rotation aims to delete older log entries automatically so that the log files do not continue growing in size indefinitely, thus saving you disk space. For your log files, you can

  • specify the number of backlogs to maintain for each type of log file,
  • set a maximum log file size, and
  • set log rotation frequency (daily/weekly/monthly).

 

Tags: , , , , , , , , , , , , , , , , , , , , , , , ,

31 Aug 10 Collaboration Data Objects for Windows NT Server (CDONTS)

 

Collaboration Data Objects for Windows NT Server (CDONTS) component is a very old component shipped mainly with Windows 2000 server. Like Collaboration Data Objects (CDO), this too can be used to accept feedback from visitors via an online form which on submission would send you an Email about the information filled in by the visitor.

IMPORTANT 

Now with the arrival of Windows 2003 this component has been deprecated. Gossimer suggests that you upgrade your scripts to CDO.

 

 

You may use the sample script provided by Gossimer, and customise it to your needs. You would need to change the From Email address in the field objMail.From to any Email address on the same domain name where you are incorporating this script. For example, if your Domain Name is abc.com, then you may define the From Email address as some-name@abc.com. This Email address need not be existing on the Mail Server of abc.com, however, the domain name in the objMail.From has to be yours. You may use an Email address like Do_Not_reply@abc.com.

The Email address in the objMail.To field needs to be changed to your Email address, where you wish to receive Emails submitted through the form.

Sample Script 

 

<%

Set objMail = Server.CreateObject(“CDONTS.NewMail”)
objMail.From = “some-name@abc.com”
objMail.Subject = “Testing Mail”
objMail.To = “user@abc.com”
objMail.Body = “Testing ….”

objMail.Send
Response.Write “Mail Sent …..”
Set objMail = nothing
%>

 

Tags: , , , , , , , , , , , , , , , , , , , , , , ,

26 Aug 10 How do I start using my Email forwarding service?

Once you have started using the Email Forwarding service, you need to take the following steps to start using it: 

A. Change the Name servers of your Domain name to our Name servers.

For your Mail forwarding service to work, it is essential that all queries for mail addresses on your Domain name should reach our Mail Forwarding server, which would further redirect mails destined for these addresses to the destination you have specified.

Thus, it is vital that after you have bought the service for a particular Domain name, you need to change the Name servers for this Domain name to our Name servers.

Follow the process outlined below to know what Name servers you need to use:

     

  1. Login to your Control Panel and search for the Domain name for which you have purchased the Mail Forwarding service.
     
  2. In the Order List View that appears, click on that particular Domain Name.
     
  3. In the details view, click on View Name Server Details.
     
  4. Here, you would find the list of Name servers you need to set for your Domain name.

If the Domain name for which you have purchased this service is registered with Gossimer, refer to the article on Modifying Name servers to learn how to go about changing your Name servers.

OR

Create an MX record for your Domain name pointing to our Mail Forwarding Server

B. Create Email forwards, and other forwarding settings. Click here to find out how

Tags: , , , , , , , , , , , , , , , , , , , , ,

26 Aug 10 How do I add Domain Aliases?

In order to add Domain Aliases for your primary domain name, follow the process mentioned below: 

1. Login to your Control Panel, search for the domain name for which you have purchased the Email Hosting package and go to the Order Details view. Click here to read how >>

2. Click the Modify Domain Aliases button on the lower toolbar.

3. Here, enter up to 5 additional domain names as aliases for your the primary domain name, and click Modify Domain Aliases.
 

IMPORTANT   

Creation of DNS Records

For each Domain Alias that you submit, you would need to point this domain name to your primary domain name (for which you have bought Email Hosting). This can be accomplished by either one of these ways:

Option 1

On the existing Name Servers of the Domain Alias, replicate the Resource Records displayed in the View Name Server Details button within the Order Details view page, of the Email Hosting Order -

       

  1. a Mail Exchanger Record (MX Record) pointing to the mail server for your primary domain name. For example,domain-alias-name.com IN MX 198765.mx.email-hosting-name.com.
     
  2. an Address Record (A Record) each for imap, pop, smtp, webmail hosts to the IP Address of the Email Hosting domain name.For example,imap.domain-alias-name.com IN A 209.62.85.240
    pop.domain-alias-name.com IN A 209.62.85.240
    smtp.domain-alias-name.com IN A 209.62.85.240
    webmail.domain-alias-name.com IN A 67.15.47.17
       

    IMPORTANT   

    The above mentioned A records for imap, pop, smtp and webmail hosts are optional. You may create these, if you wish to use imap.domain-alias-name.com/pop.domain-alias-name.com and smtp.domain-alias-name.com for managing email through an email client and webmail.domain-alias-name.com for managing emails through a web-based interface.

    Else, imap.email-hosting-name.com/pop.email-hosting-name.com, smtp.email-hosting-name.com and webmail.email-hosting-name.com may be used.

  3.  

     

Option 2

If your current DNS Service Provider does not allow you to create this record, then you can follow the process listed below -

       

  1. Purchase Managed DNS Service from Gossimer for the alias domain name.
     
  2. Search for the domain name for which you have purchased the Email Hosting package and go to the Order Details view. Click here to read how >>
     
  3. Click the View Name Server Details button.
     
  4. Replicate for your alias domain name, the following Resource Records Click here to read how to add these Resource Records >>a. set the Mail Exchanger Record (MX Record) pointing to the mail server for your primary domain name.For example,domain-alias-name.com IN MX 198765.mx.email-hosting-name.com.b. set an Address Record (A Record) each for imap, pop, smtp, webmail hosts to the IP Address of the Email Hosting domain name.

    For example,

    imap.domain-alias-name.com IN A 209.62.85.240
    pop.domain-alias-name.com IN A 209.62.85.240
    smtp.domain-alias-name.com IN A 209.62.85.240
    webmail.domain-alias-name.com IN A 67.15.47.17
     

    IMPORTANT   

    The above mentioned A records for imap, pop, smtp and webmail hosts are optional. You may create these, if you wish to use imap.domain-alias-name.com/pop.domain-alias-name.com and smtp.domain-alias-name.com for managing email through an email client and webmail.domain-alias-name.com for managing emails through a web-based interface.

    Else, imap.email-hosting-name.com/pop.email-hosting-name.com, smtp.email-hosting-name.com and webmail.email-hosting-name.com may be used.

     

  5. Modify the Name Servers of the alias domain name, as per the details provided here. Click here to find out how you can modify the Name Servers, if you have registered your Domain Name with Gossimer >>
  6.  

     

Configuration in email client

While configuring the email address in the email client, need to set the following –     

    Email Address – user@domain-alias-name.com
    Account/User Name – user@email-hosting-name.com
    Password – password for user@email-hosting-name.com

Once done, you can use email addresses on the alias domain names to send and receive emails.

Tags: , , , , , , , , , , , , , , , , , , , , , , ,

21 Aug 10 File extensions that are not allowed as attachments

From a security perspective, Gossimer, LLC Mail Server would reject inbound mails containing attachments with any of the following file extensions -

 

.ade .adp .adt .app .asd .asp .asx .bas
.bat .bin .btm .cab .cbl .cbt .cgi .chm
.cil .cla .clas .class .cmd .cpe .cpl .crt
.csc .csh .css .cvp .dll .dot .drv .exe
.fon .fxp .hlp .hta .htr .inf .ini .inp
.ins .isp .jar .js .jse .keyreg .ksh .lib
.lnk .mda .mdb .mde .mdt .mdw .mht .mhtm
.mhtml .msc .msi .msp .mst .mp3 .nte .nws
.obj .ocx .ops .ov .pcd .pgm .pif .pl
.pm .prg .scr .sct .shb .shs .slb .smm
.swf .swt .sys .vbe .vbs .vbx .vir .vmx
.vxd .wmd .wms .wmz .wsc .wsf .wsh .xms
 

Tags: , , , , , , , , , , , , , , , , , , ,

17 Aug 10 Active Server Component (ASPMail)

Every Gossimer Windows Web Hosting package comes with the ASPMail component, which allows you to send SMTP mail directly from a Web page.

You can easily customise our sample script and put it up on your website. You would, however, need to change the Email address in the field Mailer.FromAddress to any Email address on the Domain on which you are incorporating the script. For example, if your Domain Name is abc.com, then you need to define the Email address as user@abc.com. This Email address need not be existing on the Mail Server of abc.com, however, the domain name in the Mailer.FromAddress has to be yours. Thus, you may use an Email address like Do_Not_reply@abc.com as the Mailer.FromAddress.

The Email address in the Mailer.AddRecipient field needs to be changed to your Email address, where you wish to receive Emails submitted through the web page.

Sample Script

<%

Set Mailer = Server.CreateObject(“SMTPsvg.Mailer”)
Mailer.FromName = “Testing”
Mailer.FromAddress= “user@abc.com ”
Mailer.RemoteHost = “localhost”
Mailer.AddRecipient “Testing User”, “youremail”
Mailer.Subject = “Testing”
Mailer.BodyText = “Testing”
if Mailer.SendMail then
Response.Write “Mail sent…”
else
Response.Write “Mail send failure. Error was ” & Mailer.Response
end if %>

Tags: , , , , , , , , , , , , , , , ,

17 Aug 10 Collaboration Data Objects (CDO)

 

Originally known as Active Messaging, the Collaboration Data Objects (CDO) library allows users to send mails through ASP Scripts.

Collaboration Data Objects (CDO) is Microsoft’s technology for building messaging or collaboration applications or adding these capabilities to existing applications. Part of the Microsoft Exchange Server product, CDO has evolved from what Microsoft formerly called Object Linking and Embedding Messaging and, more recently, Active Messaging.

You can use the sample script provided by Gossimer and tweak it a bit to your requirements, to accept feedback from your website visitors and get the results emailed to you.

You would need to change the Email address in the field objCDOSYSMail.From to any Email address on the domain name on which you are incorporating the script. For example, if your Domain Name is abc.com, then you would define the From Email address as some-name@abc.com. This Email address need not be existing on the Mail Server of abc.com, however, the domain name in the objCDOSYSMail.From has to be yours. You may use an Email address such as Do_Not_reply@abc.com.

The Email address in the objCDOSYSMail.To field needs to be changed to your Email address, where you wish to receive Emails submitted through the form.

Sample Script 

<%
set objCDOSYSMail = Server.CreateObject(“CDO.Message”)
set objCDOSYSCon = Server.CreateObject(“CDO.Configuration”)
‘Out going SMTP server
objCDOSYSCon.Fields(“http://schemas.microsoft.com/cdo/configuration/smtpserverport”)= 25
objCDOSYSCon.Fields(“http://schemas.microsoft.com/cdo/configuration/smtpconnectiontimeout”)= 60
objCDOSYSCon.Fields.Update
‘Update the CDOSYS Configuration
Set objCDOSYSMail.Configuration = objCDOSYSCon
objCDOSYSMail.From = “some-name@abc.com”
objCDOSYSMail.To = “xyz@abc.com”
objCDOSYSMail.Subject = “Test mail”
objCDOSYSMail.TextBody = “Test Mail”
objCDOSYSMail.Send
Set objCDOSYSMail = Nothing
Set objCDOSYSCon = Nothing
If Err <> 0 Then
Err_Msg = Err_Msg & “<li>Your request was not sent due to the following error: “& Err.Description & “</li>”
End if
%>

 

 

 

IMPORTANT 

The body of the mail should not have bare linefeeds (n). If a bare linefeed is detected, the SMTP service of Microsoft IIS6 (the Web Server running on Gossimer’s Windows servers) will stop delivering any mail and the mails will get struck in the SMTP queue. This is because Microsoft IIS6 strictly follows Internet e-mail standards; and these standards forbid the presence of bare linefeed characters in e-mail messages. Click here for more details >>

For example,

objCDOSYSMail.TextBody = “Thank you for contacting us. We shall get back to you shortly.nKind regardsnabc.com

In the above case, bare linefeeds (n) are being used.

Instead of n, you need to use rn (carriage-return, line-feed). Hence, the correct usage would be -

objCDOSYSMail.TextBody = “Thank you for contacting us. We shall get back to you shortly.rnKind regardsrnabc.com

 

Tags: , , , , , , , , , , , , , , , , , , , , ,

17 Aug 10 What is Managed DNS? Which types of Resource Records does Gossimer allow?

The Domain Name System [DNS] is a distributed database, arranged hierarchically, containing records for domain names. The DNS system’s main aim is to match a domain name to an IP Address. In order to fulfill this role, the DNS Server contains Records [called Resource Records] in a Zone File, which contains the domain name and IP address mappings for computers contained within that Zone. All Resource Records have a TTL [Time To Live], specifying the number of seconds other DNS servers and applications are allowed to cache the record.

Most Web Hosting companies do not provide you with an interface to manage your own DNS Records and/or the ability to select multiple providers for various Services like Web Hosting, Mail Hosting, etc..

Gossimer gives you complete control over the following Resource Records by using our Managed DNS Service:

I. Address Record [A Record]

The A Record is the most basic and the most important DNS record type. They are used to translate human friendly domain names such as “www.domain.com” into IP-addresses such as 1.2.3.4 (machine friendly numbers).

When you wish to host your domain name, you will be provided with an IP address that needs to be set as an A Record for that particular domain name.


II. Mail Exchanger
[MX] Record

A MX Record identifies the mail server(s) responsible for a domain name. When sending an e-mail to user@xyz.com, your mail server must first look up the MX Record for xyz.com to see which mail server actually handles mail for xyz.com (this could be mail.xyz.com – or someone else’s mail server like mail.isp.com). Then it looks up the A Record for the mail server to connect to its IP-address.

A MX Record has a Preference number indicating the order in which the mail server should be used (only relevant when multiple MX Records are defined for the same domain name). Mail servers will attempt to deliver mail to the server with the lowest preference number first, and if unsuccessful continue with the next lowest and so on.


III. Canonical Name
[Alias / CNAME] Record

CNAME Records are domain name aliases. Often computers on the Internet have multiple functions such as Web Server, FTP Server, Chat Server, etc. To mask this, CNAME Records can be used, to give a single computer multiple names (aliases).

Sometimes companies register their multiple domain names for their brand-names but still wish to maintain a single website. In such cases, a  CNAME Record maybe used to forward traffic to their actual website. For example, www.abc.in could be CNAMEd to www.abc.com.

The most popular use of the CNAME Record type, is to provide access to a Web Server using both the standard www.domain.com and domain.com (without the www). This is usually done by adding a CNAME-record for the www name pointing to the short name [while creating an A Record for the short name (without www)].

CNAME Records can also be used when a computer or service needs to be renamed, to temporarily allow access through both the old and new name.


IV. Authoritative Name Server
[NS] Record

NS Records identify DNS servers responsible (authoritative) for a Zone. A Zone should contain one NS Record for each of its own DNS servers (primary and secondaries). This mostly is used for Zone Transfer purposes (notify). These NS Records have the same name as the Zone in which they are located.

But the most important function of the NS Record is Delegation. Delegation means that part of a domain is delegated to other DNS servers.

You can also delegate sub-domains of your own domain name (such as subdomain.yourname.com) to other DNS servers. An NS Record identifies the name of a DNS server, not the IP Address. Because of this, it is important that an A Record for the referenced DNS server exists, otherwise there may not be any way to find that DNS server and communicate with it.

If a NS Record delegates a sub-domain (subdomain.yourname.com) to a DNS Server with a name in that sub-domain (ns1.subdomain.yourname.com), an A Record for that server (ns1.subdomain.yourname.com) must exist in the Parent Zone (yourname.com). This A Record is referred to as a Glue Record, because it doesn’t really belong in the Parent Zone, but is necessary to locate the DNS Server for the delegated sub-domain.


V. Text [TXT] Record

A Text Record provides the ability to associate some text with a domain or a subdomain. This text is meant to strictly provide information and has no functionality as such. A TXT Record can store upto 255 characters of free form text. This record is generally used to convey information about the zone. Multiple TXT records are permitted but their order is not necessarily retained.

For example, you may add a TXT Record for yourname.com with the value as “This is my mail server”. Here if anybody was checking ALL or TXT records of yourname.com, they would notice the above text appearing in the TXT record.

TXT Record is also used to implement the Sender Policy Framework (SPF) and DomainKeys specifications.
 

Sender Policy Framework (SPF)

Sender Policy Framework is an extension to the Simple Mail Transfer Protocol (SMTP). SPF allows software to identify and reject forged addresses in the SMTP MAIL FROM (Return-Path), a typical nuisance in e-mail spam.

SPF allows the owner of a domain to specify their mail sending policy, e.g. which mail servers they use to send mail from their domain. The technology requires two sides to work in tandem -

i. the domain owner publishes this information in an TXT Record in the domain’s DNS zone, and when someone else’s mail server receives a message claiming to come from that domain, then

ii. the receiving server can check whether the message complies with the domain’s stated policy. If, for example, the message comes from an unknown server, it can be considered a fake.

Click here to find more information on SPF and how you may use it to authenticate mails being sent from your domain name >>

DomainKeys

DomainKeys is an e-mail authentication system (developed at Yahoo!) designed to verify the authenticity of the E-mail sender and the message integrity (i.e,. the message was not altered during transit). The DomainKeys specification has adopted aspects of Identified Internet Mail to create an enhanced protocol called DomainKeys Identified Mail (DKIM).

Click here to find more information about DomainKeys and how you can prove and protect an Email Sender’s identity >>
 

VI. Start of Authority [SOA] Parameters

Each Zone contains one SOA Record, which holds the following parameters for the Zone -

Name of Primary DNS Server - The domain name of the Primary DNS Server for the Zone. The Zone should contain a matching NS Record.

Mailbox of the Responsible Person – The email address of the person responsible for maintenance of the Zone.

Serial Number - Used by Secondary DNS Servers to check if the Zone has changed. If the Serial Number is higher than what the Secondary Server has, a Zone Transfer will be initiated. This number is automatically increased by our Servers when changes to the Zone or its Records are made.

Refresh Interval - How often Secondary DNS Servers should check if changes are made to the zone.

Retry Interval - How often Secondary DNS Server should retry checking, if changes are made – if the first refresh fails.

Expire Interval - How long the Zone will be valid after a refresh. Secondary Servers will discard the Zone if no refresh could be made within this interval.

Minimum (Default) TTL - Used as the default TTL for new records created within the zone. Also used by other DNS Server to cache negative responses (such as record does not exist, etc.).

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

15 Aug 10 What is Free DNS? Which types of Resource Records does ResellerClub allow?

The Domain Name System [DNS] is a distributed database, arranged hierarchically, containing records for domain names. The DNS system’s main aim is to match a domain name to an IP Address. In order to fulfill this role, the DNS Server contains Records [called Resource Records] in a Zone File, which contains the domain name and IP address mappings for computers contained within that Zone. All Resource Records have a TTL [Time To Live], specifying the number of seconds other DNS servers and applications are allowed to cache the record.

Most Web Hosting companies do not provide you with an interface to manage your own DNS Records and/or the ability to select multiple providers for various Services like Web Hosting, Mail Hosting, etc..

Gossimer, LLC gives you complete control over the following Resource Records by using our Free DNS Service:

I. Address Record [A Record]

The A Record is the most basic and the most important DNS record type. They are used to translate human friendly domain names such as “www.domain.com” into IP-addresses such as 1.2.3.4 (machine friendly numbers).

When you wish to host your domain name, you will be provided with an IP address that needs to be set as an A Record for that particular domain name.


II. Mail Exchanger
[MX] Record

A MX Record identifies the mail server(s) responsible for a domain name. When sending an e-mail to user@xyz.com, your mail server must first look up the MX Record for xyz.com to see which mail server actually handles mail for xyz.com (this could be mail.xyz.com – or someone else’s mail server like mail.isp.com). Then it looks up the A Record for the mail server to connect to its IP-address.

A MX Record has a Preference number indicating the order in which the mail server should be used (only relevant when multiple MX Records are defined for the same domain name). Mail servers will attempt to deliver mail to the server with the lowest preference number first, and if unsuccessful continue with the next lowest and so on.


III. Canonical Name
[Alias / CNAME] Record

CNAME Records are domain name aliases. Often computers on the Internet have multiple functions such as Web Server, FTP Server, Chat Server, etc. To mask this, CNAME Records can be used, to give a single computer multiple names (aliases).

Sometimes companies register their multiple domain names for their brand-names but still wish to maintain a single website. In such cases, a  CNAME Record maybe used to forward traffic to their actual website. For example, www.abc.in could be CNAMEd to www.abc.com.

The most popular use of the CNAME Record type, is to provide access to a Web Server using both the standard www.domain.com and domain.com (without the www). This is usually done by adding a CNAME-record for the www name pointing to the short name [while creating an A Record for the short name (without www)].

CNAME Records can also be used when a computer or service needs to be renamed, to temporarily allow access through both the old and new name.


IV. Authoritative Name Server
[NS] Record

NS Records identify DNS servers responsible (authoritative) for a Zone. A Zone should contain one NS Record for each of its own DNS servers (primary and secondaries). This mostly is used for Zone Transfer purposes (notify). These NS Records have the same name as the Zone in which they are located.

But the most important function of the NS Record is Delegation. Delegation means that part of a domain is delegated to other DNS servers.

You can also delegate sub-domains of your own domain name (such as subdomain.yourname.com) to other DNS servers. An NS Record identifies the name of a DNS server, not the IP Address. Because of this, it is important that an A Record for the referenced DNS server exists, otherwise there may not be any way to find that DNS server and communicate with it.

If a NS Record delegates a sub-domain (subdomain.yourname.com) to a DNS Server with a name in that sub-domain (ns1.subdomain.yourname.com), an A Record for that server (ns1.subdomain.yourname.com) must exist in the Parent Zone (yourname.com). This A Record is referred to as a Glue Record, because it doesn’t really belong in the Parent Zone, but is necessary to locate the DNS Server for the delegated sub-domain.


V. Text [TXT] RecordA Text Record provides the ability to associate some text with a domain or a subdomain. This text is meant to strictly provide information and has no functionality as such. A TXT Record can store upto 255 characters of free form text. This record is generally used to convey information about the zone. Multiple TXT records are permitted but their order is not necessarily retained.

For example, you may add a TXT Record for yourname.com with the value as “This is my mail server”. Here if anybody was checking ALL or TXT records of yourname.com, they would notice the above text appearing in the TXT record.

TXT Record is also used to implement the Sender Policy Framework (SPF) and DomainKeys specifications.
 

Sender Policy Framework (SPF)

Sender Policy Framework is an extension to the Simple Mail Transfer Protocol (SMTP). SPF allows software to identify and reject forged addresses in the SMTP MAIL FROM (Return-Path), a typical nuisance in e-mail spam.

SPF allows the owner of a domain to specify their mail sending policy, e.g. which mail servers they use to send mail from their domain. The technology requires two sides to work in tandem -

i. the domain owner publishes this information in an TXT Record in the domain’s DNS zone, and when someone else’s mail server receives a message claiming to come from that domain, then

ii. the receiving server can check whether the message complies with the domain’s stated policy. If, for example, the message comes from an unknown server, it can be considered a fake.

Click here to find more information on SPF and how you may use it to authenticate mails being sent from your domain name >>

DomainKeys

DomainKeys is an e-mail authentication system (developed at Yahoo!) designed to verify the authenticity of the E-mail sender and the message integrity (i.e,. the message was not altered during transit). The DomainKeys specification has adopted aspects of Identified Internet Mail to create an enhanced protocol called DomainKeys Identified Mail (DKIM).

Click here to find more information about DomainKeys and how you can prove and protect an Email Sender’s identity >>
 

VI. Start of Authority [SOA] Parameters Each Zone contains one SOA Record, which holds the following parameters for the Zone -

Name of Primary DNS Server - The domain name of the Primary DNS Server for the Zone. The Zone should contain a matching NS Record.

Mailbox of the Responsible Person – The email address of the person responsible for maintenance of the Zone.

Serial Number - Used by Secondary DNS Servers to check if the Zone has changed. If the Serial Number is higher than what the Secondary Server has, a Zone Transfer will be initiated. This number is automatically increased by our Servers when changes to the Zone or its Records are made.

Refresh Interval - How often Secondary DNS Servers should check if changes are made to the zone.

Retry Interval - How often Secondary DNS Server should retry checking, if changes are made – if the first refresh fails.

Expire Interval - How long the Zone will be valid after a refresh. Secondary Servers will discard the Zone if no refresh could be made within this interval.

Minimum (Default) TTL - Used as the default TTL for new records created within the zone. Also used by other DNS Server to cache negative responses (such as record does not exist, etc.).

Tags: , , , , , , , , , , , , , , , , , , , ,

09 Aug 10 Outlook Express

Follow the steps detailed below to use Microsoft Outlook Express 6.0 to send/receive emails from your Email account.

 

1. Start Outlook Express 6.0. On the Tools menu, click Accounts.

express01 Outlook Express

 

2. In the Internet Accounts dialog box, click Add, and then click Mail

express02 Outlook Express

 

3. In the Display name box, type the name that you want others to see when you send a message, and then click Next.

express03 Outlook Express

 

4. In the E-mail address box, type the e-mail address for the account that you are using (for example, user@yourdomainname.com), and then click Next.

express04 Outlook Express

 

5. Under E-mail Server Names, click the appropriate incoming e-mail server type (Post Office Protocol version 3 [POP3] is the default type).

express05 Outlook Express

 

6. Incase you selected POP3 as the incoming mail server in the above step, enter the Incoming mail server as pop.yourdomainname.com. If you selected IMAP as the incoming mail server, then the mail server you need to use is imap.yourdomainname.com. The SMTP server address in any case will be entered as smtp.yourdomainname.com. Once this is done, click Next.

express06 Outlook Express

 

7. Type your complete email address and password in the Account name and Password boxes respectively and then click Next.

express07 Outlook Express

 

8. The next window that you see reads “Congratulations, you have successfully entered all of the information required to set up your account. To save these settings, click Finish.

express08 Outlook Express

 

9. Now again open the Internet Accounts dialog box referring to steps 1 and 2. In the Mail view, you will see the Account you have just added. Now you need to click Properties.

express09 Outlook Express

 

10. Under the Servers tab, you need to check the checkbox My server requires authentication placed under Outgoing Mail Server. Once this is done, click Apply and close the Internet Accounts dialog box.

express10 Outlook Express

 

11. Now under Send/Receive button, click on Send and Receive All and the mails will be download and visible when you click on Inbox which is located in the List of Local Folders as shown below.

express11 Outlook Express

 

IMPORTANT 

Usually, the port used for the Outgoing Mail Server/SMTP Service is 25. However, there might be a situation where your ISP might be blocking the use of port 25 for SMTP service. Many ISPs block port 25 in order to minimize the amount of spam sent using their network. If you are facing issues sending mails using the default port 25, you can confirm with your ISP whether port 25 is indeed blocked by them.

To circumvent this, Gossimer allows you to use an alternate port 2525 for sending mails if port 25 is blocked -

a. In Outlook Express, on the Tools menu, click Accounts.

express01 Outlook Express

 

b. Select the email account you wish to modify and click Properties.

express09 Outlook Express

 

c. Under the Advanced tab, replace the default port number 25 with the alternate port number 2525 in the field provided for Outgoing mail (SMTP).

express12 Outlook Express

 

d. Click OK and then Close to save the changes.

Tags: , , , , , , ,

07 Aug 10 Creating / Modifying various Resource Records [A, MX, CNAME, NS, TXT, SOA]

The managed DNS Service by Gossimer is a very simple and user friendly interface, which allows you to Add/Modify  A, MX, CNAME, NS, TXT & SOA Records.

In order to add records,

1. Login to your Control Panel and search for the Domain name for which you have purchased this service. Click here to learn how >>

2. In the Orders details, click on Manage Records. A new interface will pop-up where you may add any of the following records

I. Address (A) Record

  1. Click on A Records -> Add A Record.
     
  2. There you would find 3 fields
     
    • Host Name: Here the Domain Name for which you are adding the A Record for, would be pre-filled (e.g. yourdomainname.com). Now, if you wish to Add record for my.yourdomainname.com, then you would have to put in my the text box. If you wish to enter A record for just yourdomainname.com, then you can leave this box blank.
       
    • Destination IP Address: Here you would have to enter the IP Address of the Web Server, where you wish to host this domain name.
       
    • TTL: This is the Time To Live for this record, in seconds. Any Server which once queries this record will update this record after this time interval. The ideal TTL is 86400, which is 1 day. It can not be set to less than 14400, i.e. 4 hours.
       
  3. Click on the Add Record button to submit your record.

 

II. MX Record

  1. Click on MX Records -> Add MX Record.
     
  2. There you would find 4 fields
     
    • Zone: The domain name for which you setting an MX Record needs to be entered as the Zone. If you are configuring the mail server for yourdomainname.com, such that you can receive mails@yourdomainname.com, then you need to leave this field blank.
       
    • Value: This is the Mail Server Domain Name. If you are yourself managing your Mail Servers, then you may set the Value in the format – mail.yourdomainname.com.
       
    • If you are using another Internet Service Provider’s Mail Server, then you need to enter a Fully Qualified Domain Name like mail.isp.com. Note that a Fully Qualified Domain Name always ends with a "." in the end.
       
    • TTL: This is the Time To Live for this record. Any Server which once queries this record will update this record after this time interval. The ideal TTL is 86400 which is 1 day. It can not be set to less than 14400, i.e. 4 hours.
       
    • MX Priority: An MX Record has a Preference number indicating the order in which the mail server should be used (only relevant when multiple MX Records are defined for the same domain name). Mail servers will attempt to deliver mail to the server with the lowest preference number first, and if unsuccessful, continue with the next lowest and so on.
       
  3. Click on the Add Record button to submit your record.

 

III. CNAME Record

  1. Click on CNAME Records -> Add CNAME Record.
     
  2. There you would find 3 fields
     
    • Host Name: If you wish to Add a CNAME Record for yourdomainname.com like manage.yourdomainname.com or www.yourdomainname.com, then enter the Host Name as manage or www  in this text box.
       
    • Value: This is the Destination for the CNAME created. Thus, if you wish to create a CNAME Record for www.yourdomainname.com pointing to yourdomainname.com, then you would have to enter yourdomainname.com. in this text box.
       
    • TTL: This is the Time To Live for this record. Any DNS Server which once queries this record will update this record after this time interval. The ideal TTL is 86400, which is 1 day. It can not be set to less than 14400, i.e. 4 hours.
       
  3. Click on the Add Record button to submit your record.

 

IV. NS Record

  1. Click on NS Records -> Add NS Record.
     
  2. There you would find 3 fields
     
    • Zone: If you wish to create a Name Server for a sub-domain like ns1.subdomain.yourdomainname.com, then enter the Zone as subdomain.yourdomainname.com in this text box.
       
    • Value: This is the Name of the Name Server to be created or another Fully Qualified Domain Name that you want to make responsible for this Zone. Thus, if you wish to create an NS Record for subdomain.yourdomainname.com, you may enter the value as ns1.subdomain.yourdomainname.com. Or, you may want a Name Server like ns1.subdomain.yourdomainname.com to be delegated to another Fully Qualified Domain Name like dns1.anyotherns.com.
       
    • TTL: This is the Time To Live for this record. Any DNS Server which once queries this record will update this record after this time interval. The ideal TTL is 86400, which is 1 day. It can not be set to less than 14400, i.e. 4 hours.
       
  3. Click on the Add Record button to submit your record.

 

V. TXT Record

  1. Click on TXT Records -> Add TXT Record.
     
  2. There you would find 3 fields
     
    • Host Name: If you wish to Add a TXT Record for yourdomainname.com like yourdomainname.com, then leave the Host Name text box blank.
       
    • Value: 255 characters of free form text can be provided in this field. This record is generally used to convey information about the zone.

      For example, you may add a TXT Record for mail.yourdomainname.com with the value as "This is my mail server". Here if anybody was checking ALL or TXT records of mail.yourdomainname.com, they would notice the above text appearing in the TXT record.
       

    • TTL: This is the Time To Live for this record. Any DNS Server which once queries this record will update this record after this time interval. The ideal TTL is 86400, which is 1 day. It can not be set to less than 14400, i.e. 4 hours.
       
  3. Click on the Add Record button to submit your record.

 

VI. SOA Parameters

The moment you buy Managed DNS Service from Gossimer, a default Start Of Authority [SOA] Record is created for your domain name. To modify your SOA Record -

  1. Click on SOA Parameters -> Modify Record.
     
  2. There you would find 5 fields
     
    • TTL: This is the Time To Live for this record. Any DNS Server which once queries this record will update this record after this time interval. The ideal TTL is 86400, which is 1 day. It can not be set to less than 14400, i.e. 4 hours.
       
    • Serial: This is a number that is automatically generated by our Servers. All Secondary Name Servers cache the Serial Number in the SOA Record, such that when a Serial Number change is detected by Secondary DNS Servers, it updates its Records with the changes. This number is automatically increased by our Servers when changes to the Zone or its Records are made.
       
    • Refresh: The Refresh Interval indicates how often Secondary Name Servers should check if changes are made to the Zone. You can decide your own value for this Interval.
       
    • Retry: The Retry Interval indicates how often the Secondary Name Servers should retry checking, if changes are made – if the first refresh fails.
       
    • Expire: The Retry Interval indicates how long the Zone will be valid after a refresh. Secondary Servers will discard the Zone, if no refresh could be made within this interval.
       
  3. Click on the Modify Record button to submit your changes.
     
IMPORTANT

Upon adding any Managed DNS Record, you are required to make modifications to your domain name’s Name Servers as well. Click here to know how you can start using your Managed DNS service >>
 

Tags: , , , , , , , , , , ,