I just read an article about Google providing public DNS servers for everyone to use. I thought, "why?" There are enough ways to provide DNS resolution, and most ISPs provide pretty good DNS service, so why would any corporation or individual need the services of Google for DNS resolution?
I still haven't answered that.
Anyway, I looked in to starting up my own internal DNS server and went looking on the boards to see how I might go about it. I was presented with a problem that most people on those boards experienced - I didn't have enough experience and didn't know what I was doing. I noticed that folks on the only site I looked on were having trouble with the little example there, and directly asked for help.
I'm not so interested anymore and I don't have the time (or the server), but if I did I wouldn't subscribe to a single post, follow examples, and ask for help directly. Some of the comments lead me to believe that the folks asking questions actually work in the IT field and can't go somewhere else to find what they need to do their job. I would recommend the following for you if you are the type of person who asks for help on free examples:
Find another example. Plenty of times I find that some dude's code is crap and another site has better examples to follow. Viewing other sources and hacking away with more information is much better than waiting for someone to answer a question about something they wrote over a year ago.
Read about the technology. If you want to set up a specific service, be it DNS, Secure FTP, CVS, or whatever, take a minute to read about the technology itself - are there standards you can learn about? Protocols? Specific requirements? If you can find out how something works, it will be easier to configure a server to do it because then you'll know what all that extra stuff in the .conf file is, and you might actually remember some of the settings if you need to change something later.
Go to the source. If it's a service on Ubuntu, there is definitely some documentation on it. In that documentation you can find out a lot of configuration information, syntax, and security practices for the service that you might not find out on Bob's FTP tutorial.
Help yourself, people. I'm glad I don't write tutorials.
No comments:
Post a Comment