Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a VPS server that i'm running some hosting from. I have noticed for a while now that anytime I try to go to one of the websites hosted on my server the initial attempt fails; giving a server not found message in IE. The second picks the IP up real quick and loads fine. This is true for web pages and everything else that involves using a dns name thats on my server. This leads me to believe that its a DNS issue but i'm not sure what would cause this. This happens no matter what computer I try it from, and it seems to happen about once a day. Meaning once I access a site in the morning it works fine for the rest of the day. Now for some information as to my configuration:
OS: CentOS 3.5
Bind Version 9.2.4
Main server IP: xx.xx.xx.94
Secondary IP: xx.xx.xx.95
ns1.domain.com is on xx.xx.xx.94
ns2.domain.com is on xx.xx.xx.95
Main Site is on secondary IP, since it uses a SSL certificate, the rest of the sites are on the main IP.
Any clue as to what could be causing this? Any help is appriciated.
It does sound like a DNS problem. The first resolution attempt seems to be failing, and the second is second with the results then cached for the remainder of the TTL so that it does not happen again that day.
Does this happen only to you, or is this widespread? Are you using xx.xx.xx.94 and xx.xx.xx.95 as resolvers on your PC from which you experience the problems? Anything of interest in /var/log/messages?
Well I tracked it down to a screwup on my providers end. I recently ordered a SSL certificate so they moved that domain to xx.xx.xx.95 and in the process changed the DNS record for the main nameserver to the wrong IP. Once they changed it back and updated the nameservers for the domain name everything returned to normal. Nothing was showing in /var/log/messages and it was happening to all the domains on my server, as well as occuring no matter what computer I was using, which realy made me thing DNS issue.