If external visitors to your network are able to reach your services, but you can't view them locally using the host, you are experiencing a loopback connection error. Instead of correctly interpreting your request and routing you locally, the router gets confused and you simply can't connect. In some instances, this can be fixed by changing security settings in your router such as the "Filter Internet NAT Redirection" setting in Linksys devices.

This is also a loopback connection error. The router mistakenly believes you that are attempting to connect to the router instead of to local services running on port 80. External visitors do not see your router's login screen, however, and should be able to properly access your services.

Being able to ping a host does not indicate connectivity. Many firewalls, routers and even some ISPs reject ICMP (ping) packets. Likewise, even if a host responds to a ping, that doesn't indicate that services are available at that location. Instead, you should attempt to reach services at your network using our Open Port tool or a Telnet command.

Being able to ping a host does not indicate connectivity. Many firewalls, routers and even some ISPs reject ICMP (ping) packets. Likewise, even if a host responds to a ping, that doesn't indicate that services are available at that location. Instead, you should attempt to reach services at your network using our Open Port tool or a Telnet command.

You can host the mail yourself using a mail server such as Microsoft Exchange or Exim to receive and send mail for your domain without running a mail server.

By default, your ISP controls your reverse DNS records, and will usually create the necessary PTR records for you upon request. If you have a large block of static IP addresses and you would like to control them through meibu.com, please see our article for detailed instructions.

To preserve the integrity of our Custom DNS service, we do not allow transfers from our name servers to any third party. If your domain delegation includes any "foreign" name servers, the Custom DNS service will deactivate within two weeks of the change, or fail to initially activate until the extraneous name servers are removed.

If you wish to host your own primary DNS and use other companies (including DynDNS.com) as secondary providers for the domain, Secondary DNS will function if other DNS providers are listed in the delegation, though it will still refuse transfer requests to these servers.

Custom DNS supports nearly all of the top-level domains available to the ICANN root servers, includingall global top-level domains (gTLD) such as .com, .edu, .gov, .org, .net; sponsoredTLDs such as .aero, .biz, .coop, .info, .name, .pro; and nearly all of the country code TLDs (ccTLDs). You can see our full list of supported TLDs.

At this time, Custom DNS does not fully support .nl or .dk due to registry restrictions. Some customers may also have issues, please see our articles for more details.