The only party that truly has access to provide you with reverse DNS on your IP block is your ISP. Your ISP has the power to either delegate authority for reverse DNS to another party, or to provide reverse DNS themselves.
We can't simply setup reverse DNS for you unless you have a colocated or dedicated server with us. If you need reverse DNS for your home or office broadband connection, please contact your ISP.
At this point, we don't provide free reverse DNS, so your best bet is to ask your ISP to provide it to you directly rather than having it delegated to us.
We do, however, provide specialized reverse DNS on the enterprise level if you are in need of this service.
Thanks,
Sitelutions Support
On the page to which you are taken, you will be able to add, remove, or change the nameservers that are used by the domain. To change the nameservers to our own, simply select the radio button next to "use Sitelutions" and click "Save Changes".
If the domain's registrar is not Sitelutions, you will need to make this nameserver change with the current registrar.
]]>Do the following:
Unfortunately this a problem that you will have to troubleshoot on your end -- if our DNS is working correctly, there is not much more we can do.
]]>
Good news! You can use Sitelutions to help you run a web server anyway!
First, find a port that your ISP allows connections to. Typically port 8080 will work. Try this by having a friend on another internet connection access your IP address like so: http://123.45.789.10:8080/. If the friend is able to get through and see your site, everything is good.
Next you will need to add a "secondary" hostname which you will update via one of our Dynamic DNS Update Clients. You can use "www2.yourdomain.com." Go to the URL & DNS Control Center to add this. Then add an A record for this domain pointing to your IP (see http://www.sitelutions.com/myip to retrieve it). Next, get the ID of this A record by clicking "Advanced Config," finding the A record, and clicking the "DynDNS" or "Dynamic DNS" link next to it.
Once you have the ID, configure your update client with it and make sure all is working.
Then, using the DNS Wizard, set www.yourdomain.com and "root domain" (yourdomain.com) to redirect to http://www2.yourdomain.com:8080/.
It is that simple. If you follow these instructions carefully, it should work well for you!
]]>
DNS is a complex system. Despite the fact that our system propogates updates instantly to our global network of nameservers, there are a few factors that can prevent your domain or hostnames from resolving properly. There are also a few factors which can cause DNS updates to take quite a while -- often 1-2 days or more to complete.
First, make sure you have made the appropriate modifications with your registrar and set our nameservers up as the authoritative servers for your domain. If you registered your domain with Sitelutions and chose "Use Sitelutions Nameservers," you need not worry about this. If not, this is a simple process of logging into your current registrar, finding the "modify nameservers" screen (ask them for help if you cannot find it), and changing the nameservers to the ones that we provide in the "Add Domain" screen (just login to your Sitelutions Account to see this list).
Once you have modified nameservers settings so that our servers are set as the authoritative nameservers for your domain, your registrar will typically take 24-48 hours to update the root nameservers for your top-level domain (.com, .net, .org, .us, etc.).
Please make sure that DNS is now properly configured with Sitelutions. If you have a Sitelutions Space hosting account, the system automatically configures DNS -- you do not need to make any special DNS changes! If you are managing a custom DNS configuration or doing your hosting elsewhere, you should setup the proper DNS records for your domain.
Even after making these changes, your domain / hostnames may take quite a while to work.
Why? All DNS records ("resource records") contain a "TTL," or time-to-live. This TTL tells DNS resolvers (like those that your ISP uses to look up DNS information for you when you request a given domain name) how long to cache DNS records. This is useful because it reduced the number of DNS queries made to the authoritative DNS provider by allowing global resolvers to cache DNS records for an extended period of time. Because they have the records cached, they do not need to look any further or go out to the internet for more information.
Many DNS providers, by default, use a high TTL, such as 86400 seconds (one day), or even greater. Some DNS providers, in an attempt to save money use a default TTL of 2, 3, or even 7 days.
If your previous DNS provider used a high TTL, you may have to wait quite a while until old, incorrect DNS information expires from global DNS resolvers for your domain to work properly. In almost all cases, our DNS is working properly -- it's just a matter of letting old, cached records expire.
If it's been a few days and you are still concerned, you might want to have several friends who are using different ISPs than yours check your domain name -- each will be using different DNS resolvers, which may NOT have DNS information cached for your domain. You might find that some friends get the proper DNS information for your site while some don't -- this is perfectly normal. In a few days, any cached DNS information should begin working and you should see your domain name.
Note that TTL and previous DNS settings are out of our control -- therefore, there is absolutely nothing we can do to speed up this process, or to force remotely cached DNS information to expire -- we'd have to contact every single ISP or operator of a DNSresolver (there is no published list, and if there was, it would probably consist of hundreds of thousands of DNS resolvers) and force them to clear their cache.
If you have a small, local ISP, you might be able to convince them to flush their DNS cache manually. Larger ISPs will typically not do this for you.
If your domain still doesn't work after 7 business days, it's likely that there's a DNS configuration error -- please contact us.
]]>
1) Setup your home web server to run on another port. In this example we'll use port 8080. Make sure your ISP isn't blocking this port. You may have to try several ports before you find one that your ISP isn't blocking.
2) Setup www.yourdomain.com. Add a redirect so that it redirects to http://www2.yourdomain.com:8080/.
3) Add www2.yourdomain.com and create an A record for this. You may use dynamic DNS to update this A record -- you can find help on this in the help section at http://www.sitelutions.com/help/
4) Make sure your broadband router is configured to forward any traffic for port 8080 to the appropriate server on your network.
5) That's it. When people access www.yourdomain.com, they should be redirected to www2.yourdomain.com:8080 and have access to your site.
Thanks,
Sitelutions Support
These registrars/registries will often complain about ttl, serial, refresh, and other values associated with the SOA record.
Sitelutions now offers each user the ability to modify all information that is part of the start of authority, including the owner's mailbox as stored in the SOA record.
Simply navigate to the domain control center, select all domains that you want to modify (check the box next to these domains), and click "Modify SOA Record(s)".
Simply make your modifications, save your changes, and viola.
PLEASE MAKE SOA MODIFICATIONS AT YOUR OWN RISK! If you do not know what you are doing, you could cause damage to your domain name's ability resolve. Please be careful.
Thanks,
Sitelutions Support
While our dynamic DNS services are extremely easy-to-use and reliable, many of our users have problems because they've setup their DNS update software incorrectly.
If you're having a problem with DynSite or you're receiving a "failure (not owner)" error message from our server, please continue reading and follow the directions specified.
This KnowledgeBase entry will provide you with information on setting up DynSite.
If you are using Sitelutions DNS, setting up mail routing for your domain is simple.
First, you must have a mail server accepting mail for your domain name. This is a server that is either provided by your ISP or that you are running on your home broadband connection. This server must accept mail on port 25 (SMTP). We recommend that you have some system administration experience before attempting to run your own mail server. We cannot provide general system administration support to our users.
First you need to set up a DNS "A" record for your mail server. For the example we'll set mail.domain.com to be the SMTP server for your domain, domain.com. To set everything up, go to the Sitelutions URL & DNS Control Center.
You are now done creating your MX record for your domain. Note that it may take global DNS resolvers a period of time to flush old cached DNS information for your domain. Typically, this takes less than 24-48 hours. If mail for your domain still does not work after 24-48 hours, please contact support.
]]>When you add a domain, Your CNAME record in your DNS is set to "domainpark.sitelutions.com" by default to park your domain to Sitelutions.
This is a feature to keep your domain name's website available and displaying a clean web page created by us instead of an giving an error while you develop your own web page.
In order to stop your domain from pointing to Sitelutions, go to the URL & DNS Control Center, go to Advanced Configuration for the given hostname or [root domain], and remove this CNAME record.
]]>