Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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've set an FQDN for an IP address using BIND like suzie.example.com, but I feel that suzie.example.com is too long. I think that it's better if I can set a single word like suzie to be an FQDN. Thanks for helping.
Thanks for helping me. I've tried the link you show me, but I can't make it worked. If I omitted the zone name in named.conf, named fails to start. If I use $ORIGIN example.com., IN NS suzie, and suzie IN A 192.168.1.2., nothing's happen. host suzie.example.com, I get "suzie.example.com has address 192.168.1.2." and host suzie, I get"Host suzie not found:3 (NXDOMAIN)". Actually, I am new in computer thing. Can you help me any further?
When you change the entries in the zone file, you need to increase the value of the number in the 'serial' field, usually by '1', so that bind/DNS knows it needs to re-broadcast that info to all systems.
That can take a little while. I think (?) if you reboot DNS on that system after you've fixed the file (ie set the recs correctly, increment the serial), that will force a re-broadcast.
See section '16.3.3. Example Zone File' in that doc I linked to.
Actually, prob a good idea if you post your file here.
@ IN SOA suzie.example.com. root.example.com. (
2008102435 ; serial
28800 ; refresh
7200 ; retry
604800 ; expire
86400 ) ; minimum TTL of 1 day
IN NS suzie.example.com.
IN MX 10 mail.example.com.
suzie IN A 192.168.1.2
mail IN A 192.168.1.2
I've tried to add $ORIGIN example.com., change every suzie.example.com. to suzie., add serial number by one, and restart named. I've tried to do the same in 1.168.192.in-addr.arpa.zone. But nothing happened.
I've tried to add suzie IN CNAME suzie.example.com, too. But named failed to start.
Please help me.