I can't resolve hosted domains

Portal Home > Knowledgebase > Articles Database > I can't resolve hosted domains

Posted by Tim G, 04-16-2008, 05:17 AM
Hi, I can't resolve hosted domains on ssh or via php on my server. All of other domains fine when i dig or ping but mine is not. I did run fix scripts for dns and restarted named but result is still same. Also, when i try to reach one of my domains via php's fsockopen function, i get "65 No route to host" or "68 Too many users" error. I haven't not much knowledge about these. I'd be glad if you can help. Thanks.
Posted by david510, 04-16-2008, 06:34 AM
What does this result from server? dig @localhost yourdomain.com What does this result from outside the server? dig yourdomain.com
Posted by Tim G, 04-16-2008, 07:03 AM
Hi, I can ping the domain a while ago but now, i can't ping again. For different domains, results are different. Like this;
Posted by david510, 04-16-2008, 07:40 AM
Nameservers are not responding from outside your server. The following are not responding. dig @NS1.WEBHOSTINGPLANET.NET zpnd.com dig @NS2.WEBHOSTINGPLANET.NET zpnd.com
Posted by Tim G, 04-16-2008, 07:51 AM
I'm using ns10 and ns11. I can't ping that too but i can reach to my sites with browser. I don't have any idea why i can't ping or why you can't dig that nameservers. If you look at ns records you can be able to see that nameservers definitions are correct. We can try if you have an idea or solution.
Posted by whmcsguru, 04-16-2008, 08:01 AM
Resolving domains from 'inside your server' rarely has anything to do with DNS configuration, but more to do with resolver configuration. The problem with resolver configuration is that most DC's set it up and then shut down the resolvers a few months later. Can this be fixed? You bet. If you have WHM/CPanel: go into WHM Find the resolver configuration link Once in resolver configuration, add the following two ip addresses And take away anything else that may be in there. Save that and you're done This will put you on the OpenDNS resolvers and things should start instantly looking better. Now, IF your resolver configuration already has your server's ip address in there, that means there's something wrong with your named configuration, or that it's refusing local connections. You shoudl verify that it actually works before modifying resolvers. To verify that named works, simply type from the command line. If that returns anything but at the last line, then you need to edit your dns configs and fix the problem. Now assuming you DON'T have whm/cpanel, you can fix your resolvers by editing /etc/resolv.conf and clearing out the entire file, leaving just these two lines That should get you started
Posted by david510, 04-16-2008, 08:30 AM
Have a check here? http://whois.domaintools.com/zpnd.com I can see the site uses the nameservers n1 and ns2. Simply "dig domain.com" from server will show result according to your resolvers only. To see actual result, dig servers from your local machine.
Posted by Tim G, 04-16-2008, 09:16 AM
Hi, I can resolve any domain, except hosted on my server. If my problem is related with resolver ip's, i can't be able to resolve external domains right ? Also i have live a lot of problem with opendns IPs. I don't want to use it if possible. I checked out named as you said and i get "server is up and running" response at last line. David, You're right, my mistake. But all of my nameservers pointed to one server. You can check here ; I can enter to a few sites on the server. And i can't enter to a few other sites on the server again. I'm going to crazy o_O Also i can ping the domains SOMETIMES inside from server, but mostly i can't. Btw, i must handle all these problems myself (with your help of course). I can't pay for an half-hour support £50. Last edited by Tim G; 04-16-2008 at 09:27 AM.
Posted by whmcsguru, 04-16-2008, 09:35 AM
Sorry, I misread the post and thread, it's early, gimme a break Most likely what things are in this specific case then is your named configurations. You need to have an admin go over your named configurations and fix them. While you can try (try) doing this yourself, through WHT help, it will get lost in the translation, and you'll be stuck waiting on someone to reply 'for free' to help you out. Find an admin, have them go over the configs. One thing that could be stopping this from working 100% is your recursion blocking. Make sure that you've allowed your local ip's to the "allow" list.
Posted by Tim G, 04-16-2008, 10:01 AM
I know, i should doing this as you said but probably this problem is not so big. If there is a way, i prefer get to learn and fix myself. Also I agree with you for paying to professionals like these jobs but £50 is a little big for me Otherwise if i stuck and if there is a trusted service with reasonable price, i can accept gladly.
Posted by david510, 04-16-2008, 10:53 AM
Open a request at the "System Management" area of wht..

Add to Favourites Print this Article