Hello there!
I should note that I am relatively new to networking and still have much to learn about its intricacies.
Currently, my domain controller is deployed on Yandex cloud, which unfortunately does not allow for changes to its IP and DNS settings. Despite being told that everything is static, I am unable to change settings without losing the machine.
I have attempted to register the external IP address of the controller in their DNS but have had no success in joining computers to the domain.

Additionally, when attempting to create a reverse view zone on a domain controller, an error appears upon checking the box in the PTR record. Below are nslookup results from the computer I am trying to connect to the domain.
Could someone please suggest how I might join my computer to the domain given the differing subnets between it and the domain controller?

If possible, I have access to a microtick on site which could be used as a last resort. If anyone knows how to turn it through it, please let me know.
I have been scrolling through Google for two days now in search of a solution and have tried everything I can think of to no avail. Another domain controller has been experiencing similar issues as well. As always, the deadline is quickly approaching.

To enter the domain, the input machine needs to be contacted by the domain controller. However, if there is no connection between the machine and the reverse routing cloud, this cannot happen. It is important to establish the expected connection using a VPN.

It is crucial to ensure that the input machine is reachable by the domain controller for successful domain access. When there is no connection between the machine and the reverse routing cloud, this becomes impossible. To overcome this, setting up a VPN and connecting as expected would be the best solution.

For a successful domain joining, the PC and the domain controller must establish a connection. The SRV record for the controller needs to be accurate as this is what the PC will use to locate it.

However, if you're on separate networks, you may run into some issues. In such cases, it's imperative that these conditions are met; otherwise, the entire process will fail.

It's essential to ensure that all technical requirements are met before attempting to join a domain. Failure to do so could lead to a lot of frustration and wasted time.

You must ensure that there is a single network (subnet) present in all the network settings. You can register it on your own, for instance, 192.168.100.4 in the domain, and 192.168.100.5 on the PC that you are accessing.

Also, remember to manually set up the DNS and make sure that it's in an online status in the domain. This information can be found in the server manager.

Afterwards, perform a ping back and forth test. If the ping is successful, then go ahead and add the PC to the domain. However, if they are in different subnets, this will not work.

You're stuck with a domain controller in Yandex cloud, and they won't let you touch the IP or DNS settings. That's a bummer, but we'll work with what we've got. Now, you've tried registrin' the external IP in their DNS, but no luck joinin' computers to the domain. That's 'cause you're missin' a crucial step, or maybe a few.

When you're tryin' to join a computer to a domain, it needs to be able to resolve the domain name to an IP address, and vice versa. That's where DNS comes in. You've got a forward lookup zone for A records, right? Make sure you've added an A record for your domain controller's hostname that points to its IP address. And don't forget to add a CNAME record for the '@' symbol that points to the hostname. That's a common mistake, newbie.

Now, you're tryin' to create a reverse lookup zone for PTR records, but you're gettin' an error. That's likely 'cause you're tryin' to create a zone for a network that's not yours, or you don't have the right permissions. Remember, the reverse lookup zone should match the network ID of the computers you're tryin' to join. And when you add the PTR records, make sure the target is the fully qualified domain name (FQDN) of the computer, not just the hostname.

As for the nslookup results, if they're showin' that the domain controller can't be resolved, that's a red flag. It means your DNS settings are all wonky, and you need to fix 'em. Check your forward and reverse lookup zones again, and make sure the DNS server on your domain controller is configured correctly.

Now, about that microtick on site. If you're thinkin' about usin' it as a last resort, let me stop you right there. That's like bringin' a knife to a gunfight. A microtick is a network time protocol (NTP) server, not a DNS server. It won't help you with your domain joinin' issues. But, if your domain controller's clock is way off, it could cause authentication problems. So, make sure it's synced with the microtick, or another reliable time source.

And listen, I get it, you're new to this. But don't go runnin' around like a chicken with its head cut off. Take a deep breath, and tackle one problem at a time. And for cryin' out loud, read the error messages. They're there to help you, not confuse you.

Now, go fix your DNS, and get those computers joined to the domain. And remember, next time you're stuck, don't just keep bangin' your head against the wall. Take a step back, and look at the bigger picture.

If you can't even manage to join a domain due to subnet issues, it might be time to reconsider your approach to networking. The fact that you're relying on Yandex Cloud's static settings without a backup plan is risky.

Have you even tried basic troubleshooting like checking connectivity with ping or traceroute? The MikroTik could be a lifesaver, but if you don't know how to leverage it, you're just wasting time. Get your hands dirty with the routing configurations and make sure your DNS records are set up properly.