*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
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.
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 am hoping that someone can help me on this. I have been beating away at this for many hours.
I had my primary dns server stop answering dns requests yesterday after a power outage at it's data center. I have it co-located in Michigan and I am in Oklahoma. All the dns requests fell back onto my windows server 03 box here in OK. I decided to take one of my other co-located servers that was not doing anything anymore (also in Oklahoma) and make it the new primary dns (ns1). Long story short, I replaced the stock bind with "bind9-base-184.108.40.206" and managed to get everything functioning including rndc but it will not answer a normal dns request. I can dig it locally and from one of my other bsd boxes and it responds with the correct record. I can go to "dns stuff" site and it will respond...but if I try pinging, I can't get any domains to resolve. I try to browse to a page that it is hosting dns for and I get nowhere. I have not deeply researched dig but I am guessing that dig and the "dns stuff" site may be sending requests through tcp when the real world is sending through udp. Anyone with any ideas?
BTW. This name server is not used except as a master authorative dns server for a hand full of domains.
Nevermind. I guess that it is working. Every machine that I was trying to ping from were using my win 03 server dns box and for some reason would not foward dns requests to root. I think that the problem is resolved.