I’m also happy that I was selected as a Technical Reviewer of this book and, in a (small) way, helped in creating this awesome resource. My final copy arrived just this morning, and I can’t wait to read it (again).
You can find more info about it (as well as order your copy) here.
The other day I was “playing” with setting up Office 365 for one of our clients – they have Linux machines for their DNS servers, and BIND as their DNS solution. As this was my first encounter with configuring BIND by myself, I just wanted to share steps I’ve taken to make it work (in my lab environment) – maybe it will help someone…
DISCLAIMER: I’m not a Linux/UNIX expert! I try to figure out what I need, and then try to make this work… with the help of Internet resources (or experts), of course. There is plenty of resources on how to do this already, but I like to have things in one place if I need them again.
So, I’ve began my experiment with wondering which Linux distribution should I take. After some consulting (thanks, Ingrid ), the final choice was pretty easy – Fedora(criteria – had to be relatively easy to use (for non-Linux person like me), had to work in Hyper-V without much trouble, and there should be someone who can help if I got stuck).
After a pretty simple installation process (wizard, Next, …, Next, Finish), I’ve had my Fedora box up and running.
Now, the more complicated part – setup this box to be BIND server, and load the correct records in it, so that Office 365 can add and verify my domain.
Here are the high-level steps (I’ve used Terminal, with su rights):
1. install few packages to get things up and running:
yum-yinstall bind bind-utils bind-libs nano
2. configure the BIND (DNS) server to run at startup:
chkconfig named on
3. query the firewall rules for UDP port 53 access: