DNS Administration: Difference between revisions
Hippieshaker (talk | contribs) m (→Introduction) |
Hippieshaker (talk | contribs) |
||
Line 41: | Line 41: | ||
= |
= Administering DNS on Windows = |
||
To |
To administer DNS from a Windows client, you have to install the DNS MMC Snap-In. See [[Samba_AD_management_from_windows|Samba AD Management from Windows]] for more details. |
||
Line 124: | Line 124: | ||
: [[Image:DNS_Delete_Zone.png]] |
: [[Image:DNS_Delete_Zone.png]] |
||
= Administrating DNS on Linux/Unix = |
= Administrating DNS on Linux/Unix = |
Revision as of 17:04, 20 September 2013
Introduction
If you're running Samba as Active Directory Domain Controller, you also have to administer a DNS server.
You will already find general information on the internal DNS and the BIND DLZ module and documentation about Bind as DNS Backend in the Wiki.
General
Per default, Samba creates the following two forward zones during provisioning/upgrading (of course with your own domain name):
- samdom.example.com: Zone for your domain.
- _msdcs.samdom.example.com: This is the ForestDNSZone, that contains several service records for the entire directory.
Features
The Samba internal DNS is a new implementation. Even if BIND is a grown up DNS and long in production on millions of servers, the Samba BIND DLZ module is also still new. That why both backends doesn't cover all features yet, you can setup with the Microsoft DNS tools. If you discover problems or missing features, please open a bug report/feature request at https://bugzilla.samba.org/.
But even if the internal DNS and the BIND DLZ modules are new, they both support all basic requirements for Active Directory and more.
Known/issues missing features
- Managing zone transfers is not implemented yet. Bug report #9951:DNS MMC: Enabling DNS zone transfers in MMC fails
- Different zone transfer settings on internal DNS (denied) and BIND DLZ (allowed). Bug report #9634: Samba Bind DLZ module allows zone transfers for everyone
Importance of DNS for Active Directory
A working Active Directory is heavily based on a working DNS. It's not just for resolving IP addresses into names and vice versa. Clients find their Domain Controller/s and other important AD services by DNS queries.
Administering DNS on Windows
To administer DNS from a Windows client, you have to install the DNS MMC Snap-In. See Samba AD Management from Windows for more details.
Adding new records
- Navigate to the zone, where you want to to add a new record.
- Right-click to it and choose the kind of record to add.
- Fill the fields and save the new entry.
Updating existing records
- Navigate to the zone that contains the record you want to edit.
- Right-click the record and choose „Properties“.
- Edit the entry and save the changes.
Delete a record
- Navigate to the zone that contains the record you want to remove.
- Right-click to the record and choose „Delete“.
Changing zone properties
- Right-click to a zone of which you you want to do changes.
- Choose „Properties“.
Note: Currently both DNS backends doesn't support all features, that can be setup in the dialogues. If you discover problems or missing features, please open a bug report/feature request at https://bugzilla.samba.org/.
Creating a new zone
As example we'll add a reverse lookup zone.
- Right-click to „Reverse Lookup Zones“ and choose „New Zone“.
- The „New Zone Wizard“ appears.
- Zone Type: Select „Primary zone“ and „Store the zone in Active Directory“.
- Zone Replication Scope: Depents on your needs.
- Reverse Lookup Zone Name: Depents on your needs.
- Dynamic Update: Depents on your needs.
- Finish the wizard.
Your new zone is direclty live. You don't have to restart Samba/BIND.
Deleting a zone
- Right-click to a zone and choose „Delete“.
Administrating DNS on Linux/Unix
Adding new records
- Example: Adding an A record
# samba-tool dns add <Your-Server> samdom.example.com demo A 10.99.0.55 Password for [administrator@SAMDOM.EXAMPLE.COM]: Record added successfully
- Example: Adding a PTR record to a reverse zone
# samba-tool dns add <Your-Server> 0.99.10.in-addr.arpa 55 PTR demo.samdom.example.com Password for [administrator@SAMDOM.EXAMPLE.COM]: Record added successfully
- Example: Adding a SRV record to _tcp.samdom.example.com
# samba-tool dns add <Your-Server> samdom.example.com _demo._tcp SRV 'demo.samdom.example.com 8080 0 100' Password for [administrator@SAMDOM.EXAMPLE.COM]: Record added successfully
- A note on SRV records: The order of the four parameters in the last field („data“) are 'hostname port priority weight' and have to be between ' '.
Updating existing records
- Example: Changing an A record
# samba-tool dns update <Your-Server> samdom.example.com demo A 10.99.0.55 10.99.0.66 Password for [administrator@SAMDOM.EXAMPLE.COM]: Record updated succefully
Delete a record
- Example: Deleting an A record
# samba-tool dns delete <Your-Server> samdom.example.com demo A 10.99.0.55 Password for [administrator@SAMDOM.EXAMPLE.COM]: Record deleted succefully
Creating a new zone
As example we'll add a reverse lookup zone.
# samba-tool dns zonecreate <Your-Server> 0.99.10.in-addr.arpa Password for [administrator@SAMDOM.EXAMPLE.COM]: Zone 0.99.10.in-addr.arpa created successfully
Your new zone is direclty live. You don't have to restart Samba/BIND.
Deleting a zone
- Example: Deleting a reverse zone:
# samba-tool dns zonedelete <Your-Server> 0.99.10.in-addr.arpa Password for [administrator@SAMDOM.EXAMPLE.COM]: Zone 0.99.10.in-addr.arpa delete successfully
Configuring clients to use your AD DNS server
If you provide DNS server addresses via DHCP to your clients, configure your DHCP server to ship the adress/es of your DNS server/s.
For static configuration on the different Windows versions, continue reading.
Windows 8
- Press [Win]+[W] and search for „Network and Sharing Center“ in Settings and open the app.
- Click „Change adapter settings“.
- Right-click to your network adapter and choose „Properties“.
- Click to your Internet Protocol (IPv4/IPv6) and click the „Properties“ button.
- Enter the IP address/es of your DNS server/s.
- Save the settings by clicking „OK“.
Windows 7
- Click to „Start“ and search for „Network and Sharing Center“.
- Click „Change adapter settings“.
- Right-click to your network adapter and choose „Properties“.
- Click to your Internet Protocol (IPv4/IPv6) and click the „Properties“ button.
- Enter the IP address/es of your DNS server/s.
- Save the settings by clicking „OK“.
Windows XP
- Right-click to „My Network Places“ and choose „Properties“.
- Right-click to your network connection and choose „Properties“.
- Click to your Internet Protocol and click the „Properties“ button.
- Enter the IP address/es of your DNS server/s.
- Save the settings by clicking „OK“.
Linux/Unix
Edit your /etc/resolv.conf and add a „nameserver“ entry for each DNS server and your search domain:
nameserver 10.99.0.1 nameserver 10.99.0.2 search samdom.example.com
Testing your DNS Server
On Windows and *nix, you can use „nslookup“ to test if your computer can resolve records by using your DNS. Try resolving the name of your Domain Controller into its IP:
# nslookup DC1.samdom.example.com Server: 10.99.0.1 Address: 10.99.0.1#53 Name: DC1.samdom.example.com Address: 10.99.0.1
Nslookup will show you, which server was asked (10.99.0.1) and the result of your query (DC1.samdom.example.com has IP 10.99.0.1)
To query a SVR record, you have to start nslookup and set the type to „SRV“, to retrieve the values (works on Windows and *nix):
# nslookup Default Server: UnKnown Address: 10.99.0.1 > set type=SRV > _ldap._tcp.samdom.example.com. Server: UnKnown Address: 10.99.0.1 _ldap._tcp.samdom.example.com SRV service location: priority = 0 weight = 100 port = 389 svr hostname = dc1.samdom.example.com samdom.example.com nameserver = dc1.samdom.example.com dc1.samdom.example.com internet address = 10.99.0.1
If your query can't be answered, because it doesn't exist, you'll receive
** server can't find DC9.samdom.example.com: NXDOMAIN
If you query a none existing DNS server, it would result in
;; connection timed out; no servers could be reached