Author
Topic: LMCE as DNS Server? (Read 3476 times)

How do I use LMCE as the nameserver for my LAN? Independent of using DynDNS so Internet hosts could find my LAN hosts by FQDNs published on the Internet, how can I just replace the /etc/hosts file on each of my LAN hosts with DNS management that's published only on my LAN?

Wouldn't you just have to setup a DNS server on your core, and then edit the DHCP config file to point your MDs/devices at it rather than the Internet DNS system (or broadband router, which often forward these requests?) Don't know how you do that on Linux in terms of the detail, but functionally it is very simple. Isn't there a dhpcd.config file? That would be where you point the clients at your core. And DNS server is a standard function of all Unix-like OSs as far as I am aware... guessing dnsd? nsd? ypd? bind?

LMCE already has named (but not bind) installed, which is a BIND 9 DNS server. I don't know what role it plays in LMCE, but probably there's a way to use either that facility already running (and perhaps configurable with an existing LMCE GUI), or to just add some configs for LAN administration. And probably add a GUI, which should also expose configuring DynDNS.

LMCE already has named (but not bind) installed, which is a BIND 9 DNS server.

read that sentence again

Quote

I don't know what role it plays in LMCE, but probably there's a way to use either that facility already running (and perhaps configurable with an existing LMCE GUI), or to just add some configs for LAN administration. And probably add a GUI, which should also expose configuring DynDNS.

there is no gui in lmce for that. Add your zone files to /etc/bind/named.conf.local

I don't know what role it plays in LMCE, but probably there's a way to use either that facility already running (and perhaps configurable with an existing LMCE GUI), or to just add some configs for LAN administration. And probably add a GUI, which should also expose configuring DynDNS.

there is no gui in lmce for that. Add your zone files to /etc/bind/named.conf.local

What does LMCE use named for by default? And is there any reason I shouldn't add at least a "zone file import" field to the LMCE Network settings form, if I get a chance?

there is no gui in lmce for that. Add your zone files to /etc/bind/named.conf.local

What does LMCE use named for by default?

as the named name suggests its used as a name server. What else?your provider's name servers are written into the file /etc/bind/named.conf.forwarders (that gets included by named.conf.options) by the script "Network_DNS.sh". That greps the servers from "/etc/resolv.conf" at line 19.

Quote

And is there any reason I shouldn't add at least a "zone file import" field to the LMCE Network settings form, if I get a chance?

From what I know linuxmce uses named to proide dns resolutions for local machines. If you look at the network config on machines on the linuxmce network they have the core listed as their name server. Which means that these machine use the core for dns lookups.From what I gather it uses dns forwarding and forwards all dns queries onto the dns servers on your isp to avoid excess network traffic.This is known as a non recursive name server.Basically the named on the core justs acts as a dns forwarder and passes the lookup to the isps name server istead of doing a full dns lookup itself.So basically it will see if it has a zone file with info on the domain itself. ie if the domain is hosed on the local name server and if not it will pass it on/

/etc/bind.new/named.conf /etc/bind.new/named.conf.options /etc/bind.new/logging.conf /etc/bind.new/rndc.conf /etc/bind.new/rndc.key /etc/bind.new/db.wright.local.zone /etc/bind.new/db.wright.local.rev /etc/dhcp3.new/dhcpd.conf /etc/resolv.conf.newyou are missing the e at the end of /etc/resolv.conf.new and again here

dcerouter_1030439:~# sudo rndc reloadWARNING: key file (/etc/bind/rndc.key) exists, but using default configuration file (/etc/bind/rndc.conf)rndc: connection to remote host closedThis may indicate that* the remote server is using an older version of the command protocol,* this host is not authorized to connect,* the clocks are not synchronized, or* the key is invalid.

System = 10.04 core only install. Using the "LMCE-1004-20120730212926289.iso"Thanks.

This action has been automatically identified as harmful, and therefore disallowed. If you believe your edit was constructive, please contact an administrator, and inform them of what you were trying to do. A brief description of the abuse rule which your action matched is: Link spamming 2

/etc/bind.new/named.conf /etc/bind.new/named.conf.options /etc/bind.new/logging.conf /etc/bind.new/rndc.conf /etc/bind.new/rndc.key /etc/bind.new/db.wright.local.zone /etc/bind.new/db.wright.local.rev /etc/dhcp3.new/dhcpd.conf /etc/resolv.conf.newyou are missing the e at the end of /etc/resolv.conf.new and again here

dcerouter_1030439:~# sudo rndc reloadWARNING: key file (/etc/bind/rndc.key) exists, but using default configuration file (/etc/bind/rndc.conf)rndc: connection to remote host closedThis may indicate that* the remote server is using an older version of the command protocol,* this host is not authorized to connect,* the clocks are not synchronized, or* the key is invalid.

System = 10.04 core only install. Using the "LMCE-1004-20120730212926289.iso"Thanks.