Copyright © 2007 by Scott Orr and the Trustees of Indiana University

Slides:



Advertisements
Similar presentations
Chapter 2 Gathering Target Information: Reconnaissance, Footprinting, and Social Engineering.
Advertisements

Web Server Administration
Web Server Administration Chapter 4 Name Resolution.
Domain Name System. DNS is a client/server protocol which provides Name to IP Address Resolution.
DNS server & Client Objectives Contents
DNS Domain name server – a server to translate IP aliases to addresses As you know, IP (internet protocol) works by providing every Internet machine with.
DNS. DNS is a network service that enables clients to resolve names to IP address and vice-versa. Allows machines to be logically grouped by domain names.
1 DNS. 2 BIND DNS –Resolve names to IP address –Resolve IP address to names (reverse DNS) BIND –Berkeley Internet Name Domain system Version 4 is still.
The Domain Name System. CeylonLinux DNS concepts using BIND 2 Hostnames IP Addresses are great for computers –IP address includes information used for.
CS335 Networking & Network Administration Wednesday, May 26, 2010.
Domain Name System (DNS) Network Information Center (NIC) : HOSTS.TXT.
The Domain Name System Unix System Administration Download PowerPoint Presentation.
MCTS Guide to Microsoft Windows Server 2008 Network Infrastructure Configuration Chapter 5 Introduction to DNS in Windows Server 2008.
1 CMPT 471 Networking II DHCP © Janice Regan,
Module 12: Domain Name System (DNS)
DNS Domain Name Service References: Wikipedia 1.
Reverse DNS. Overview Principles Creating reverse zones Setting up nameservers Reverse delegation procedures.
Domain Name Services Oakton Community College CIS 238.
Host Name Resolution. Overview Name resolution Name resolution Addressing a host Addressing a host Host names Host names Host name resolution Host name.
DNS. Introduction What is DNS? –Hierarchy or Tree –Dot used as a separator.
DNS and Active Directory Integration
DHCP server & Client Objectives Contents
DHCP. DHCP (Dynamic Host Configuration Protocol) is a network service that enables clients to obtain network settings (IP Address, Subnet Mask, Default.
New SA Training Topic 7: DNS and DHCP To implement the underlying basis for our organizations networking, we rely on two fundamental services  DNS – the.
NAME SERVICES. Names and addresses File names /etc/passwd URLS Internet domain names—dcs.qmw.ac.uk Identifiers- ROR, NFS.
1 Network Administration Module 6 Domain Name Service (DNS)
Name Resolution Domain Name System.
TELE 301 Lecture 11: DNS 1 Overview Last Lecture –Scheduled tasks and log management This Lecture –DNS Next Lecture –Address assignment (DHCP)
Chapter 7 Support infrastructure for networking DHCP, NAPT, ARP, DNS.
DNS and C# SWE 344 Internet Protocols & Client Server Programming.
Petrozavodsk State University, Alex Moschevikin, 2003NET TECHNOLOGIES Domain Name System HISTORY File hosts (the size of Internet became more than 1000.
70-291: MCSE Guide to Managing a Microsoft Windows Server 2003 Network Chapter 7: Domain Name System.
DHCP Ana Chanaba Robert Huylo. DHCP Background / Server dhcpd - Dynamic Host Configuration Protocol Server allows hosts on a TCP/IP network to request.
DHCP server & Client Objectives –to learn how to setup dhcp servers Contents –Download and Install The DHCP Package –The /etc/dhcpd.conf File –Upgrading.
CITA 310 Section 1 Name Resolution (Textbook Chapter 4)
Communication Between Networks How the Internet Got Its Name.
1 Domain Name System. 2 Resolve IP to a Name /etc/hosts  The /etc/hosts file is just a list of IP addresses and their corresponding server names.  Your.
Internet and Intranet Protocols and Applications Lecture 5 Application Protocols: DNS February 20, 2002 Joseph Conron Computer Science Department New York.
Objectives Discuss the basics of the Domain Name System (DNS) and its terminology Configure DNS clients Install a standard DNS server on Server 2008 Create.
Module 2 Zone Files. Objective Understand the idea of a zone and how it relates to a domain name understand zone file structure Understand the major Resource.
TCP/IP Administration IP addresses & Names DNS, BOOTP, DHCP, IP Routing, Routing protocols.
Configuring Name Resolution and Additional Services Lesson 12.
1 Domain Name System (DNS). 2 3 How DNS Works Application Transport Internet Network Application Transport Internet Network DNS Resolver Name Server.
1 Internet Network Services. 2 Module - Internet Network Services ♦ Overview This module focuses on configuring and customizing the servers on the network.
ECMM6018 Enterprise Networking for Electronic Commerce Tutorial 7 Dynamic Host Protocol.
DNS DNS overview DNS operation DNS zones. DNS Overview Name to IP address lookup service based on Domain Names Some DNS servers hold name and address.
CIS 192B – Lesson 2 Domain Name System. CIS 192B – Lesson 2 Types of Services Infrastructure –DHCP, DNS, NIS, AD, TIME Intranet –SSH, NFS, SAMBA Internet.
DNS server & Client Objectives –to learn how to setup dns servers Contents –An Introduction to DNS –How To Download and Install The BIND Packages –How.
Linux Operations and Administration
Sample DNS configurations. Example 1: Master 'master' DNS and is authoritative for this zone for example.com provides 'caching' services for all other.
DNS/Proxy Babu Ram Dawadi. Introduction - DNS Domain Name Server Domain Name Server –programs that store information about the domain name space –largest.
DNS - BIND9 Přednášející Vaše jméno. Master and caching name server options { directory "/var/named"; allow-transfer {“none”;}; }; zone "." { type hint;
Network Reconnaissance CS490 - Security in Computing Copyright © 2005 by Scott Orr and the Trustees of Indiana University.
Web Server Administration Chapter 4 Name Resolution.
1 CMPT 471 Networking II DNS © Janice Regan,
OPTION section It is the first section of the named.conf User can use only one option statement and many option-value pair under the section. Syntax is.
2/26/2003 Lecture 4 Computer System Administration Lecture 4 Networking Startup/DNS.
WHAT IS DNS??????????.
Juan Ortega 10/7/09 NTW342. Setting up the Configuration File ddns-update-style interim; Ignore client-updates; Subnet netmask
Domain Name System DPNM Lab. Seongho Cho
This courseware is copyrighted © 2016 gtslearning. No part of this courseware or any training material supplied by gtslearning International Limited to.
KAPLAN SCHOOL OF INFORMATION SYSTEMS AND TECHNOLOGY IT375 Window Enterprise Administration Course Name – IT Introduction to Network Security Instructor.
AfNOG-2003 Domain Name System (DNS) Ayitey Bulley Setting up an Authoritative Name Server.
Chapter 5c.  Upon completion of this chapter, you should be able to:  Configure IP addresses  Identify & select valid IP addresses for networks  Configure.
1 Internet Service DNS & BIND OPS335 Seneca College of Applied Technology.
DNS Domain name server a server to translate IP aliases to addresses
IMPLEMENTING NAME RESOLUTION USING DNS
LINUX ADMINISTRATION 1
DNS and Bind Presenter David Wood
Routing and Switching Essentials v6.0
Presentation transcript:

Copyright © 2007 by Scott Orr and the Trustees of Indiana University DNS and DHCP CSCI N321 – System and Network Administration Copyright © 2007 by Scott Orr and the Trustees of Indiana University

Section Overview DNS Overview Bind DNS Record Types DHCP

References Internet Software Consortium RedHat Deployment Guide Chapter 17 – DNS Chapter 21 – DHCP

In the beginning… Early name resolution /etc/hosts All addresses in shared file Never 100% accurate /etc/hosts IP_Addr Hostname [Aliases…] 127.0.0.1 localhost.localdomain localhost 134.68.140.203 pegasus.cs.iupui.edu pegasus

Domain Name Service (DNS) Allows for IP-Hostname translations Distributed Hierarchical Database Hostname to IP address IP Address to Hostname Root Servers (A-M) Mail Server addressing Resolver Library calls Protocol to exchange data

DNS Management Internet Corporation for Assigned Names and Numbers (ICANN) Registries ARIN – North America RIPE - Europe APNIC – Asian Pacific AfriNIC - Africa LACNIC – Latin America Domain Registrars and ISPs Authoritative DNS Servers

Whois Queries Owner Location Domain name Domain DNS Servers IP Address Block Contact Information Administrative (Tech) Abuse Noc

ISC BIND Primary DNS Server Software in use Started as a graduate student project Versions 4.x – Depreciated 8.x – Maintenance Development only 9.x – Active Development Authoritative (master & slave) Caching Recursive/Non-recursive

/etc/named.conf (Config) options { directory "/var/named"; dump-file "/var/named/data/cache_dump.db"; statistics-file "/var/named/data/named_stats.txt"; // query-source address * port 53; }; controls { inet 127.0.0.1 allow { localhost; } keys { rndckey; };

/etc/named.conf (Zones) zone "." IN { type hint; file "named.ca"; }; zone "localdomain" IN { type master; file "localdomain.zone"; allow-update { none; }; zone "localhost" IN { file "localhost.zone"; zone "0.0.127.in-addr.arpa" IN { type master; file "named.local"; allow-update { none; }; }; // CS Domain Config zone "cs.iupui.edu" { file "dns.cs.iupui.edu"; zone "140.68.134.in-addr.arpa" { file "rev.134.68.140"; include "/etc/rndc.key";

Zone Files Typically in /var/named/ Forward and reverse files Record Format [name] [ttl] [class] type data TTL – Time to keep data cached Class IN (Internet) CN (ChaosNet – No longer used) HS (Hesoid – internal database)

SOA Records Server Name Contact Name Serial (Must be increased w/ change) Refresh Secondary Retry Refresh Expire non-refreshed entries Minimum time to live

SOA Record Example @ IN SOA klingon.cs.iupui.edu. root.klingon.cs.iupui.edu. ( 2007112500 ; Serial - increase when file changes 7200 ; Refresh secondaries every 2 hours 1200 ; Retry refresh every 20 minutes 2592000 ; Expire non-refreshed entries after 30 days 7200 ) ; Minimum time-to-live is 2 hours

Name Server Records Which name servers support this domain Does not differentiate between master and slave servers Example: IN NS klingon.cs.iupui.edu. IN NS dns1.iu.edu. IN NS dns2.iu.edu.

Address (A) Records A Records – Maps hostnames to IP addresses Format Hostname IN A #.#.#.# Examples: tempest IN A 134.68.140.202 pegasus IN A 134.68.140.203 enigma IN A 134.68.140.206

Pointer (PTR) Records PTR Records – Maps IP addresses to hostnames Format # IN PTR FQDN. Examples: 202 IN PTR tempest.cs.iupui.edu. 203 IN PTR pegasus.cs.iupui.edu. 206 IN PTR enigma.cs.iupui.edu.

Conical Name (CNAME) Records Aliases for hostnames Usually associated with Services Format Alias IN CNAME Hostname Examples: imap IN CNAME tempest ns IN CNAME klingon smtp IN CNAME tempest www IN CNAME enigma webmail IN CNAME tempest

Mail Exchanger (MX) Records Special records for domain email servers Prioritization and round robin capability Format Domain. IN MX pri host Examples: cs.iupui.edu. IN MX 10 tempest cs.iupui.edu. IN MX 100 enigma

Other Record Types Service (SVC) Text (TXT) HINFO Associated with network Services Text (TXT) Notes (also SPF information) HINFO Host information (no longer used)

ISC DHCPd Provides IP addresses to client systems Static – Based on MAC Address Dynamic – Given to unknown hosts Optionally provides other Network settings Subnet Masks DNS Servers ( /etc.resolv.conf ) Default Gateway Network and Broadcast Addresses Lease times

/etc/dhcpd.conf authorative; #ddns-update-style ad-hoc; ddns-update-style none; one-lease-per-client true; host camera { hardware ethernet 00:40:8c:5b:c1:91; fixed-address 10.234.140.21; } # Block Bad MAC address host ronin { hardware ethernet 00:20:e0:67:53:68; subnet 134.68.140.0 netmask 255.255.255.0 { option domain-name "cs.iupui.edu"; option domain-name-servers 134.68.140.1 option subnet-mask 255.255.255.0; option broadcast-address 134.68.140.255; option routers 134.68.140.100; pool { range 134.68.140.101 134.68.140.199; default-lease-time 7200; max-lease-time 144000; deny known clients; }

/etc/dhcpd.leases Active Lease Entry Expired Lease Entry starts 3 2007/12/05 04:14:12; ends 3 2007/12/05 06:14:12; binding state active; next binding state free; hardware ethernet 00:13:72:da:2c:ad; uid "\001\000\023r\332,\255"; client-hostname "in-csci-16sl247"; } Expired Lease Entry lease 134.68.140.121 { starts 2 2007/12/04 22:45:28; ends 3 2007/12/05 00:45:28; tstp 3 2007/12/05 00:45:28; binding state free; hardware ethernet 00:18:8b:d9:d5:a9; uid "\001\000\030\213\331\325\251"; client-hostname "in-csci-lt1"; }