DNS Configuration Research Articles

NETWORK PROGRAMMABILITY FOR NETWORK ISSUE USING PARAMIKO LIBRARY

In a company, information technology is needed, especially computer networks, to facilitate data communication. The management of a computer network, of course, requires good administration. The criteria for whether or not a network is good can be seen from the performance, reliability, and security indicators so that it will not cause network issues. Events such as server downs, data loss, lost connections, and undetected computers cause the organization's business performance to be disrupted. This study's purpose is to detect network issues with network programmability technology automatically. Paramiko library supports network automation systems and implements OSPF routing protocol in finding the shortest path to send network packets. This study uses the PPDIOO flow, namely prepare, plan, design, implement, operate, and optimize, because it is considered by the flow of making network detection tools. The results showed that the design and implementation of a small-scale network were successfully built by utilizing network programmability technology and the paramiko library, which helps detect network conditions at any time. This design has a dashboard, provisioning, assurance, and policy features that allow administrators to manage and monitor information on each network device. The network design is fitted with REST-API technology and security through a secure shell (ssh) from the Network Controller that can detect the device's connection conditions and the device's health and update the DNS configuration used. Network Issues that have been seen are devices being down, and the connection being lost. Future research can improve features for network troubleshooting when the connection is lost.

Estimating Maintenance Cost for Web Applications

(ProQuest: ... denotes formulae omitted.)1 Research Premises and HypothesisMaintenance costs have a consistent weight in the total costs generated by an application during its entire lifecycle. Previously conducted research and studies that focus on software maintenance support this claim. In [2], the 60/60 rule of software is depicted. The rule claims that maintenance accounts for 60% of the total costs generated by a software in its entire lifecycle. Enhancement or perfective [3] maintenance tasks account for 60% of all the costs generated by maintenance [2], whereas error correction or corrective [3] maintenance tasks account only for 17% of total maintenance costs [2]. In [4] it's stated that software applications evolve over time to meet the changing needs which leads to maintenance generating 67% of the applications total lifecycle costs. In [5] it is argued that maintenance typically accounts for 75% or more of the total software workload. Other relevant research place maintenance costs at 90% [6], 75% [7], 90% [8] or at 60% to 70% [9] of the overall application's lifecycle cost. It is therefore of paramount importance to accurately estimate maintenance cost before implementing a software project in order to better comprehend the total costs associated with developing and owing a software application. Better understanding maintenance costs will provide valuable information regarding resource planning and the appropriate time to decommission the application.The cost of maintenance is directly determined by the number of people involved in the maintenance process and the number of hours each person invests in the maintenance tasks. Thus in order to estimate maintenance cost one needs to estimate the effort invested in the maintenance process. The maintenance effort is expressed in man-hours which entails the number of ours dedicated by the maintenance team to implementing maintenance tasks. Maintenance in web applications has two main components: content maintenance and technical maintenance.Content maintenance requires performing tasks of a non-technical nature like updating product inventory and information, adding news or articles, managing blog posts, updating contact or brand and visual identity information and moderating user comments or messages. Content maintenance team staffing and therefore content maintenance effort is determined by the web application's size [1].According to [1] and as presented in Table 1, content maintenance cost is determined by the number of hours required to keep the web application up to date in terms of content. The larger the application the more hours need to be invested in keeping it up to date in terms of content. The more content changes in an application the more technical maintenance tasks are generated. Technical maintenance tasks are generated because content managers spot bugs or request new functionality to help keep the content up to date. Therefore, content update frequency is a factor that impacts maintenance effort and cost.Technical maintenance requires adding new functionality, performing regular back-ups, monitoring website outages, checking IP reputation, checking DNS configuration, test website speed, check for broken links, perform software updates if third party software was used when developing the web application, monitor traffic statistics and review search engine indexing.According to [1] and as presented in Table 2, technical team stuffing is determined by the level of complexity built into the web application. Thus, a Basic web application which is characterized by static content build mainly using front-end technologies like HTML, CSS and JavaScript will require no more than 1 person to perform maintenance tasks. A Dynamic web application which stores its content in a database and has functionality which is powered by PHP, Java, ASP.NET, Python, Ruby or any other high-level programming language will require 1 to 2 persons to perform maintenance tasks. …

DNS Configuration in IPv6: Approaches, Analysis, and Deployment Scenarios

IPv6 provides abundant address space and automatic network-parameter configuration. The IETF has proposed three approaches for DNS configuration in IPv6 hosts for recursive DNS server addresses and the DNS search list. The authors analyze these approaches and describe four deployment scenarios in IPv6 wired and wireless networks. They provide guidelines for DNS configuration that IPv6 network administrators and users can apply in their target networks.

Design and implementation of an intelligent DNS management system

In this paper, we focus on the design and building of iDNS-MS by using knowledge-based system and ontological engineering technologies. iDNS-MS , developed by using web interface and expert system technology, is a unifying environment for providing plausible answers to help solve the complex DNS management problems or alleviate these DNS administration loadings. In iDNS-MS , we propose an ontology-driven model to elicit rules from a previously built DNS ontology and construct an objected-oriented knowledge base. The whole process of the model consists of ontology construction, knowledge class organization and facts/rules loading phases. Ontology construction phase is used to construct the domain ontology, knowledge class organization phase is used to organize the relationships between the knowledge classes, and facts/rules loading phase is used to fill in the facts/rules of knowledge classes extracted from domain experts. In addition, we adopt DRAMA/NORM development environment as the expert system shell to design and implement a unifying framework (e.g. DNS-related problem diagnosis, planning, tutoring, etc.) for supporting intelligent DNS management. According to our experimental results, the paradigm of using DNS ontology to build iDNS-MS works good and effective. iDNS-MS will benefit the sharing and reusing of global DNS knowledge, the reduction of people's time to learn DNS management, the ease of DNS configuration and planning, and the improvement on DNS and network operation.

Cohesive and Structural Energies for the 5d Elements, Lu through Au

We have calculated the cohesive energy and the energy difference between the fcc and bcc phases of the 5d elements Lu-Au using the recently developed Linear Augmented Slater Type Orbital method. We find the crystal structure to be correctly predicted and the structural energy differences to be significantly larger than the most commonly quoted values. We also find that the cohesive energies of these elements can be understood within the local spin density functional theory provided the experimental promotion energy from the local density dns configuration to the preferred dn-1s2 configuration is included.