The DNS is an internet service that converts domain names to IP addresses and vice versa. It was implemented to deal with the task of translating domain names to IP addresses for any computer on the internet. When a user enters a domain name, a recursive query is made to root name servers, TLD name servers, and authoritative name servers to ultimately return the IP address associated with that domain name. DNS uses a distributed database across servers with different roles like master, slave, caching, and forwarding servers.
The document discusses DNS (Domain Name System) servers and how they work. It explains that DNS servers translate human-readable domain names to machine-readable IP addresses in 7 steps: 1) A request is made, 2) recursive DNS servers are queried, 3) root nameservers are queried, 4) TLD nameservers are queried, 5) authoritative nameservers are queried, 6) the IP address record is retrieved, and 7) the answer is received. DNS servers act like a phone book to lookup domain names and allow the internet to function by linking names to IP addresses.
The document provides an overview of the Domain Name System (DNS). It discusses how DNS was developed to solve problems with the early HOSTS.TXT file system for mapping names to IP addresses. DNS implements a distributed database hierarchy with name servers, resolvers, and a namespace to translate between hostnames and IP addresses. The document outlines the components of DNS and how the domain name resolution process works by querying multiple name servers in a recursive manner to ultimately return an IP address.
The DNS name space is based on a domains, which exist in a hierarchical structure much like the directory tree in a file system.
A domain is the equivalent of a directory, in that it can contain either subdomains (subdirectories) or hosts (files), forming a structure called DNS tree.
The DNS name space function in the same way : administrators are assigned domain names and are then responsible for specifying host names to systems within that domain.
The result is that every computer on the Internet is uniquely identifiable by a DNS, name that consists of host name plus the names of all its parent domains, stretching up to the root of the DNS tree, separated by periods.
Each of the names between the periods can be up to 63 characters long, with a total length of 255 characters for a complete DNS name.
Domain and host names are not case sensitive, and can take any value except the null value.
The document provides an overview of the Domain Name System (DNS). It discusses how DNS works to translate domain names to IP addresses by using a distributed database across multiple server types. DNS implements a hierarchical namespace and resolves domain names through cooperation between local name servers and authoritative name servers. It allows internet resources to be accessed through easy to remember domain names instead of hard to remember IP addresses.
Domain Name System (DNS) is a hierarchical distributed database that contains mappings of domain names to IP addresses. DNS allows easy to remember domain names to be used instead of hard to remember IP addresses. It works by matching domain names to IP addresses through a lookup process involving root servers, top-level domain servers and authoritative name servers. This allows computers all over the world to communicate with each other using domain names.
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.
The document discusses Domain Name System (DNS) servers and how they work. It provides information on:
1) DNS servers translate domain names to IP addresses so computers can locate systems on the internet. The DNS database hierarchy includes root servers, TLD servers, and authoritative name servers.
2) DNS uses a distributed database and client-server model. Root servers point to TLD servers, which point to authoritative servers that maintain records for domains.
3) DNS configuration files include named.conf, resolv.conf, zone files, and include files that define DNS settings and mappings.
The document discusses DNS (Domain Name System) servers and how they work. It explains that DNS servers translate human-readable domain names to machine-readable IP addresses in 7 steps: 1) A request is made, 2) recursive DNS servers are queried, 3) root nameservers are queried, 4) TLD nameservers are queried, 5) authoritative nameservers are queried, 6) the IP address record is retrieved, and 7) the answer is received. DNS servers act like a phone book to lookup domain names and allow the internet to function by linking names to IP addresses.
The document provides an overview of the Domain Name System (DNS). It discusses how DNS was developed to solve problems with the early HOSTS.TXT file system for mapping names to IP addresses. DNS implements a distributed database hierarchy with name servers, resolvers, and a namespace to translate between hostnames and IP addresses. The document outlines the components of DNS and how the domain name resolution process works by querying multiple name servers in a recursive manner to ultimately return an IP address.
The DNS name space is based on a domains, which exist in a hierarchical structure much like the directory tree in a file system.
A domain is the equivalent of a directory, in that it can contain either subdomains (subdirectories) or hosts (files), forming a structure called DNS tree.
The DNS name space function in the same way : administrators are assigned domain names and are then responsible for specifying host names to systems within that domain.
The result is that every computer on the Internet is uniquely identifiable by a DNS, name that consists of host name plus the names of all its parent domains, stretching up to the root of the DNS tree, separated by periods.
Each of the names between the periods can be up to 63 characters long, with a total length of 255 characters for a complete DNS name.
Domain and host names are not case sensitive, and can take any value except the null value.
The document provides an overview of the Domain Name System (DNS). It discusses how DNS works to translate domain names to IP addresses by using a distributed database across multiple server types. DNS implements a hierarchical namespace and resolves domain names through cooperation between local name servers and authoritative name servers. It allows internet resources to be accessed through easy to remember domain names instead of hard to remember IP addresses.
Domain Name System (DNS) is a hierarchical distributed database that contains mappings of domain names to IP addresses. DNS allows easy to remember domain names to be used instead of hard to remember IP addresses. It works by matching domain names to IP addresses through a lookup process involving root servers, top-level domain servers and authoritative name servers. This allows computers all over the world to communicate with each other using domain names.
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.
The document discusses Domain Name System (DNS) servers and how they work. It provides information on:
1) DNS servers translate domain names to IP addresses so computers can locate systems on the internet. The DNS database hierarchy includes root servers, TLD servers, and authoritative name servers.
2) DNS uses a distributed database and client-server model. Root servers point to TLD servers, which point to authoritative servers that maintain records for domains.
3) DNS configuration files include named.conf, resolv.conf, zone files, and include files that define DNS settings and mappings.
The document provides an overview of the application layer and several key protocols and concepts:
- It describes the Domain Name System (DNS) and its role in mapping domain names to IP addresses through a distributed database and hierarchy of name servers. The registration process for obtaining domain names is also outlined.
- Resource records are discussed as the basic units of information in the DNS database, with examples given of common record types like A, CNAME, NS, and PTR.
- Name servers are defined as root servers, top-level domain servers, and authoritative servers that host parts of the domain name hierarchy.
- The concepts of zones, which are areas of responsibility for individual name servers, and iterative and
The document discusses how the Domain Name System (DNS) works by translating domain names to IP addresses. It involves the following steps:
1) A user enters a domain name in their browser. Their computer first checks its local DNS cache for the IP address.
2) If not found locally, the computer queries a recursive DNS server, typically provided by the user's Internet Service Provider.
3) If the recursive DNS server doesn't have the IP address, it queries the root name servers which direct the query to the authoritative name servers for the top-level domain (e.g. .com, .org).
4) The authoritative name servers for the specific domain (e.g. ut
The document provides information about DNS (Domain Name System) including how it works and how to configure a DNS server in Windows Server 2012. It discusses:
- DNS resolves human-readable domain names to machine-readable IP addresses and other information.
- It works through a series of steps where the DNS server is queried to retrieve the IP address associated with a domain name.
- Configuring a DNS server in Windows Server 2012 involves installing the DNS server role, then using the DNS Manager to configure zones, dynamic updates, and forwarders.
The document discusses DNS (Domain Name System) which is a naming system that translates domain names to IP addresses. It explains that DNS servers map domain names that people use, like "example.com", to the corresponding IP addresses that computers use to locate websites. DNS is necessary because computers communicate using IP addresses, not domain names. The document provides details on how DNS works, the different types of DNS servers involved in lookups, and concepts like DNS caching and DNS resolution.
This document discusses domain name system (DNS) configuration and troubleshooting. It describes DNS components like name servers, domains, and zones. It provides instructions for configuring DNS in Linux and Windows, including setting up primary and secondary servers with zone files. Troubleshooting tools like ping, nslookup, and dig are also covered.
The Domain Name System (DNS) is a hierarchical naming system that translates human-readable domain names to machine-readable IP addresses. When a user enters a domain name, the browser sends a DNS query to local resolving servers, which don't have the requested address but know the locations of root servers. The root servers help locate authoritative name servers that can provide the exact IP address corresponding to the requested domain name. This IP address is then returned to the resolving server, cached, and passed back to the browser so it can access the intended website.
Domain names are used to identify Internet resources and are translated to IP addresses by the Domain Name System (DNS). DNS operates via a hierarchical namespace with top-level domains like .com and country-specific TLDs. DNS servers store records like A records mapping domain names to IP addresses and MX records directing email. When a user accesses a website, their DNS client and local DNS server work through the DNS hierarchy to resolve the domain name to an IP address and load the webpage.
The document discusses name resolution services including NIS, DNS, and how they work together. NIS is a local name service, while DNS is global and hierarchical. It describes the components and configuration of DNS, including root, top-level, and subordinate domains as well as master, slave and caching nameservers. The document then provides an example of the name resolution process between a client, local nameserver, and external domain.
This document provides an overview of the Domain Name System (DNS) including: the hierarchical namespace structure with top-level and second-level domains; how domain names are registered; how DNS works through name servers and caching; the BIND software; DNS database and zone files; and common DNS tools like dig and host.
The document provides step-by-step instructions for configuring a master DNS server on Linux. It discusses installing bind packages, configuring the named.conf and zones files to define domains and records, creating zone files for forward and reverse lookups, restarting services, and testing the name resolution. Key aspects covered include defining the master server IP, domains and records in the zones file, generating zone files from templates, configuring firewall rules and resolving configuration.
DNS is a globally distributed database that translates domain names to IP addresses. It consists of a name space organized in a hierarchical tree structure, servers that store data about parts of the name space, and resolvers that query servers to map names to addresses. The resolution process involves recursively querying servers at higher levels, like root and TLD servers, until reaching an authoritative name server that can provide the address. Caching improves performance by storing previous lookups.
This document discusses DNS (Domain Name System) and how it relates to censorship. It notes that DNS is commonly targeted by censors because it lacks cryptographic integrity, DNSSEC is not widely implemented, and cached DNS data can persist. It describes how censors can block DNS names by pressuring domain name registrars or Internet service providers to change DNS records, effectively blocking access to certain websites indefinitely.
About DNS name service.
If you looking for Domain Name Registar, check out the review: https://medium.com/@JohnBeardslee/best-domain-name-registrars-top-recommendations-b3d65128b46a
The document discusses the Domain Name System (DNS), which maps human-readable domain names to IP addresses. DNS uses a hierarchical, domain-based naming scheme stored in a distributed database across multiple name servers. When a domain name is queried, DNS performs a recursive lookup by querying name servers at higher levels until it reaches an authoritative name server that can provide the IP address associated with the domain name. Caching of responses improves performance by avoiding unnecessary lookups.
This document provides an overview of the Domain Name System (DNS) and discusses some of its security and censorship implications. It begins with an introduction to DNS basics like its hierarchical structure and mapping of domain names to IP addresses. It then covers security issues such as DNS spoofing, cache poisoning, and reflection attacks. The document also discusses how DNS is used for censorship through blocking domain name resolutions or injecting false DNS responses. Overall, the document provides a high-level tour of the DNS system and some of the ways it can be exploited or manipulated for malicious purposes.
The Domain Name System (DNS) provides translation between human-readable domain names and machine-readable IP addresses. DNS works like a phone book, allowing users to look up IP addresses using easier to remember domain names. DNS has a hierarchical structure with top-level domains at the root and subordinate domains below. DNS servers store and serve DNS records to resolve domain names to IP addresses through either iterative or recursive queries. Authoritative DNS servers maintain definitive records for their registered domains.
The document discusses the Domain Name System (DNS) and its components. It explains what DNS is, how it works to translate domain names to IP addresses, the different record types used in DNS like A, NS, MX records. It describes DNS name servers, resolvers, zones and namespaces. It provides examples of DNS configuration files for both master and slave name servers as well as sample zone files mapping names to IP addresses.
The document discusses Internet domain names and the Domain Name System (DNS). It explains that domain names have a hierarchical tree structure with top-level domains like .com and country-specific domains like .uk. DNS servers convert domain names to IP addresses, allowing communication between devices on the Internet. The DNS hierarchy is managed by organizations like ICANN and domain name registries to coordinate a globally unique addressing system.
The document discusses the Domain Name System (DNS) and how it works. It covers DNS zones, forward and reverse lookups, forwarding, and delegation. DNS associates domain names with IP addresses and other information to direct internet traffic. It functions like a phone book to translate human-readable names to computer-readable IP addresses. DNS is hierarchical, with the domain name space divided into zones served by authoritative nameservers.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
A Comprehensive Guide to DeFi Development Services in 2024Intelisync
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
The document provides an overview of the application layer and several key protocols and concepts:
- It describes the Domain Name System (DNS) and its role in mapping domain names to IP addresses through a distributed database and hierarchy of name servers. The registration process for obtaining domain names is also outlined.
- Resource records are discussed as the basic units of information in the DNS database, with examples given of common record types like A, CNAME, NS, and PTR.
- Name servers are defined as root servers, top-level domain servers, and authoritative servers that host parts of the domain name hierarchy.
- The concepts of zones, which are areas of responsibility for individual name servers, and iterative and
The document discusses how the Domain Name System (DNS) works by translating domain names to IP addresses. It involves the following steps:
1) A user enters a domain name in their browser. Their computer first checks its local DNS cache for the IP address.
2) If not found locally, the computer queries a recursive DNS server, typically provided by the user's Internet Service Provider.
3) If the recursive DNS server doesn't have the IP address, it queries the root name servers which direct the query to the authoritative name servers for the top-level domain (e.g. .com, .org).
4) The authoritative name servers for the specific domain (e.g. ut
The document provides information about DNS (Domain Name System) including how it works and how to configure a DNS server in Windows Server 2012. It discusses:
- DNS resolves human-readable domain names to machine-readable IP addresses and other information.
- It works through a series of steps where the DNS server is queried to retrieve the IP address associated with a domain name.
- Configuring a DNS server in Windows Server 2012 involves installing the DNS server role, then using the DNS Manager to configure zones, dynamic updates, and forwarders.
The document discusses DNS (Domain Name System) which is a naming system that translates domain names to IP addresses. It explains that DNS servers map domain names that people use, like "example.com", to the corresponding IP addresses that computers use to locate websites. DNS is necessary because computers communicate using IP addresses, not domain names. The document provides details on how DNS works, the different types of DNS servers involved in lookups, and concepts like DNS caching and DNS resolution.
This document discusses domain name system (DNS) configuration and troubleshooting. It describes DNS components like name servers, domains, and zones. It provides instructions for configuring DNS in Linux and Windows, including setting up primary and secondary servers with zone files. Troubleshooting tools like ping, nslookup, and dig are also covered.
The Domain Name System (DNS) is a hierarchical naming system that translates human-readable domain names to machine-readable IP addresses. When a user enters a domain name, the browser sends a DNS query to local resolving servers, which don't have the requested address but know the locations of root servers. The root servers help locate authoritative name servers that can provide the exact IP address corresponding to the requested domain name. This IP address is then returned to the resolving server, cached, and passed back to the browser so it can access the intended website.
Domain names are used to identify Internet resources and are translated to IP addresses by the Domain Name System (DNS). DNS operates via a hierarchical namespace with top-level domains like .com and country-specific TLDs. DNS servers store records like A records mapping domain names to IP addresses and MX records directing email. When a user accesses a website, their DNS client and local DNS server work through the DNS hierarchy to resolve the domain name to an IP address and load the webpage.
The document discusses name resolution services including NIS, DNS, and how they work together. NIS is a local name service, while DNS is global and hierarchical. It describes the components and configuration of DNS, including root, top-level, and subordinate domains as well as master, slave and caching nameservers. The document then provides an example of the name resolution process between a client, local nameserver, and external domain.
This document provides an overview of the Domain Name System (DNS) including: the hierarchical namespace structure with top-level and second-level domains; how domain names are registered; how DNS works through name servers and caching; the BIND software; DNS database and zone files; and common DNS tools like dig and host.
The document provides step-by-step instructions for configuring a master DNS server on Linux. It discusses installing bind packages, configuring the named.conf and zones files to define domains and records, creating zone files for forward and reverse lookups, restarting services, and testing the name resolution. Key aspects covered include defining the master server IP, domains and records in the zones file, generating zone files from templates, configuring firewall rules and resolving configuration.
DNS is a globally distributed database that translates domain names to IP addresses. It consists of a name space organized in a hierarchical tree structure, servers that store data about parts of the name space, and resolvers that query servers to map names to addresses. The resolution process involves recursively querying servers at higher levels, like root and TLD servers, until reaching an authoritative name server that can provide the address. Caching improves performance by storing previous lookups.
This document discusses DNS (Domain Name System) and how it relates to censorship. It notes that DNS is commonly targeted by censors because it lacks cryptographic integrity, DNSSEC is not widely implemented, and cached DNS data can persist. It describes how censors can block DNS names by pressuring domain name registrars or Internet service providers to change DNS records, effectively blocking access to certain websites indefinitely.
About DNS name service.
If you looking for Domain Name Registar, check out the review: https://medium.com/@JohnBeardslee/best-domain-name-registrars-top-recommendations-b3d65128b46a
The document discusses the Domain Name System (DNS), which maps human-readable domain names to IP addresses. DNS uses a hierarchical, domain-based naming scheme stored in a distributed database across multiple name servers. When a domain name is queried, DNS performs a recursive lookup by querying name servers at higher levels until it reaches an authoritative name server that can provide the IP address associated with the domain name. Caching of responses improves performance by avoiding unnecessary lookups.
This document provides an overview of the Domain Name System (DNS) and discusses some of its security and censorship implications. It begins with an introduction to DNS basics like its hierarchical structure and mapping of domain names to IP addresses. It then covers security issues such as DNS spoofing, cache poisoning, and reflection attacks. The document also discusses how DNS is used for censorship through blocking domain name resolutions or injecting false DNS responses. Overall, the document provides a high-level tour of the DNS system and some of the ways it can be exploited or manipulated for malicious purposes.
The Domain Name System (DNS) provides translation between human-readable domain names and machine-readable IP addresses. DNS works like a phone book, allowing users to look up IP addresses using easier to remember domain names. DNS has a hierarchical structure with top-level domains at the root and subordinate domains below. DNS servers store and serve DNS records to resolve domain names to IP addresses through either iterative or recursive queries. Authoritative DNS servers maintain definitive records for their registered domains.
The document discusses the Domain Name System (DNS) and its components. It explains what DNS is, how it works to translate domain names to IP addresses, the different record types used in DNS like A, NS, MX records. It describes DNS name servers, resolvers, zones and namespaces. It provides examples of DNS configuration files for both master and slave name servers as well as sample zone files mapping names to IP addresses.
The document discusses Internet domain names and the Domain Name System (DNS). It explains that domain names have a hierarchical tree structure with top-level domains like .com and country-specific domains like .uk. DNS servers convert domain names to IP addresses, allowing communication between devices on the Internet. The DNS hierarchy is managed by organizations like ICANN and domain name registries to coordinate a globally unique addressing system.
The document discusses the Domain Name System (DNS) and how it works. It covers DNS zones, forward and reverse lookups, forwarding, and delegation. DNS associates domain names with IP addresses and other information to direct internet traffic. It functions like a phone book to translate human-readable names to computer-readable IP addresses. DNS is hierarchical, with the domain name space divided into zones served by authoritative nameservers.
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
A Comprehensive Guide to DeFi Development Services in 2024Intelisync
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
2. The Domain Name Service (DNS) is an internet service that converts
domain names into their corresponding IP Addresses and vice versa.
Any computer on the internet can maintain a file that manually associates
IP addresses with domain names. On Linux and Unix systems, this file is
called the /etc/hosts file. Here you can enter the IP Addresses and domain
names of computer you commonly access.
Using this method, however each computer needs a complete listing of all
others computers on the Internet, and this listing must be updated
constantly.
The DNS has been implemented to deal with the task of translating the
domain name of any computer on the Internet to its IP Address.
Shikhar Verma
4. User at rabbit.mytrek.com wants to connect to lizard.mytrek.com, so it will
query to the respective dns server and dns server looks up the name
lizard.mytrek.com and find its IP Address 192.168.0.3
Using the IP address for lizard.mytrek.com, the user at rabbit.mytrek.com
can now connect to that host.
Communication between two systems is happens with IP Address only.
When a user wants to access remote host, it enters its fully qualified
domain name to access a remote host, a resolver program queries the
local network’s DNS Server to provide the IP Address of a remote host.
With the IP address the user can then access the remote host.
Shikhar Verma
5. The Domain Name System of the Internet
The domain name system of the internet works in a inverted tree structure.At the top of the
tree is the root name server.The root server is followed by TLD's or Top Level Domains,and
then TLD's are followed by SLD's or Second Level Domains. All of these are seperated by
dots.
The root server is represented by a .(a dot).
TLD's are split into two types as follows.
Shikhar Verma
6. o TLD’s (Top Level Domain) are split into two types as follows.
Shikhar Verma
7. o Generic Top Level Domains(gTLD's) are TLD's like .com,.net,.org,.edu etc.
o Country Code Top Level Domains are domains such as .in,.us,.uk etc.
o Now when we call www.example.in a domain name, this domain name is a combination
of gTLD,SLD(Secondry Level Domain) and the host name. We will come back to this in
some time.
o When we normally call a domain like google.com its the combination of TLD,SLD.
Shikhar Verma
9. o Each and every node in this Domain Name system is assigned to an authority or
organization for its administration. And that organization resposible for a particular node
is authoritative for that node.The term authoritative will be used many times in DNS
system.
o It is very much important to understand the fact that, the left most part (www) in any
address, like for example www.example.in, is the hostname. WWW is used by websites
only by convention, there is no rule to use www for a website. A web site can also be
named xyz.example.com.
Shikhar Verma
10. o what happens when I type www.example.com in the address bar of the
browser?
The root name server(.) is the most important resource in the name server hierarchy. when
any name server is asked for an information which it does not have, the first thing that
name server does is asking one of the (.)root name server.
there are 13 root name servers as follows.
a.root-servers.net.
b.root-servers.net.
c.root-servers.net.
d.root-servers.net.
e.root-servers.net.
f.root-servers.net.
g.root-servers.net.
h.root-servers.net.
i.root-servers.net.
j.root-servers.net.
k.root-servers.net.
l.root-servers.net.
m.root-servers.net. Shikhar Verma
11. o what happens when I type www.example.com in the address bar of the
browser?
Now the ip address of all the root servers mentioned above are known to all the DNS
software packages, by default. Which means all the DNS servers can reach these root
servers without any other DNS server.
Step1: the client types www.example.com in his browser
Step2: the operating system looks at /etc/host file,first for the ip address of
www.example.com(this can be changed from /etc/nsswitch), then looks /etc/resolv.conf for
the DNS server IP for that machine
Step3: the dns server will search its database for the name www.example.com, if it finds it
will give that back, if not it will query the root server(.) for the information.
Shikhar Verma
12. o what happens when I type www.example.com in the address bar of the
browser?
Step4: root server will return a referral to the .com TLD name server(these TLD name
servers knows the address of name servers of all SLD's).In our case we searched for
www.example.com so root server will give us referral to .com TLD servers.
If it was www.example.net then root server will give, .net TLD servers refferal.
Step5: Now One of the TLD servers of .com will give us the referral to the DNS server
responsible for example.com domain.
Step6: the dns server for example.com domain will now give the client the ip address of
www host(www is the host name.)
Shikhar Verma
13. Now lets practically have a look at how this process works.
[root@myvm1 ~]# dig +trace www.google.com
; <<>> DiG 9.3.4-P1 <<>> +trace www.google.com
;; global options: printcmd
. 5 IN NS a.root-servers.net.
. 5 IN NS b.root-servers.net.
. 5 IN NS c.root-servers.net.
. 5 IN NS d.root-servers.net.
. 5 IN NS e.root-servers.net.
. 5 IN NS f.root-servers.net.
. 5 IN NS g.root-servers.net.
. 5 IN NS h.root-servers.net.
. 5 IN NS i.root-servers.net.
. 5 IN NS j.root-servers.net.
. 5 IN NS k.root-servers.net.
. 5 IN NS l.root-servers.net.
. 5 IN NS m.root-servers.net.
;; Received 228 bytes from 192.168.159.2#53(192.168.159.2) in 49 ms
14. Now lets practically have a look at how this process works.
com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
;; Received 504 bytes from 198.41.0.4#53(a.root-servers.net) in 153 ms
Shikhar Verma
15. Now lets practically have a look at how this process works.
google.com. 172800 IN NS ns2.google.com.
google.com. 172800 IN NS ns1.google.com.
google.com. 172800 IN NS ns3.google.com.
google.com. 172800 IN NS ns4.google.com.
;; Received 168 bytes from 192.33.14.30#53(b.gtld-servers.net) in 12 ms
www.google.com. 300 IN A 74.125.236.48
www.google.com. 300 IN A 74.125.236.50
www.google.com. 300 IN A 74.125.236.51
www.google.com. 300 IN A 74.125.236.49
www.google.com. 300 IN A 74.125.236.52
;; Received 112 bytes from 216.239.34.10#53(ns2.google.com) in 108 ms
Now you can clearly see from the dig with trace output that, the request first went to root
servers. a.root-servers.net replied me with the addresses of all .com gtld servers, and
b.gtld-servers.net gave me the name servers for google.com and finally ns2.google.com
replied me with the ip address of www.google.com
16. Working Procedures of DNS:
1. When your computer need to connect with a host on the Internet (e.g.
MyGreatName.com), you only need to enter the Domain Name (e.g. MyGreatName.com) in
the URL of browser. Your computer will then contact the configured or default Name Servers
(usually your ISP Name Server), asking for the IP Address of the host (e.g
MyGreatName.com).
2. If your ISP Name Server has the information of the IP Address of the query host, it will
tell your computer immediately.
3. Assume that your ISP Name Server do not have the information of MyGreatName.com.
Your ISP Name Server will ask the DNS Root Name Server immediately the Name Server
that has the information of MyGreatName.com.
STOP! You may ask: "How can your ISP Name Server knows the Root Name Server? Which
Root Name Server to ask?"
Shikhar Verma
17. Working Procedures of DNS:
Actually all Name Servers will download and install a file from the FTP server of interNIC.
The file is called "named.cache" or "named.root". This file has the IP Addresses of ALL Root
Name Servers.
there are 13 root name servers as follows.
a.root-servers.net.
b.root-servers.net.
c.root-servers.net.
d.root-servers.net.
e.root-servers.net.
f.root-servers.net.
g.root-servers.net.
h.root-servers.net.
i.root-servers.net.
j.root-servers.net.
k.root-servers.net.
l.root-servers.net.
m.root-servers.net. Shikhar Verma
18. Working Procedures of DNS:
From the above named.cache file, we know that there are 13 Root Name Servers on the
Internet (A.ROOT-SERVERS.NET., B.ROOT-SERVERS.NET., ...., M.ROOT-SERVERS.NET.).
The Root Name Servers are distributed around the world.
Root Name Servers have all of information of Autoritative Domain Name Servers for the top
level domain names (for example: .com, .org, .net, .com.hk, etc ..)
4. When your ISP Name Server do not have the IP address information of
MyGreatName.com, it will check the named.cache file and ask for help from the Root
NameServer. If the first Root Name Server is out of order or do not have response, your ISP
Name Server will ask the second Root Name server.
5. Root Name Server will then tell your ISP Name Server the authoritative Name Server of
MyGreatName.com are 212.69.192.10 (Primary
Name Server) and 212.69.192.11 (Secondary Name Server).
Shikhar Verma
19. Working Procedures of DNS:
Now you should know that why you need to submit information of two Name Servers when
register new domain names.
6. Your ISP Name Server now has the IP Address of the Authoritative Name Server of
MyGreatName.com. Your ISP Name Server will then contact the Authoritative Name Server
of MyGreatName.com (212.69.192.10). The Authoritative Name Server of
MyGreatName.com will then check and confirm the information of MyGreatName.com. It
then tell the IP Address of MyGreatName.com (212.69.204.148) to your ISP.
7. Your ISP Name Server now has the IP Address of MyGreatName.com, it will tell your
computer immediately.
8. Once your computer get the IP Address of MyGreatName.com, your computer can then
communicate with MyGreatName.com.
Shikhar Verma
20. Working Procedures of DNS:
From the working procedures of DNS, you should notice that:
The Root Name Servers on the Internet play a very important role in DNS.
There are a lot of Name servers located around the world.
All Name Servers on the Internet have the information of all Root Name Servers. If the first
Root Name Server has no response, the second Root Name Server will be contacted .......
Shikhar Verma
21. BIND
The DNS server software currently in use on Linux systems is Berkeley Internet Name
Domain (BIND). BIND was originally developed at the University of California, Berkeley
and is currently maintained and supported by the Internet Software Consortium (ISC).
The name of the BIND name server daemon is named. To operate your machine as a
name server, simply run the named daemon with the appropriate configuration.
The named daemon listens for resolution requests and provides the correct IP address
for the requested hostname.
Shikhar Verma
22. Tool
Dig domain: Domain information groper tool to obtain information on a
DNS Server. Preferred over nslookup.
Host hostname: Simple lookup of hosts
Nslookup domain: Tool to query DNS Servers for information about
domains and hosts
Rndc: Remote name daemon controller
Ndc: Name daemon controller
Shikhar Verma
23. Domain name Service Configuration
You configure a DNS Server using a configuration file, several zone files and a cache
file. The part of a network for which the name server is responsible is called a zone.
A zone is not the same as a domain because in a large domain you could have several
zones, each with its own name server.
In this case, each zone has its own zone file. The zone file hold resource records that
provide hostname and IP address associations for computers on the network for which
the DNS server is responsible.
Zone entries are defined in the named.conf file. Here, you place zone entries for your
master slave and forward DNS Servers. The most commonly used zone files are
Shikhar Verma
24. Domain name Service Configuration
Master Zone: It holds the mapping from domain names to IP addresses for all the hosts
on the network.
Slave Zone: These are references to other DNS Servers for your network to help carry
work load. A Slave DNS server automatically copies its configuration file, including all
zone files from the master DNS Server
Forward Zone: The forward zone lists name servers outside your network that should
be searched if your network’s name server fails to resolve an address.
IN-ADDR.ARPA Zone: DNS can also provide reverse resolutions, where an IP address is
used to determine the associated domain name addresses.
Shikhar Verma
25. DNS Servers
There are several kinds of DNS Servers, each perform different types of task under the
domain Name Service. These are
Master Server: This is the primary DNS Server for a zone. Each network must have at
least one master server which is responsible for resolving names on the network.
Slave Server: These are references to other dns servers for your network to help carry
workload. A slave DNS server automatically copies its configuration file, including all
zone files from the master DNS Server.
Forwarder Server: A server that forwards unresolved DNS requests to outside DNS
Servers and can be used to keep other servers as a local network hidden from the
Internet.
Shikhar Verma
26. DNS Servers
There are several kinds of DNS Servers, each perform different types of task under the
domain Name Service. These are
Caching only Server: Caches DNS information it receives from DNS Server and uses it
to resolve local request.
Shikhar Verma
27. named.conf
The configuration file for the named daemon is named.conf, located in /etc directory. It
uses a flexible syntax similar to C programs.
The named.conf file contains the main dns configuration and tells BIND where to find the
configuration files for each domain you own.
zone "." IN {
type hint;
file "named.ca";
The first zone (.) defines a hint zone specifying the root name servers. The cache file listing
these servers is named.ca.
Shikhar Verma
28. named.conf
zone “techno.com" IN {
type master;
file "fwd.techno.com.db";
The second zone statement defines a zone for techno.com domain. Its type is master and
its zone file “fwd.techno.com.db”. The next zone id ised for reverse IP mapping of the
previous zone.
zone "137.198.20.in-addr.arpa" IN {
type master;
file "137.198.20.db";
Shikhar Verma
29. named.conf
The last zone statement defines a reverse mapping zone for the loopback interface, the
method used by the system to address itself and enable communication between local users
on the system. The zone file used for this local zone is named.local
Shikhar Verma
30. Resource Records
Resource records are used to associate IP Addresses with fully qualified domain names. You
need a record for every computer in the zone.
name [<ttl> [<class>] <type> <rdata> [<comments>]
Each zone files contains a variety of records (SOA, NS,MX,A,PTR and CNAME)
Shikhar Verma
31. Resource Records
Time to Live Value (TTL)
The very first entry in the zone file is usually the zone’s time to live (TTL) value. Caching
DNS server cache the responses to their queries from authoritative DNS Servers.
The purpose of TTL is to reduce the number of DNS queries to the authoritative server
(DNS). If the TTL is set to three days, then caching servers use the original stored response
from three days before making the query again.
$TTL 3D
Shikhar Verma
32. Resource Records
Start of Authority: SOA
The zone and reverse mapping files always begin with a special resource record called the
start of Authority (SOA) record.
The format for an SOA record follows:
Name {ttl} class SOA origin person-in-charge (
serial number
refresh
retry
expire
minimum);
Shikhar Verma
33. Resource Records
The first is the serial number. You change the serial number only when you add or
change records, so that it can be updated by other servers.
Refresh specifies the time interval for refreshing SOA information.
Retry is the frequency for trying to contact an authoritative server.
Expire is the length of time a secondary name server keeps information about a zone
without updating it.
Minimum is the length of time records in a zone line.
Shikhar Verma
34. Resource Records
Name Server: NS
The name server record specifies the name of the name server for its zone.
IN NS turtle.mytrek.com.
Address Record: A and A6
Resource records of type A are address records that associate a fully qualified domain name
with an IP address.
Turtle.mytrek.com IN A 192.168.100.3
Shikhar Verma
35. Resource Records
Mail Exchanger: MX
This record specifies that the mail server is used for this zone.
mytrek.com IN MX 10 turtle.mytrek.com
Aliases: CNAME
The term CNAME stands for canonical name are used to specify alias name for a host in the
zone.
mytrek IN A 192.168.0.4
ftp.mytrek.com IN CNAME turtle.mytrek.com
Shikhar Verma
36. Resource Records
Pointer Record: PTR
A PTR record is used to perform reverse mapping an IP address to a host.
4 IN PTR turtle.mytrek.com
Shikhar Verma
37. Steps to configure DNS
Assumptions
Server Name: Server2.gupta.com
IP Address: 20.198.137.211
Install BIND package
BIND stands for Berkeley Internet Name Domain, a software which provides an ability to
perform name to ip conversion.
# yum -y install bind bind-utils
Shikhar Verma
38. Steps to configure DNS
Configure BIND
Configuration file of bind is /etc/named.conf, open up /etc/named.conf file. Comment out
the following line, and this will enable BIND to listen on all ip addresses.
#listen-on port 53 { 127.0.0.1; };
#listen-on-v6 port 53 { ::1; };
Add your network in the following line. I’ve added 192.168.12.0/24, and this will allow
clients from the mentioned network can query the DNS for the name to ip translation.
allow-query { localhost;192.168.12.0/24; };
If you want to transfer all zones to slave server (192.168.12.6), add the following line
(Optional)
allow-transfer { 192.168.12.6; };
Shikhar Verma
39. Steps to configure DNS
Create Zones
The following is the forward zone entry in named.conf file, written for the itzgeek.local
domain. Edit /etc/named.conf.
zone "gupta.com" IN {
type master;
file "fwd.gupta.com.db";
allow-update { none; };
};
gupta.com – Domain name
master – Primary DNS
fwd.gupta.com.db – Forward lookup file
allow-update – Since this is the primary DNS, it should be none
40. Steps to configure DNS
Create Zones
zone "137.198.20.in-addr.arpa" IN {
type master;
file "137.198.20.db";
allow-update { none; };
};
137.198.20.in-addr.arpa – Reverse lookup name
master – Primary DNS
137.198.20.db – reverse lookup file
allow-update – Since this is the primary DNS, it should be none
Shikhar Verma
41. Steps to configure DNS
Create zone files
Now, it’s the time to create a lookup file for a created zone. By default, zone lookup files are
placed under /var/named directory. Create a zone file called fwd.gupta.com.db for forward
lookup under /var/named directory. All domain names should end with a dot (.).
There are some special keywords for Zone Files
A – A record
NS – Name Server
MX – Mail for Exchange
CNAME – Canonical Name
Shikhar Verma
42. Steps to configure DNS
[root@Server2 named]# vi /var/named/fwd.gupta.com.db
$TTL 86400
@ IN SOA Server2.gupta.com. root.gupta.com. (
2017112807 ;Serial
3600 ;Refresh
1800 ;Retry
604800 ;Expire
86400 ;Minimum TTL
)
@ IN NS Server2.gupta.com.
Server2 IN A 20.198.137.211
Server1 IN A 20.198.137.84
gupta.com. IN MX 10 mail.gupta.com.
www IN A 20.198.137.211
mail IN A 20.198.137.211
shikhar IN CNAME Server2.gupta.com. Shikhar Verma
43. Steps to configure DNS
Create a zone file called 137.198.20.db for reverse zone under /var/named directory, create
a reverse pointer to the above forward zone entries.
PTR – Pointer
SOA – Start of Authority
Shikhar Verma
44. Steps to configure DNS
[root@Server2 named]# vi /var/named/137.198.20.db
$TTL 86400
@ IN SOA Server2.gupta.com. root.gupta.com. (
2017112807 ;Serial
3600 ;Refresh
1800 ;Retry
604800 ;Expire
86400 ;Minimum TTL
)
@ IN NS Server2.gupta.com.
211 IN PTR Server2.gupta.com.
211 IN PTR www.gupta.com.
84 IN PTR Server1.gupta.com.
Shikhar Verma
45. Steps to configure DNS
Once zone files are created, restart bind service.
# systemctl restart named.service
Enable it on system startup.
# systemctl enable named.service
Shikhar Verma
46. Steps to configure DNS
Verify zones
Visit any client machine and add a DNS server ip address in /etc/resolv.conf if Network Manager
does not manage the network.
# vi /etc/resolv.conf
nameserver 20.198.137.211
If Network Manager manages the networking then place the following entry in
/etc/sysconfig/network-scripts/ifcfg-eXX file.
DNS1=20.198.137.211
Restart network service.
# systemctl restart NetworkManager.service
Shikhar Verma
47. END of this Course Module.
http://www.itzgeek.com/how-tos/linux/centos-how-tos/configure-dns-bind-
server-on-centos-7-rhel-7.html
http://www.mygreatname.com/how-dns-works/e-04-how-dns-works.htm
https://www.slashroot.in/how-dns-works
Thanks
Shikhar Verma