Thursday, 26 November 2009

Sunrise for Russian Federation top level domain .RF (.РФ )

Today, November 25, 2009 starting 12.00 MSK trademark holders may
enjoy .РФ Domains Sunrise Registration.

The .РФ Top level domain stands for "R.F." or Russian Federation.

Before March 25, 2010 RU-CENTER clients - Russian-named trademark
holders may register .РФ domains at 1200 rub.

Before submitting an application for .РФ domain registration we recommend
that you study "Sunrise Registration Schedule in РФ TLD".

Further details about .РФ domains sunrise registration are given at

To learn more about РФ TLD please refer to

Friday, 20 November 2009

IP address change of main Nameservers


IP Addresses of the nameservers on are changing from:, from to, from to

This change will be finalized on the 18th of December 2009, when the old IP address will
fail to work.

Wednesday, 18 November 2009

Into DNS, a free DNS checking service

Status Test name Information
Parent Info Domain NS records Nameserver records returned by the parent servers are: [''] (NO GLUE) [TTL=14400] [''] (NO GLUE) [TTL=14400] was kind enough to give us that information.
Pass TLD Parent Check Good., the parent server I interogated, has information for your TLD. This is a good thing as there are some other domain extensions like "" for example that are missing a direct check.
Pass Your nameservers are listed Good. The parent server has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers.
Info DNS Parent sent Glue The parent nameserver is not sending out GLUE for every nameservers listed, meaning he is sending out your nameservers host names without sending the A records of those nameservers. It's ok but you have to know that this will require an extra A lookup that can delay a little the connections to your site. This happends a lot if you have nameservers on different TLD ( for example with nameserver
Pass Nameservers A records Good. Every nameserver listed has A records. This is a must if you want to be found.
NS Info NS records from your nameserversNS records got from your nameservers listed at the parent NS are: [''] [TTL=7200] [''] [TTL=7200]

Error Recursive Queries I could use the nameservers listed below to performe recursive queries. It may be that I am wrong but the chances of that are low. You should not have nameservers that allow recursive queries as this will allow almost anyone to use your nameservers and can cause problems. Problem record(s) are:
Warn Same Glue Looks like the A records (the GLUE) got from the parent zone check are different than the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do.I detected some problems as follows:
For the parent reported: [''] and your nameservers reported: ['']
For the parent reported: [''] and your nameservers reported: ['']
Pass Glue for NS records OK. When I asked your nameservers for your NS records they also returned the A records for the NS records. This is a good thing as it will spare an extra A lookup needed to find those A records.
Pass Mismatched NS records OK. The NS records at all your nameservers are identical.
Pass DNS servers responded Good. All nameservers listed at the parent server responded.
Pass Name of nameservers are valid OK. All of the NS records that your nameservers report seem valid.
Pass Multiple Nameservers Good. You have multiple nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me.
Pass Nameservers are lame OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
Pass Missing nameservers reported by parent OK. All NS records are the same at the parent and at your nameservers.
Pass Missing nameservers reported by your nameservers OK. All nameservers returned by the parent server are the same as the ones reported by your nameservers.
Pass Domain CNAMEs OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Pass NSs CNAME check OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
Pass Different subnets OK. Looks like you have nameservers on different subnets!
Pass IPs of nameservers are public Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like
Pass DNS servers allow TCP connection OK. Seems all your DNS servers allow TCP connections. This is a good thing and usefull even if UDP connections are used by default.
Pass Different autonomous systems OK. It seems you are safe from a single point of failure. You must be carefull about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down.
Pass Stealth NS records sent Ok. No stealth ns records are sent
SOA Info SOA recordThe SOA record is:
Primary nameserver:
Hostmaster E-mail address:
Serial #: 1256841781
Refresh: 28800
Retry: 7200
Expire: 2419200 4 weeks
Default TTL: 7200
Pass NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is 1256841781.
Pass SOA MNAME entry OK. That server is listed at the parent servers.
Warn SOA Serial Your SOA serial number is: 1256841781. This can be ok if you know what you are doing.
Pass SOA REFRESH OK. Your SOA REFRESH interval is: 28800. That is OK
Pass SOA RETRY Your SOA RETRY value is: 7200. Looks ok
Pass SOA EXPIRE Your SOA EXPIRE number is: 2419200.Looks ok
Pass SOA MINIMUM TTL Your SOA MINIMUM TTL is: 7200. This value was used to serve as a default TTL for records without a given TTL value and now is used for negative caching (indicates how long a resolver may cache the negative answer). RFC2308 recommands a value of 1-3 hours. Your value of 7200 is OK.
MX Info MX RecordsYour MX records that were reported by your nameservers are:


[These are all the MX records that I found. If there are some non common MX records at your nameservers you should see them below. ]
Pass Different MX records at nameservers Good. Looks like all your nameservers have the same set of MX records. This tests to see if there are any MX records not reported by all your nameservers and also MX records that have the same hostname but different IPs
Pass MX name validity Good. I did not detect any invalid hostnames for your MX records.
Pass MX IPs are public OK. All of your MX records appear to use public IPs.
Pass MX CNAME Check OK. No problems here.
Pass MX A request returns CNAME OK. No CNAMEs returned for A records lookups.
Pass MX is not IP OK. All of your MX records are host names.
Info Number of MX records OK. Looks like you only have one MX record at your nameservers. You should be carefull about what you are doing since you have a single point of failure that can lead to mail being lost if the server is down for a long time.
Pass Mismatched MX A OK. I did not detect differing IPs for your MX records.
Pass Duplicate MX A records OK. I have not found duplicate IP(s) for your MX records. This is a good thing.
Pass Reverse MX A records (PTR) Your reverse (PTR) record: ->
You have reverse (PTR) records for all your IPs, that is a good thing.
WWW Info WWW A Record Your A record is: []
Pass IPs are public OK. All of your WWW IPs appear to be public IPs.

Processed in 0.214 seconds.

This is a sample domain set up on, and the report is from IntoDNS

Thursday, 5 November 2009

Attract new customers with a free £75.00 voucher

Redeem your AdWords voucher in just minutes:

  1. Visit Google Adwords and click "Try AdWords now" to create your account.
  2. Log into your new AdWords account, and we'll help you create your first campaign, step by step.
  3. In your AdWords account, fill out your “Billing Preferences”.
  4. In the 'Promotional Code' field, enter the following exactly as given: HHMZ-2A52-NN2P-82MG-VTW
  5. Click “Save and Activate.” Now you’re ready to go live and start acquiring new customers.
(Offer is limited to one per customer)