Author Topic: Calan Technologies  (Read 1313 times)

SilentRage

  • Newbie
  • *
  • Posts: 0
    • View Profile
Calan Technologies
« Reply #15 on: March 07, 2004, 03:14:00 am »
Quote:
http://www.dollardns.net/index.html?http://www.dollardns.net/manage.html

\"# Sean Cahill (info@calanhost.com) of Calan Technologies

I had some troubles with my ensim control panel where the domains wouldn\'t resolve for some clients. The ensim support said all was fine, but I didn\'t believe them. I hired DollarDNS to take a look at it and he found the problem and fixed it in only one hour! He even taught me how to manage things in the future. He only asked for $3, but I gave him $30.\"

I understand that someone has to teach everyone, but this guy is running a business and didn\'t know how to manage his DNS server... still, I wasn\'t able to find anything saying pricedrightdomains bought them out, would you mind posting a link for it?


In his defense, it was not a typical everyday problem.  As stated even the ensim support tried to help him but didn\'t know what the problem was.  I specialize in DNS so therefor know a bit more than the average dns administrator.  I\'ve noticed many google searches for calan coming my way, that is the email address I used when speaking with him.  If it\'s down, then I don\'t know how you can contact him.  The above service was rendered Jan. 26, 2004.

JohnScott

  • Newbie
  • *
  • Posts: 0
    • View Profile
Calan Technologies
« Reply #16 on: March 07, 2004, 03:35:00 am »
What was the problem with the DNS? Just curious.

SilentRage

  • Newbie
  • *
  • Posts: 0
    • View Profile
Calan Technologies
« Reply #17 on: March 07, 2004, 04:35:00 am »
The NS records in the zone did not match the registered hosts for the domain.  People tend to be lazy about whether the NS records match the \"true\" hosts, but it is actually very important that they match.  The reason is cause even though host information is provided at the root servers, the NS records are cached by many (but not all) name servers.  If the NS records are wrong then when cached, the caching server will fail all further requests for that domain until the cached NS records expire.

The result is a domain that sometimes resolves and sometimes not, and resolve for some people and not for others - depending on whether the server caches the root server NS records for the domain, or the authoritative (zone) NS records.  Here\'s a graphical example:

[registered name servers]
http://www.dollardns.net/cgi-bin/dnscrawler/index.pl?server=a.root-servers.net&name=litplanet.com&type=NS&class=IN&lr=1&submit=IMR

[zone name servers]
http://www.dollardns.net/cgi-bin/dnscrawler/index.pl?server=dns.theharddrive.net&name=litplanet.com&type=NS&submit=IMR

As you can see they don\'t match, but the guy is safe in this case since both registered and zone name servers return the same information.  Discouraged configuration however.

JohnScott

  • Newbie
  • *
  • Posts: 0
    • View Profile
Calan Technologies
« Reply #18 on: March 07, 2004, 04:56:00 am »
Interesting stuff. You should stick around and help us out in the hosting/dedicated server forums.

SilentRage

  • Newbie
  • *
  • Posts: 0
    • View Profile
Calan Technologies
« Reply #19 on: March 07, 2004, 05:15:00 am »
heh, thanks for the invitation but I\'m already busy swamping 2 other DNS forums with help.

http://www.serverexpert.com/forum/viewforum.php?f=8
http://forums.devshed.com/forumdisplay.php?f=36

It\'s my form of advertising.    internet-marketing-research is an impressively active site if the number of people linking from here to my site is any indication.  It\'s tempting.