The document discusses the need for and history of the Domain Name System (DNS). It explains that DNS was created to map human-friendly domain names to IP addresses and vice versa. Originally, a single host file contained all name-IP mappings but this became infeasible as the internet grew. DNS addresses this by hierarchically dividing the name space and distributing the mappings across multiple name servers. It uses a tree structure with domains like .com, .edu at the top level and subdomains below. DNS servers are authoritative for different zones and work together to resolve queries through either recursive or iterative queries.
Learn about the essentials of the Domain Name System (DNS), including name resolution, different record types, roots, zones, authority and recursion.
See the full webinar and the rest of the series at https://www.thousandeyes.com/resources/intro-to-dns-webinar
Overview of the Domain Name System (DNS).
In the early days of the Internet, hosts had a fixed IP address.
Reaching a host required to know its numeric IP address.
With the growing number of hosts this scheme became quickly awkward and difficult to use.
DNS was introduced to give hosts human readable names that would be translated into a numeric IP addresses on the fly when a requesting host tried to reach another host.
To facilitate a distributed administration of the domain names, a hierarchic scheme was introduced where responsibility to manage domain names is delegated to organizations which can further delegate management of sub-domains.
Due to its importance in the operation of the Internet, domain name servers are usually operated redundantly. The databases of both servers are periodically synchronized.
A complete Coverage of DNS and its features. This ppt deals with well balanced practical and theoretical aspects of DNS. The best ppt for a novice learner.
Learn about the essentials of the Domain Name System (DNS), including name resolution, different record types, roots, zones, authority and recursion.
See the full webinar and the rest of the series at https://www.thousandeyes.com/resources/intro-to-dns-webinar
Overview of the Domain Name System (DNS).
In the early days of the Internet, hosts had a fixed IP address.
Reaching a host required to know its numeric IP address.
With the growing number of hosts this scheme became quickly awkward and difficult to use.
DNS was introduced to give hosts human readable names that would be translated into a numeric IP addresses on the fly when a requesting host tried to reach another host.
To facilitate a distributed administration of the domain names, a hierarchic scheme was introduced where responsibility to manage domain names is delegated to organizations which can further delegate management of sub-domains.
Due to its importance in the operation of the Internet, domain name servers are usually operated redundantly. The databases of both servers are periodically synchronized.
A complete Coverage of DNS and its features. This ppt deals with well balanced practical and theoretical aspects of DNS. The best ppt for a novice learner.
This slide contains details about domain name servers (DNS).
It also contains Resolution of the Name Servers with Domain Name Structure with statistics table. The process of Name resolution is also explained with Recursive and iterative resolution processes.
This slide contains details about domain name servers (DNS).
It also contains Resolution of the Name Servers with Domain Name Structure with statistics table. The process of Name resolution is also explained with Recursive and iterative resolution processes.
DOMAIN NAME SYSTEM AND DYNAMIC DOMAIN NAME SYSTEM
Machines on the internet are identified by a unique IP address. But it is difficult for people to remember these addresses.
Humans are more comfortable with names rather than numbers. Hence it would be easier to identify a machine using a name instead of an address.
DDNS (Dynamic Domain Name System) allows us to overcome the issues related to Dynamic IP Addresses, in attempting to connect to a DVR somewhere on the Internet whose IP Address may change at any time.
The application layer sits at Layer 7, the top of the Open Systems Interconnection (OSI) communications model. It ensures an application can effectively communicate with other applications on different computer systems and networks. The application layer is not an application.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered Quality
Domain name system
1.
2. NEED OF DNS
To identify an entity, the Internet uses the IP address,
which uniquely identifies the connection of a host to the
Internet. However, people prefer to use names instead of
addresses. Therefore, we need a system that can map a
name to an address or an address to a name.
3. HISTORY OF DNS
When the Internet was small, mapping was done using a
host file. The host file had only two columns: one for the
name and one for the address. Every host could store the
host file on its disk and update it periodically from a
master host file. When a program or user wanted to map
a name to an address, the host consulted the host file and
found the mapping.
Today, however, it is impossible to have one single host
file relate every address to a name and vice versa. The
host file would be too large to store in every host.
4. In addition, it would be impossible to update all the host
files in the world every time there is a change.
One solution would be to store the entire host file in a
single computer and allow access to this centralized
information to every computer that needs a mapping. But
this would create huge amount of traffic on the Internet.
5. INTRODUCTION
Another solution, the one used today, is to divide this
huge information into smaller parts and store each part
on a different computer. In this method, the host that
needs mapping can contact the closest computer holding
the needed information. This method is used by the
Domain Name System (DNS).
6. Design principle of DNS
The naming system on which DNS is based is a hierarchical and logical tree
structure called the domain namespace.
An organization obtains authority for parts of the name space, and can add
additional layers of the hierarchy
In practice, allocation of the domain names generally follows the allocation of IP
address, e.g.,
All hosts with network prefix 128.143/16 have domain name suffix
virginia.edu
All hosts on network 128.143.136/24 are in the Computer Science
Department of the University of Virginia
7. NAME SPACE
A name space that maps each address to a unique name
can be organized in two ways:
a. FLAT NAME SPACE
In this, a name is assigned to an address. A name in
this space is a sequence without structure.
Disadvantage: Cannot be used in large systems like
Internet because it must be centrally controlled to
avoid ambiguity and duplication.
8. b. HIERARCHIAL NAME SPACE
• Each name is made of several parts.
• The first part can define the nature of organization, the
second part can define the name, the third part can define
departments and so on.
• The authority to assign and control the name spaces can be
decentralized.
9. DOMAIN NAME SPACE
To have a hierarchical name space, Domain Name Space
was designed. In this design, the names are defined in an
inverted-tree structure with the root at the top. The tree
can have only 128 levels: level 0 (root) to level 127. Each
level of the tree defines a hierarchical level.
10. The DNS Name Space
A portion of the Internet domain name space.
11. LABEL: Each node in a tree has a label, which is a string
with a maximum of 63 characters. The root label is a null
string. DNS requires that children of a node have different
labels, which guarantees the uniqueness of the domain
names.
DOMAIN NAME: Each node in the tree has a domain
name. A full domain name is a sequence of labels
separated by dots(.). The domain names are always read
from the node upto the root.
12. Domain name system
Each node in the DNS tree represents
a DNS name
Each branch below a node is a DNS
domain.
DNS domain can contain hosts or
other domains (subdomains)
Example:
DNS domains are
., edu, virginia.edu, cs.virginia.edu
virginia.edu
cs.virginia.eduwww.virginia.edu
neon.cs.virginia.edu
edu
.
13. FULLY QUALIFIED DOMAIN NAME (FQDN):
Every node in the DNS domain tree can be identified by a unique
Fully Qualified Domain Name (FQDN). The FQDN gives the
position in the DNS tree.
In this, the label is terminated by a null string.
It is a domain name that contains the full name of the host.
It contains all labels, from the most specific to the most general,
that uniquely define the host.
PARTIALLY QUALIFIED DOMAIN NAME (PQDN)
In this, the label is not terminated by a null string.
A PQDN starts with a node but does not reach the root.
It is used when the name to be resolved belongs to the same site
as the client.
14. Top-level domains
Three types of top-level domains:
Organizational: 3-character code indicates the function of the
organization
Used primarily within the US
Examples: gov, mil, edu, org, com, net
Geographical: 2-character country or region code
Examples: us, va, jp, de
Reverse domains: A special domain (in-addr.arpa) used for IP
address-to-name mapping
There are more than 200 top-level domains.
15. Organizational top-level domains
com Commercial organizations
edu Educational institutions
gov Government institutions
int International organizations
mil U.S. military institutions
net Networking organizations
org Non-profit organizations
16. Hierarchy of name servers
The resolution of the
hierarchical name space is
done by a hierarchy of name
servers
Each server is responsible
(authoritative) for a
contiguous portion of the DNS
namespace, called a zone.
Zone is a part of the subtree
DNS server answers queries
about hosts in its zone
root server
com servergov serveredu serverorg server
uci.edu
server
.virginia.edu
server
cs.virginia.edu
server
DISTRIBUTION OF NAME SPACE
17. Authority and Delegation
Authority for the root domain is with the Internet
Corporation for Assigned Numbers and Names (ICANN)
ICANN delegates to accredited registrars (for gTLDs) and
countries for country code top level domains (ccTLDs)
Authority can be delegated further
Chain of delegation can be obtained by reading domain
name from right to left.
Unit of delegation is a “zone”.
18.
19. DNS Domains and Zones
Each zone is anchored at a
specific domain node, but
zones are not domains.
A DNS domain is a branch of
the namespace
A zone is a portion of the DNS
namespace generally stored in
a file (It could consists of
multiple nodes)
A server can divide part of its
zone and delegate it to other
servers
. (root)
.virginia.edu
.edu
.uci.edu
cs.virginia.edumath.virginia.edu
Domain
Zone
and
domain
Zone
20. Primary and Secondary Name Servers
For each zone, there must be a primary name server and a secondary
name server
The primary server (master server) maintains a zone file which has
information about the zone. Updates are made to the primary server
The secondary server copies data stored at the primary server.
Adding a host:
When a new host is added (“gold.cs.virginia.edu”) to a zone, the
administrator adds the IP information on the host (IP address and name) to
a configuration file on the primary server
21. RESOURCE RECORDS
The database records of
the distributed data base
are called resource records
(RR)
Resource records are
stored in configuration files
(zone files) at name
servers.
Left Resource records for a
zone:
db.mylab.com
$TTL 86400
mylab.com. IN SOA PC4.mylab.com.
hostmaster.mylab.com. (
1 ; serial
28800 ; refresh
7200 ; retry
604800 ; expire
86400 ; ttl
)
;
mylab.com. IN NS PC4.mylab.com.
;
localhost A 127.0.0.1
PC4.mylab.com. A 10.0.1.41
PC3.mylab.com. A 10.0.1.31
PC2.mylab.com. A 10.0.1.21
PC1.mylab.com. A 10.0.1.11
23. Resource Records
db.mylab.com
$TTL 86400
mylab.com. IN SOA PC4.mylab.com. hostmaster.mylab.com. (
1 ; serial
28800 ; refresh
7200 ; retry
604800 ; expire
86400 ; ttl
)
;
mylab.com. IN NS PC4.mylab.com.
;
localhost A 127.0.0.1
PC4.mylab.com. A 10.0.1.41
PC3.mylab.com. A 10.0.1.31
PC2.mylab.com. A 10.0.1.21
PC1.mylab.com. A 10.0.1.11
Max. age of cached data
in seconds
* Start of authority (SOA) record.
Means: “This name server is
authoritative for the zone
Mylab.com”
* PC4.mylab.com is the
name server
* hostmaster@mylab.com is the
email address of the person
in charge
Name server (NS) record.
One entry for each authoritative
name server
Address (A) records.
One entry for each hostaddress
24. Resolver and name server
1. An application program on a host
accesses the domain system through
a DNS client, called the resolver
2. Resolver contacts DNS server, called
name server
3. DNS server returns IP address to
resolver which passes the IP address
to application
Reverse lookups are also possible,
i.e., find the hostname given an IP
address
HTTP Resolver
Hostname (neon.tcpip-lab.edu)
IP address (128.143.71.21)
Name
server
Hostname
(neon.tcpip-lab.edu)
IPaddress(128.143.71.21)
25. Domain name resolution
1. User program issues a request for
the IP address of a hostname
2. Local resolver formulates a DNS
query to the name server of the host
3. Name server checks if it is
authorized to answer the query.
a) If yes, it responds.
b) Otherwise, it will query other
name servers, starting at the
root tree
4. When the name server has the
answer it sends it to the resolver.
HTTP Resolver
Hostname (neon.tcpip-lab.edu)
IP address (128.143.71.21)
Name
server
Hostname
(neon.tcpip-lab.edu)
IPaddress(128.143.71.21)
26. Recursive and Iterative Queries
There are two types of queries:
Recursive queries
Iterative (non-recursive) queries
The type of query is determined by a bit in the DNS query
Recursive query: When the name server of a host cannot
resolve a query, the server issues a query to resolve the query
Iterative queries: When the name server of a host cannot
resolve a query, it sends a referral to another server to the
resolver
27. Recursive queries
In a recursive query, the resolver
expects the response from the name
server
If the server cannot supply the
answer, it will send the query to the
“closest known” authoritative name
server (here: In the worst case, the
closest known server is the root
server)
The root sever sends a referral to the
“edu” server. Querying this server
yields a referral to the server of
“virginia.edu”
… and so on
root server
edu server
virginia.edu
server
cs.virginia.edu
server
Resolver
Name
server
query
response
Referral to edu name server
1st query: neon.cs.virginia.edu
2nd query: neon.cs.virginia.edu
Referral to virginia.edu name
server
3rd
query:
neon.cs.virginia.edu
Referral to
cs.virginia.edu
name server
4th query:
neon.cs.virginia.edu
IP address of
neon.cs.virginia.edu
28. Iterative queries
In an iterative query, the name server
sends a closest known authoritative
name server a referral to the root
server.
This involves more work for the
resolver
root server
edu server
virginia.edu
server
cs.virginia.edu
server
Resolver
Name
server
query
referraltorootserver
Referral to
edu
nam
e
server
1
st query: neon.cs.virginia.edu
2
nd query: neon.cs.virginia.edu
Referral to virginia.edu name
server
3
rd query: neon.cs.virginia.edu
Referral to cs.virginia.edu
name server
4th
query:
neon.cs.virginia.edu
IP address of
neon.cs.virginia.edu
29. Caching
To reduce DNS traffic, name servers caches information on
domain name/IP address mappings
When an entry for a query is in the cache, the server does not
contact other servers
Note: If an entry is sent from a cache, the reply from the
server is marked as “unauthoritative”