BIND DNS Server on a Local Network: Part 2
Setting up the local network
disclaimer
posted: 2020-07-17 | updated: 2020-10-27
In Part 2 we’re starting with a local area network consisting of a development web server, netbook, smartphone, and laptop all connected by a wireless router. Each device can access the Internet via the router which is connected to a broadband modem. The development server is up and running and can display development websites on the localhost (itself).
Steps to be completed in Part 2:
- Assign a static IP address to the development server
- Configure DHCP reservations for network devices
- Limit network access with MAC filtering
- Configure the ZoneAlarm Firewall on the Development Server
- Test the network configuration
All examples in this article are based on the IPv4 (Internet Protocol version 4) addresses listed below. Yours may differ.
Device | IP address | Connection Type | Assignment method |
---|---|---|---|
development server | 192.168.0.200 | Ethernet | static IP |
netbook | 192.168.0.199 | wireless | DHCP reservation |
smartphone | 192.168.0.198 | wireless | DHCP reservation |
laptop | 192.168.0.197 | wireless | DHCP reservation |
Step 1: Assign a static IP address to the development server
If the development server obtains its IP address automatically (via the router’s DHCP server) there is no guarantee that it will always be assigned the same IP address. This would require updating the development server’s IP address in Apache and BIND each time it changes. How inconvenient. The solution is to assign the development server a static IP address so we’ll always know where to find it.
-
Record the TCIP/IP Properties
When configuring a static IP address, you’ll have to enter these properties manually, so you’ll need to write them down:
- Default Gateway – the router’s IP address
- Subnet mask – a 32-bit number used to distinguish the network and host portions of an IP address
- Primary DNS Server IP address*
-
Secondary DNS Server IP address*
*These are the DNS servers used to surf the web. They may be provided by your ISP, or you may have opted to use a public DNS server.
To find the properties, from the command prompt, type:
C:\>ipconfig /all
Press Enter.
If the DNS Server IP addresses don’t show up, or they have the same IP address as the Default Gateway, log in to your router—the DNS Server IP addresses will be displayed on the Status page.
-
Select an IP address for the development server
Select an IP address for your development server that is outside of your router’s DHCP IP address range. To find your router’s DHCP IP address range:
- Log in to the router’s admin panel, click Setup, click Network Settings
-
Under the DHCP Server Settings section, find the DHCP Address Range. In this example, the IP range is 192.168.0.100 to 192.168.0.199. I’ve opted to use 192.168.0.200 as the static IP address for the development server, which is just outside of the router’s DHCP address range.
-
Assign a static IP address to the development server’s network adaptor
-
To access the network connections, at the command prompt, type:
C:\>ncpa.cpl
Press Enter.
-
Double click the network connection you would like to edit
-
In the Local Area Connection Status dialog box, click the Properties button
-
Select Internet Protocol Version 4 (TCP/IPv4), click the Properties button
If you are currently obtaining your development server’s IP and DNS server address automatically, your Internet Protocol (TCP/IP) Properties will look like this:
-
Click the Use the following IP address radio button. This will automatically select Use the following DNS server addresses as well. When assigning a static IP address to a network interface, it will no longer obtain DNS server IPs automatically from the router, they must be manually entered—thank goodness you wrote them down.
-
Enter the following:
Web Server Static IP Settings IP address: 192.168.0.200 (web server static IP) Subnet mask: 255.255.255.0 Default gateway: 192.168.0.1 (router IP) Preferred DNS Server: 84.200.69.80 Alternate DNS Server: 84.200.70.40 Click OK, click Close twice, and close the Network Connections dialog box. Now the development server has the static IP address, 192.168.0.200.
-
No comments yet…