I’m making an attempt to create my very own dns utilizing Bind9 and Debian 11
One Digital Machine in Google Computing Engine has these configuration

Server 1 Google Cloud IP 35.206.115.212
The file /and so forth/hosts

127.0.0.1       localhost
::1             localhost ip6-localhost ip6-loopback
ff02::1         ip6-allnodes
ff02::2         ip6-allrouters
35.206.115.212 ns1.itinfrastructuretest.information ns1
10.128.0.2 instance-1.us-central1-a.c.dns-1902.inside instance-1  # Added by Google
169.254.169.254 metadata.google.inside  # Added by Google

The file /and so forth/hostname

ns1

The File /and so forth/bind/zones/db.35.206.115

; BIND reverse knowledge file for native loopback interface
;
$TTL    604800
@       IN      SOA     itinfrastructuretest.information. root.itinfrastructuretest.information. (
                              2         ; Serial
                         604800         ; Refresh
                          86400         ; Retry
                        2419200         ; Expire
                         604800 )       ; Adverse Cache TTL
;
        IN      NS      ns1.itinfrastructuretest.information.
        IN      NS      ns2.itinfrastructuretest.information.


1       IN      PTR     ns1.itinfrastructuretest.information.
2       IN      PTR     ns2.itinfrastructuretest.information.
3       IN      PTR     www.itinfrastructuretest.information.

The File /and so forth/bind/zones/db.itinfrastructuretest.information

$TTL    604800
@       IN      SOA     ns1.itinfrastructuretest.information. root.itinfrastructuretest.information. (
                              5         ; Serial
                         604800         ; Refresh
                          86400         ; Retry
                        2419200         ; Expire
                         604800 )       ; Adverse Cache TTL
;

; Identify servers
itinfrastructuretest.information.    IN      NS      ns1.itinfrastructuretest.information.
itinfrastructuretest.information.    IN      NS      ns2.itinfrastructuretest.information.

; A information for identify servers
ns1             IN      A       35.206.115.212
ns2             IN      A       15.236.156.144

; Different A information
@               IN      A       15.236.147.109
www             IN      A       15.236.147.109
                IN      TXT     google-site-verification=EdC5AxyrHZ-HnRwyCgjckdIiFgFDzLniOyS2Tm6MwAk
; Mail server MX report

The File /and so forth/bind/named.conf.native

//
// Do any native configuration right here
//

// Take into account including the 1918 zones right here, if they don't seem to be utilized in your
// group
//embody "/and so forth/bind/zones.rfc1918";

zone "itinfrastructuretest.information" {
  kind grasp;
  file "/and so forth/bind/zones/db.itinfrastructuretest.information";
 allow-transfer { 15.236.156.144; };
};

zone "115.206.35.in-addr.arpa" {
        kind grasp;
        notify no;
        file "/and so forth/bind/zones/db.35.206.115";
};

The File /and so forth/bind/named.conf.choices

choices {
        listing "/var/cache/bind";

        dnssec-validation auto;

        listen-on-v6 { any; };

recursion no;
allow-transfer { none; };
auth-nxdomain no;
};

Server 2 Amazon Cloud IP 15.236.156.144
The Second Server on AWS
The /and so forth/hosts

# Your system has configured 'manage_etc_hosts' as True.
# Because of this, if you want for adjustments to this file to persist
# then you will want to both
# a.) make adjustments to the grasp file in /and so forth/cloud/templates/hosts.tmpl
# b.) change or take away the worth of 'manage_etc_hosts' in
#     /and so forth/cloud/cloud.cfg or cloud-config from user-data
#
127.0.1.1 ip-172-31-45-28.eu-west-3.compute.inside ip-172-31-45-28 ns2 ns2
127.0.0.1 localhost
15.236.156.144 ns2.itinfrastructuretest.information ns2
# The next strains are fascinating for IPv6 succesful hosts
::1 ip6-localhost ip6-loopback
fe00::Zero ip6-localnet
ff00::Zero ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::Three ip6-allhosts

The file /and so forth/hostname

ns2

The File /and so forth/bind/named.conf.native

//
// Do any native configuration right here
//

// Take into account including the 1918 zones right here, if they don't seem to be utilized in your
// group
//embody "/and so forth/bind/zones.rfc1918";

zone "itinfrastructuretest.information"{
  kind slave;
  file "db.itinfrastructuretest.information";
  masters { 35.206.115.212;};
};

zone "156.236.15.in-addr.arpa" {
        kind slave;
        file "db.15.236.156";
        masters {35.206.115.212 ;};
};

The File /and so forth/bind/named.conf.choices

choices {
        listing "/var/cache/bind";

 dnssec-validation auto;

        auth-nxdomain no;    # conform to RFC1035
        listen-on-v6 { any; };
        allow-transfer { none; };
        recursion no;

};

I used to be following these tutorials

How To Configure Bind as an Authoritative-Only DNS Server on Ubuntu 14.04

and
BIND9ServerHowto

The uploaded picture reveals that nothing was transferred from the grasp dns to the slave dns.
enter picture description right here

Once I run dig command within the grasp dns server I obtained this

 dig 35.206.115.212 115.206.35.in-addr.arpa. AXFR

; <<>> DiG 9.11.5-P4-5.1-Debian <<>> 35.206.115.212 115.206.35.in-addr.arpa. AXFR
;; world choices: +cmd
;; Bought reply:
;; ->>HEADER<<- opcode: QUERY, standing: NXDOMAIN, id: 39639
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: model: 0, flags:; udp: 512
;; QUESTION SECTION:
;35.206.115.212.                        IN      A

;; AUTHORITY SECTION:
.                       86385   IN      SOA     a.root-servers.web. nstld.verisign-grs.com. 2020051700 1800 900 604800 86400

;; Question time: 1 msec
;; SERVER: 169.254.169.254#53(169.254.169.254)
;; WHEN: Solar Could 17 09:38:42 UTC 2020
;; MSG SIZE  rcvd: 118

; Switch failed.

I attempted @ earlier than dig command. Nonetheless, there’s something I’m not positive about. Can I construct my very own DNS, SMTP, CA in cloud by cloud suppliers like AMAZON, GOOGLE, and MICROSOFT? or I’ve to make use of the providers for these protocols which might be supplied by the cloud suppliers? Amazon Route 53, Amazon SES, and AWS Certificates Supervisor (ACM) Personal Certificates Authority (CA)

I have no idea if I have to register one thing for ns1.itinfrastructuretest.information and ns2.itinfrastructuretest.information at
https://search.arin.web/rdap/ or

https://www.internic.web/
or my registrar or my internet hosting firm Google Cloud and Amazon Cloud