Debian Configuration :: How To Configure A DNS / DHCP / Directory Server
Jan 17, 2016
Setup a DNS/DHCP/Directory server on Debian? I would like to configure the things in Debian so that can join Linux and Windows(if possible as m not sure yet) clients to the directory server. Any links to setup both Forward and Reverse lookup zone in the environment.
i'm trying to configure my dhcp server but without success. i've installed dhcpd apt-get install dhcpd-server then i've added the following line to my dhcpd.conf
I need to install/configure a server (dns, dhcp, etc) and since im running Debian I want to configure a Debian server, but i want to do it on a virtual machine, cause i dont want to have all that stuff on my system, now Im wondering whats the best screen recorder that i can use on Debian for this purpose.
I am puzzled with trying to configure a linux (openSUSE) client to dhcp to eBox DHCP server. I am using dhclient to lease an IP address with dhclient eth0 -s 10.45.48.108 and get a response
openSUSE11232CL1 dhclient: DHCPDISCOVER on eth0 to 10.45.48.108 port 67 interval 4 openSUSE11232CL1 dhclient: DHCPOFFER from 10.45.48.108 openSUSE11232CL1 dhclient: DHCPREQUEST on eth0 to 10.45.48.108 port 67 openSUSE11232CL1 dhclient: send_packet: Network is unreachable openSUSE11232CL1 dhclient: send_packet: please consult README file regarding broadcast address.
The server reports eBox141 dhcpd: DHCPDISCOVER from 00:0c:29:3e:57:a3 (openSUSE11232CL1.domain.net) via eth0 eBox141 dhcpd: DHCPOFFER on 10.45.200.2 to 00:0c:29:3e:57:a3 (openSUSE11232CL1.domain.net) via eth0
I interpret this as the server receives the request and the client accepting it but the lease does not last long and the connection breaks. what this could be and why the connection breaks? Or my undestanding is totally wrong on how it works and should work? And BTW, where is that README file that's referenced in the message I receive on the client?
I just put a pfSense firewall inbetween my ADSL router and my LAN. It's configured to have a cachng DNS server and a DHCP server. Among other things. For reasons beyond this post the address range served by DHCP changed from 10.0.0.x to 192.168.1.x. The new DHCP server gives 192.168.1.1 as gateway and DNS server name and not the public IP addresses of our internet provider.
After reconnecting our client machines everything worked just fine on the win-xp boxes, but the Debian Squeeze servers and Ubuntu 10.4 clients all started to get network timeouts. If I ping public websites it works but browsing to the same servers fails. Other services like POP3 and IMAP also fails. All machines use WiFi to connect and the access point is the same as before.
What could it be that make the debian boxes fail? My laptop runs squeeze too and also fails. But when connecting to various other access points at hotels and such I do not get this problem.
Another weird thing is that the debian server running virtualbox cannot do things online but the virtual windows boxes running on this machine can. Weird! Where should I start looking? How is networking/dhcp clients on Debian different from Windows XP?
I'm running gnome desktop on squeeze system. When I boot my system seems to be using my internet modem as its dhcp server. The rest of the machines on my lan are correctly using my router for that purpose. As a result, what happens then is that my debian machine frequently gets a duplicate ip address assigned to it. I would like to specify to my debian computer that I want it to use the specific fixed ip address of my router for dhcp purposes.
I wanted to setup my server as a router/gateway just for educational purposes and also when it succeeded i will keep the gateway and place it on the front line right after my modem.
My current setup as it is now :
The GATEWAY/ROUTER will be doing the main work to act as a dhcp server and firewall.
Now my setup as it is now :
So now what i ment to do was :
Let the clients connect to the gateway via ETH1 and all the stuff being router to ETH0 which is the NIC that is connected to the internet.
But now i have two huge problems :
1. The DHCP configuration seems to be fine the client machines get their ip adresses and /etc/resolve.conf looks fine to. But somehow the GATEWAY/ROUTER wont let me use the specified external DNs server so i cant do anything on these machines.
2. The firewall script [url] at line 27 should be DROP but if i use this line of code the GATEWAY/ROUTER cannot use his dns server settings so when i try to browse the internet or ping a machine outside my local network it would came up with nothing.
Alright, I edited "/etc/default/isc-dhcp-server" and set "eth0" as the only thing listed for interfaces. I also have the code below in "/etc/dhcp/dhcp3/dhcpd.conf" and I even copied it to "/etc/dhcp/dhcpd.conf" for good measure, and I can't get the DHCP server to start. As an intermediate to advanced user, I am under the high assumption that it is broken since everything in the docs has been set. I have googled for two days and cannot find a fix, so before I report it as a broken package, would somebody with more experience with the package chime in?
I hid my wireless setup because it contains my WiFi network info including key. This box is routing, doing DNS resolution, and firewalling just fine. I just cannot get the friggin' DHCP server to start no matter what I try.
Oh, and is it safe to delete "/etc/dhcp" or "/etc/dhcp3"? They appear to be duplicates of each other...
I have a home Debian server running, and i would like to set it up as a gateway. I have 2 networkcards in it. So internet comes from the modem and on the other card i want to setup a dhcp server and it has to share the internet. But i want it also to connect to a vpn and share the internet of the vpn.. Is that possible?
I will be relocating to a permanent residence sometime in the next year or two. I've recently begun thinking about the best way to implement a home-based network. It occurred to me that the most elegant solution might be the use of VM technology to eliminate as much hardware and wiring as possible.My thinking is this: Install a multi-core system and configure it to run several VMs, one each for a firewall, a caching proxy server, a mail server, a web server. Additionally, I would like to run 2-4 VMs as remote (RDP)workstations, using diskless workstations to boot the VMs over powerline ethernet.The latest powerline technology (available later this year) will allow multiple devices on a residential circuit operating at near gigabit speed, just like legacy wired networks.
In theory, the above would allow me to consolidate everything but the disklessworkstations on a single server and eliminate all wired (and wireless) connections except the broadband connection to the Internet and the cabling to the nearest power outlets. It appears technically possible, but I'm not sure about the various virtual connections among VMs. In theory, each VM should be able to communicate with the other as if it was on the same network via the server data bus, but what about setting up firewall zones? Any internal I/O bandwidth bottlenecks? Any other potential "gotchas", caveats, issues? (Other than the obvious requirement of having enough CPU and RAM).Any thoughts or observations welcome, especially if they are from real world experience in a VM environment. BTW--in case you're wondering why I'm posting here, it's because I run Debian on all my workstations/servers (running VirtualBox as a VM for Windows XP on one workstation).
I am trying to configure samba for a stripped down file server. I am running debian with command line only. My problem is that I cannot unmask samba.
See below:
root@debian:/home/aaron# service samba status ● samba.service Loaded: masked (/dev/null) Active: inactive (dead)
I have tried "sudo systemctl unmask samba.service". I receive no errors however it does not actually unmask. I can't find anything online regarding a service stuck on masked status.
I have installed RHEL 5.1 in VMWare 6 I want to configure one RHEL Server with DNS & DHCP Also I would like to PXE boot, whenever I create a new VMWare Client(RHEL), the installation should be initiated via network boot
i'd like to configure a dhcp server on my RHEL 5.3 or Fedora 14, since i don' have a legitimate DNS server....n it asks for option domain-name " "what do i put in there.. me got two nics for my WAN(dhcp enabled) n LAN...i just want to parctice at home for my future job...
This is probably an odd request, but figured I'd ask in case someone knew. We have a lab that has the IP range 172.10.0.0/16 (255.255.0.0). The lab gateway/DHCP assigns an IP in the range of 172.10.0.2-172.10.0.254. I want to set up my own DHCP server on a specific range, for example 172.10.10.1-172.10.10.254. I create a new host fine, but since it's set for DHCP, it uses the DHCP server at 172.10.0.1. Is there a way to force it to use a different DHCP server on the client side? I realize that I can work around this with exclusions on the 172.10.0.1 DHCP server, or use iptables to deny DHCP requests to specific MACs, but wanted to know if there was an (easier?) way to configure the client to use the 172.10.10.1 DHCP server instead of the 172.10.0.1 server?
I've tried to configure DRBL server to use Clonezilla and that is required me to setup DHCP, TFTP servers.But I've gotten a lot of errors from them - so please look at my attachments from /var/log/messages and dhcpd.conf - help me to find out what are wrong with them.
i already have an eth0 configured to automatically get its info from dhcp.
but i wanna configure eth1 to be able to serve dhcp and dns. i havent configured either dns or dhcp server on the server box since i have not configured the serving interface.
so far my interfaces file is:
Code: # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp
I'm looking for a way to configure DHCP client so it would dynamically set the hostname and register itself to a DNS server. I don't have access to the DNS server.
I'm trying to set up a PXE boot server on a PC running Slackware 13.0 using the default apps and info shipped with that Slackware version but to no avail...Carefully reading the Slackware 13.0 README_PXE I've put together this dhcpd.conf file:
# dhcpd.conf # # Configuration file for ISC dhcpd (see 'man dhcpd.conf')
I need to place an Ubuntu machine on a network where I have a DHCP server which does not configure the Degault Gateway parameter (we don't want ordinary users to browse the internet). Is it possible to leave the machine using DHCP and define the Default Gateway manually (as in Windows XP i.e.)? How?
I need to shear internet i use isc-dhcp-serve and it work but internet doesn't work i have triad so many commends but still networking ... My setting is eth0 - wan eth1 -local
When I stop/start vm(not restart), dhclient becomes up and ip is assigned by dhcp. Why? -------------------------------- yoshi@vbox:~$ uname -a Linux vbox 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64 GNU/Linux -------------------------------- yoshi@vbox:~$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5).
I'm trying to setup a DHCP server that serves several different VLANs, we have 5 in total. Our network is working correctly, with static IPs, we're able to ping across without any issues.
When I connect my debian box to an interface on VLAN5, statically assign an address in the correct range, it works. Similarly with all other VLANs.
To configure this box as a DHCP, I set one of the ports on the switch as trunk, connect that to the debian box to allow all VLAN traffic to reach my debian box.
I setup DHCP following the steps on [URL] ....
Then I configured different VLANs by following the steps on [URL] .....
However, with the vlans setup, I am unable to ping anything. This is essentially what I did.
Code: Select allSet the port on the switch to trunk with 802.1 encapsulation disable eth0 vconfig add eth0 5 # to add vlan 5 ifconfig eth0.5 192.168.5.254 netmask 255.255.255.0 up vconfig add eth0 5 # to add vlan 10 ifconfig eth0.5 192.168.10.254 netmask 255.255.255.0 up
[Code] ....
I do not know why I am unable to get any connectivity through my VLAN interfaces.