This utility will let you check the DNS records returned by 110mb nameservers for any domain
(or subdomain) name.
These records should be identical on both nameservers, but unfortunatelly 110mb nameservers
are known to be not so reliable and enough often may be not synchronised or does not contain
records for some domains at all and this tool has been created to more easily detect such problem.
Note that if you do not use 110mb nameservers as authoritative for your domain name
the results displayed are completely irrelevant for the accessibility of your website.
Because of anti-bot protection you need to have javascript enabled in your browser.
Internet Explorer users: click "check this domain" button, hitting "enter" on keyboard
seems to not work.
You need to have javascript enabled to use this utility.
Please, turn it ON in your browser settings.
Below are presented times set at the 110mb servers.
If there is some difference, then most probably time is not synchronised.
Difference below 15 seconds may be just the result of delayed server responce time for the request.
| Box 4 | - - - | no info |
| Box 5 | - - - | no info |
| Box 9 | - - - | no info |
| Box 11 | - - - | no info |
| Box 12 | - - - | no info |
| Box 13 | - - - | no info |
| Box 14 | - - - | no info |
| Box 15 | - - - | no info |
| Box 16 | - - - | no info |
| Box 17 | - - - | no info |
| Box 18 | - - - | no info |
| Box 19 | - - - | no info |
| Box 21 | - - - | no info |
| 110mb.com | Tue, 07 Jul 2015 20:00:54 GMT | OK |
| 110mb.info | Tue, 07 Jul 2015 20:00:54 GMT | OK |
Between 2011-05-24 and 2011-05-31 time was not synchronised on box 14 (~54 minutes behind).
Between 2011-05-26 and 2011-05-27 time was not synchronised on box 12 (~36 minutes ahead).
Since 2011-05-26 time is not synchronised on box 11 (~4 minutes ahead).
Since 2011-07-12, after 14 hours downtime, time is 4 hours behind on box 21 (with "premium" accounts).
2011-11-23 - box18 -00:00:03, box19 -00:17:09 (+/- 1 sec.)
2011-12-24 - box18 -00:00:07, box19 -00:24:41 (+/- 1 sec.)
2012-01-15 - box14 -00:00:09, box17 -00:00:18, box19 -00:02:53 (+/- 1 sec.)
2012-01-29 - box17 -00:00:21, box18 +00:00:04 (+/- 1 sec.)
2012-02-19 - box17 -00:00:33, box18 +00:00:01 (+/- 1 sec.)
2012-02-26 - box17 -00:00:13, box18 +00:00:02 (+/- 1 sec.)
2012-03-11 - box17 -00:00:47, box18 +00:00:05 (+/- 1 sec.)
2012-03-25 - box17 -00:01:21, box18 +00:00:08 (+/- 1 sec.)
2012-04-08 - box17 -00:00:30, box18 -00:00:01 (+/- 1 sec.)
2012-04-22 - box17 -00:01:38, box18 -00:00:07 (+/- 1 sec.)
2012-05-06 - box17 -00:00:21, box18 -00:00:14 (+/- 1 sec.)
2012-09-30 - box17 -00:01:48, box18 +00:06:12 (+/- 1 sec.)
Below are presented DNS entries on 110mb nameservers for examples of "extra" domain names
hosted on 110mb servers. If there is no entries on one or both 110mb nameservers then something
is most probably wrong.
This tool has been created because of the ongoing problems with 110mb nameservers
being not functional for "extra" domains added by the users on their 110mb accounts.
| From ns1.110mb.com | From ns2.110mb.com | |
| example domain 1 hosted on box 4, added in March 2009 |
- - - - - |
. 86400 IN A 204.12.247.100 |
| example domain 2 hosted on box 13, added in March 2009 |
- - - - - |
- - - - - |
| example domain 3 hosted on box 4, added in April 2010 |
- - - - - |
. 86400 IN A 204.12.247.100 |
| example domain 4 hosted on box 11, added in December 2009 |
- - - - - |
- - - - - |
| example domain 5 hosted on premium server, previously on box 17, added in July 2010 |
- - - - - |
. 86400 IN A 64.120.180.52 |
| example domain 6 hosted on box 15, added in December 2008 |
- - - - - |
. 86400 IN A 63.141.253.84 |
| example domain 7 hosted on box 16, added in August 2009 |
- - - - - |
- - - - - |
| example domain 8 hosted on box 17, added in July 2009 |
- - - - - |
- - - - - |
| example domain 9 hosted on box 15, added in August 2010 |
- - - - - |
. 86400 IN A 63.141.253.84 |
| example domain 10 hosted on box 18, added in July/August 2010 |
- - - - - |
- - - - - |
| example domain 11 hosted on box 18, added in May 2010 |
- - - - - |
. 86400 IN A 174.142.79.83 |
| example domain 12 hosted on box 18, added in June 2010 |
- - - - - |
- - - - - |
| example domain 13 hosted on box 17, added in December 2009 |
- - - - - |
. 86400 IN A 70.38.113.158 |
| example domain 14 hosted on box 15, added in September 2008 |
- - - - - |
. 86400 IN A 63.141.253.84 |
| example domain 15 hosted on premium server, previously on box 4, added in July 2010 |
- - - - - |
. 86400 IN A 64.120.180.52 |
| example domain 16 hosted on box 14, added in December 2010 |
- - - - - |
. 86400 IN A 63.141.253.76 |
| example domain 17 moved outside of 110mb - good choice, previously on box 18, added in December 2010 |
- - - - - |
- - - - - |
| example domain 18 hosted on box 18, added in December 2010 |
- - - - - |
. 86400 IN A 174.142.79.83 |
| example domain 19 hosted on premium server, previously on box 4, added in March 2007 |
- - - - - |
. 86400 IN A 204.12.247.100 |
| example domain 20 hosted on box 18, added in February 2011 |
- - - - - |
- - - - - |
| example domain 21 hosted on premium server, previously on box 17, added in August 2010 |
- - - - - |
. 86400 IN A 64.120.180.52 |
| example domain 22 hosted on premium server, previously on box 17, added in May 2009 |
- - - - - |
. 86400 IN A 64.120.180.52 |
| example subdomain 1 moved from box 4 to "premium" |
- - - - - |
. 600 IN A 64.120.180.52 |
| example subdomain 2 moved from box 4 to "premium" |
- - - - - |
. 600 IN A 64.120.180.52 |
| example subdomain 3 moved from box 4 to "premium" |
- - - - - |
. 600 IN A 64.120.180.52 |
| example subdomain 4 moved from box 5 to "premium" |
- - - - - |
. 600 IN A 64.120.180.52 |
| example subdomain 5 moved from box 17 to "premium" |
- - - - - |
. 600 IN A 64.120.180.52 |
| example subdomain 6 hosted on box 18 |
- - - - - |
. 600 IN A 174.142.79.83 |
| example subdomain 7 hosted on box 18, previously on box 4 |
- - - - - |
. 600 IN A 174.142.79.83 |
| example subdomain 8 hosted on box 18, previously on box 12 |
- - - - - |
. 600 IN A 174.142.79.83 |
| example subdomain 9 hosted on box 18, previously on box 12 |
- - - - - |
. 600 IN A 174.142.79.83 |
| example subdomain 10 hosted on box 18, previously on box 12 |
- - - - - |
. 600 IN A 174.142.79.83 |
| example subdomain 11 moved from box 17 to "premium" |
- - - - - |
. 600 IN A 64.120.180.52 |
| example subdomain 12 moved from box 17 to "premium" |
- - - - - |
. 600 IN A 64.120.180.52 |
| From ns1.110mb.com | From ns2.110mb.com |
Since 2010-09-17, Friday, 110mb nameservers started to "drop" DNS entries for some of the "extra" domains - again, like several times already in the past. Having this in mind - using 110mb nameservers for own domain names hosted on 110mb is still NOT recommended, use some other instead.
On 2010-09-19, Sunday, ns2.110mb.com has the entries for "extra" domains again, entries on ns1.110mb.com are still missing.
Since 2010-09-20, Monday, both 110mb nameservers do have DNS records for most of the "extra" domains back again. Issue seems to be fixed.
Since 2010-10-06, Wednesday, ns1.110mb.com do NOT have DNS records for most of the "extra" domains again.
Since 2010-10-10/11, Sunday/Monday, ns1.110mb.com do have DNS records for most of the "extra" domains, it's fixed. Box 18's "extra" domains are pointed to different IP than *.110mb.com and *.911mb.com subdomains, though.
At 2010-10-18, Monday, ns2.110mb.com do NOT have any DNS records for 110mb.com domain name and (probably) all subdomains of it.
Situation of "extra" domain names on both - ns1 and ns2 - nameservers is (again) quite bad, lots of DNS entries are missing. After 13-14 hours it has been fixed.
At 2010-10-24, Sunday, ns2.110mb.com did NOT have any DNS records for majority of domain names for several hours again. It's fixed now.
At 2010-10-28, Thursday, ns1.110mb.com did NOT have any DNS records for majority of domain names.
At 2010-10-29, Friday, ns2.110mb.com did NOT have any DNS records for majority of domain names.
At 2010-11-02, Tuesday, after some general problems with the server, ns1.110mb.com did NOT have any DNS records for majority of domain names. Fixed after ~day and a half.
Between 2010-11-25 and 2010-12-06 - for 11 days - ns2 did not work at all.
Between 2010-12-15, Wednesday, and 2010-12-21, Tuesday, for 6 days, after general problems with the whole main 110mb.com server and several hours of not working at all, ns1 has lost entries for some of the domain names again.
(...) Three or four entries about problems not included, sorry. (...)
At 2011-04-03 ns1 has lost entries for majority of "extra" domain names. Fixed after 2 days.
At 2011-04-04 ns2 was very slow for ~7 hours.
At 2011-04-14 ns1 has lost entries for majority of "extra" domain names again. Fixed after ~7-8 days.
This part of the service have to be expanded, so you can ask me to add your example domain name to query, as I need enough representative collection of domain names added in the past and just recently, used on various 110mb servers (boxes) - just contact me through email provided in the footer of this page with subject line "110mb DNS Check".
Below are presented DNS entries for examples of *.110mb.com and correspondent *.911mb.com
subdomains on every 110mb server. If different, then something
is most probably wrong.
This tool has been created because of the problem with numerous incorrect entries for *.911mb.com
subdomains reported in this topic on 110mb forum.
box4.110mb.com. 600 IN A 204.12.247.99 | box4.911mb.com. 600 IN A 204.12.247.99 |
|
speedsuccess.110mb.com. 600 IN A 204.12.247.100 |
speedsuccess.911mb.com. 600 IN A 204.12.247.100 |
box10.110mb.com. 600 IN A 83.149.75.77 | box10.911mb.com. 600 IN A 83.149.75.77 |
|
bugawuga12.110mb.com. 600 IN A 204.12.247.100 |
bugawuga12.911mb.com. 600 IN A 204.12.247.100 |
box5.110mb.com. 600 IN A 204.12.247.102 | box5.911mb.com. 600 IN A 204.12.247.102 |
|
bugawuga10.110mb.com. 600 IN A 204.12.247.103 |
bugawuga10.911mb.com. 600 IN A 204.12.247.103 |
box9.110mb.com. 600 IN A 204.12.247.105 | box9.911mb.com. 600 IN A 204.12.247.105 |
|
bugawuga11.110mb.com. 600 IN A 204.12.247.106 |
bugawuga11.911mb.com. 600 IN A 204.12.247.106 |
box11.110mb.com. 600 IN A 204.12.247.108 | box11.911mb.com. 600 IN A 204.12.247.108 |
|
bugawuga13.110mb.com. 600 IN A 204.12.247.109 |
bugawuga13.911mb.com. 600 IN A 204.12.247.109 |
box12.110mb.com. 600 IN A 204.12.247.111 | box12.911mb.com. 600 IN A 204.12.247.111 |
|
bugawuga14.110mb.com. 600 IN A 204.12.247.112 |
bugawuga14.911mb.com. 600 IN A 204.12.247.112 |
box13.110mb.com. 600 IN A 63.141.253.67 | box13.911mb.com. 600 IN A 63.141.253.67 |
|
bugawuga15.110mb.com. 600 IN A 63.141.253.68 |
bugawuga15.911mb.com. 600 IN A 63.141.253.68 |
box14.110mb.com. 600 IN A 63.141.253.75 | box14.911mb.com. 600 IN A 63.141.253.75 |
|
bugawuga16.110mb.com. 600 IN A 63.141.253.76 |
bugawuga16.911mb.com. 600 IN A 63.141.253.76 |
box15.110mb.com. 600 IN A 63.141.253.83 | box15.911mb.com. 600 IN A 63.141.253.83 |
|
bugawuga17.110mb.com. 600 IN A 63.141.253.84 |
bugawuga17.911mb.com. 600 IN A 63.141.253.84 |
box16.110mb.com. 600 IN A 174.142.109.137 | box16.911mb.com. 600 IN A 174.142.109.137 |
|
bugawuga21.110mb.com. 600 IN A 174.142.109.139 |
bugawuga21.911mb.com. 600 IN A 174.142.109.139 |
box17.110mb.com. 600 IN A 70.38.113.153 | box17.911mb.com. 600 IN A 70.38.113.153 |
|
bugawuga27.110mb.com. 600 IN A 70.38.113.158 |
bugawuga27.911mb.com. 600 IN A 70.38.113.158 |
box18.110mb.com. 600 IN A 174.142.79.82 | box18.911mb.com. 600 IN A 174.142.79.82 |
|
bugawuga28.110mb.com. 600 IN A 174.142.79.83 |
bugawuga28.911mb.com. 600 IN A 174.142.79.83 |
box19.110mb.com. 600 IN A 204.12.247.114 | box19.911mb.com. 600 IN A 204.12.247.114 |
|
server19.110mb.com. 600 IN A 204.12.247.115 |
server19.911mb.com. 600 IN A 204.12.247.115 |
box21.110mb.com. 600 IN A 64.120.180.51 | box21.911mb.com. 600 IN A 64.120.180.51 |
|
premium_example.110mb.com. 600 IN A 64.120.180.52 |
premium_example.911mb.com. 600 IN A 64.120.180.52 |
DNS records for *.911mb.com subdomains on boxes 4/10, 5, 11, 12, 14, 16, 17 has been (partially or completely) fixed. But DNS records for *.911mb.com subdomains on boxes 9, 13, 15, 18 are INcorrect.
Since 2010-08-07 the issue seems to be fixed.
DNS records for *.911mb.com subdomains on all servers are correct.
Related informations:
-
Changelog of the service:
2010-06-17 - Start of this service that check (in)correct entries for *.911mb.com subdomains.
2010-07-26 - Backup copy of the service created.
2010-07-30 - Service expanded to check the entries on 110mb nameservers for "extra" domains.
