Atilla Tanrikulu

  •         

I am an experienced software engineer and architect living in Germany. I’m passionate about distributed scalable enterprise web-based microservices/applications and delivering great user experiences. I have created some amazing enterprise-level applications that many people have used and hopefully enjoyed.

Articles

Java Quick Reference Apache Kafka Tutorial Guvenli Kod Gelistirme Making an Enterprise Scale Angular Project Step by Step Nightly SQL Server Database Backup with command line batch file and windows scheduler AOP Framework without proxy pattern IdentityServer Nedir Middleware Pattern With Csharp And Javascript Docker most used commands Online Proje Dokumantasyonu, Docker, Nginx, mdwiki How to use Github Pages for static websites Inheritance with JavaScript, EC6 (ECMAScript 6, ECMAScript 2015) Object oriented javascript and Inheritance Singleton Pattern with Javascript Factory Pattern with Javascript Open terminal here mac os x service IdentityServer4-Angular-6-integration JMater notlari, kurulum ve kullanim Learn Jekyll in 12 Steps Make Mac Application with Automater from sh script Make spotlight index markdown or code files OAuth 2.0 Nedir (RFC6749) Using Custom CSS and Custom JavaScript to an Angular Project Cross Platform Desktop Application With .Net Core 2x and Angular 6x front-end projects with nodejs gulp bower yeoman and angularjs Host Asp.Net Core on Linux with Apache Redis kurulumu ve ayarlari Useful Mac OS Apps Choosing internet connection on multiple interface windows Changing the Responsible DNS (Name Server) for a Domain Name How to define domain name for your dynamic IP SQL table data compare, and prepare insert satements Useful Git Commands TFS ile Otomatik deployment yapmak Spring Boot Tutorial Sql server icin maliyetli sorgularin tespit edilmesi Arama Motoru Optimizasyonu (SEO) My installed mac apps

Yakında Hazırlanacak

Mac OS bilgisayarda Wine kullanimi ve Wine icin tavsiye programlar. Mac icin tavsiye programlar Atom icin tavsiye pluginler Chain of responsibility Design Pattern Kurumsal yazilmlarda kullanilan Design Pattern'ler Kurumsal yazilimlarda Cache yonetimi

Changing the Responsible DNS (Name Server) for a Domain Name

Purpose: To change the responsible DNS record for a domain name purchased from any provider.

Normally, companies from which we purchase domain names set their own DNS servers as the “Name Server” (NS) records for those domains. However, the purpose of this guide is to ensure that the company we purchased the domain from replaces the responsible “Name Server” records with the IP addresses of our own DNS servers.

What Does This Process Provide Us?

This process allows us to function as a defined DNS provider on the internet. As a result:

  • We can direct all the domains we have purchased to our own “Name Server.”
  • We can add subdomains and MX records to any domain we own.
  • We gain complete control over all domain-related operations.

Example Scenario:

Let’s assume we own three domain names, all purchased from www.netsol.com:

Domain Name Name Server (NS)
sirket1.com : ns1.netsol.com, ns2.netsol.com
sirket2.com : ns1.netsol.com, ns2.netsol.com
sirket3.com : ns1.netsol.com, ns2.netsol.com

Now, let’s define a new Name Server for one of these domains:

Name Server IP Address
ns1.sirket1.com : 68.78.88.98 (Our static IP address)
ns2.sirket1.com : 68.78.88.98 (Our static IP address)

Updating the Domain Name NS Records:

Let’s modify the current NS records of the three domain names as follows:

Domain Name Name Server (NS)
sirket1.com : ns1.sirket1.com, ns2.sirket1.com
sirket2.com : ns1.sirket1.com, ns2.sirket1.com
sirket3.com : ns1.sirket1.com, ns2.sirket1.com

After these updates, when someone on the internet tries to access www.sirket2.com, the DNS query for the domain will proceed as follows:

  1. The query is sent to the root DNS servers.
  2. Starting from the root DNS servers, the query eventually reaches our DNS server.
  3. Since our server is now the responsible DNS, it will be asked for the IP address of the www subdomain.
  4. Our DNS server will return the IP address defined for the www subdomain in our configuration.

DNS-Name-Server-Process.png

Important Note:

After making these changes, don’t assume, “I made the changes, but it’s not working yet.” Some of these updates may take anywhere from 1 minute to 24 hours to become active on the internet.

For example, if you set the NS record for sirket2.com to ns1.sirket1.com, it may take up to 24 hours for this change to propagate and become active.

Date: 2024-12-15

Date: 2024-12-15 10:20:00 +0000