Hi All,
I should have considered this beforehand... Assumed the info would be
in the Wiki somewhere. Cannot find.
The way our LAN has been working is clients use DHCP, but all address
assignments are static. Thus, when a given PC asks "what's my
address?", the DHCP server looks at the MAC address and asks the
configured resolver what is the IP address for the hostname for that
MAC address.
E.g.:
subnet 192.168.0.0 netmask 255.255.255.0 {
group {
server-name "deepthought.example.com";
option domain-name-servers 192.168.0.2;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option routers 192.168.0.1;
option netbios-name-servers 192.168.0.2;
option netbios-node-type 2;
host somepc.example.com {
hardware ethernet 0a:1b:2c:3d:4e:5f;
fixed-address somepc.example.com;
}
}
}
And the zone file on deepthought might read something like...
somepc IN A 192.168.0.10
In this manner: We always know who's who, and we don't have employees
throwing random things on the LAN and getting addresses.
Problem with the AD DC is that it lives in a sub-domain,
"addc.example.com", and the zone for that sub-domain is a dlz. So...
how do I set/assign client PCs' IP addresses?
Thanks,
Jim
--
Note: My mail server employs *very* aggressive anti-spam
filtering. If you reply to this email and your email is
rejected, please accept my apologies and let me know via my
web form at <http://jimsun.LinxNet.com/contact/scform.php>.
On 09/08/2015 09:04 AM, Jim Seymour wrote:> Hi All, > > I should have considered this beforehand... Assumed the info would be > in the Wiki somewhere. Cannot find. > > The way our LAN has been working is clients use DHCP, but all address > assignments are static. Thus, when a given PC asks "what's my > address?", the DHCP server looks at the MAC address and asks the > configured resolver what is the IP address for the hostname for that > MAC address. > > E.g.: > > subnet 192.168.0.0 netmask 255.255.255.0 { > > group { > server-name "deepthought.example.com"; > option domain-name-servers 192.168.0.2; > option subnet-mask 255.255.255.0; > option broadcast-address 192.168.0.255; > > option routers 192.168.0.1; > > option netbios-name-servers 192.168.0.2; > option netbios-node-type 2; > > host somepc.example.com { > hardware ethernet 0a:1b:2c:3d:4e:5f; > fixed-address somepc.example.com; > } > } > } > > > And the zone file on deepthought might read something like... > > somepc IN A 192.168.0.10 > > In this manner: We always know who's who, and we don't have employees > throwing random things on the LAN and getting addresses. > > Problem with the AD DC is that it lives in a sub-domain, > "addc.example.com", and the zone for that sub-domain is a dlz. So... > how do I set/assign client PCs' IP addresses?See my recent thoughts on this. With static IP address mapping in DHCP, you can extend it to static zone files. But, what about all the other dynamic stuff? all the srv records you see in: /var/lib/samba/private/dns_update_list MS decided to lean heavily on standard services; pushing them a bit at the time. In many regards we should be thankful for that as there was less to do and it was easier to figure out what they were up to.
On Tue, 8 Sep 2015 09:19:22 -0400 Robert Moskowitz <rgm at htt-consult.com> wrote:> > On 09/08/2015 09:04 AM, Jim Seymour wrote: >[snip]> > > > And the zone file on deepthought might read something like... > > > > somepc IN A 192.168.0.10[snip]> > Problem with the AD DC is that it lives in a sub-domain, > > "addc.example.com", and the zone for that sub-domain is a dlz. So... > > how do I set/assign client PCs' IP addresses? > > See my recent thoughts on this.Which ones? You've had a lot of thoughts, recently :)> With static IP address mapping in > DHCP, you can extend it to static zone files.[snip] Er... what? All I want to do is add (and remove) forward and reverse records to the DLZ zones in which the AD DC and its clients reside. I think I found it (dunno why I did not, in the first place): https://wiki.samba.org/index.php/DNS_Administration So, for the example I gave, above: samba-tool dns add deepthought.addc.example.com addc.example.com somepc A 192.168.0.10 and... samba-tool dns add deepthought.addc.example.com 0.168.192.in-addr.arpa 10 PTR somepc.addc.example.com (N.B.: "deepthought.example.com" will also work, for the first parameter to the "add"s, above, in my case, as deepthought.example.com and deepthought.addc.example.com are the same thing, in my case.) Regards, Jim -- Note: My mail server employs *very* aggressive anti-spam filtering. If you reply to this email and your email is rejected, please accept my apologies and let me know via my web form at <http://jimsun.LinxNet.com/contact/scform.php>.
On Tue, 8 Sep 2015, Jim Seymour wrote:> I should have considered this beforehand... Assumed the info would be > in the Wiki somewhere. Cannot find.[snip]> Problem with the AD DC is that it lives in a sub-domain, > "addc.example.com", and the zone for that sub-domain is a dlz. So... > how do I set/assign client PCs' IP addresses?It's here: https://wiki.samba.org/index.php/DNS_administration But basically, all you have to do is (on your DC): samba-tool dns add <yourDC> addc.example.com <hostname> A <hostaddress>
On 09/08/2015 10:25 AM, Sketch wrote:> On Tue, 8 Sep 2015, Jim Seymour wrote: > >> I should have considered this beforehand... Assumed the info would be >> in the Wiki somewhere. Cannot find. > [snip] >> Problem with the AD DC is that it lives in a sub-domain, >> "addc.example.com", and the zone for that sub-domain is a dlz. So... >> how do I set/assign client PCs' IP addresses? > > It's here: > > https://wiki.samba.org/index.php/DNS_administration > > But basically, all you have to do is (on your DC): > > samba-tool dns add <yourDC> addc.example.com <hostname> A <hostaddress> >Or CNAME, MX, etc.