<div>
This is likely a DNS issue.<br />
<br />
What are you using for a DNS server? &nbsp;To what does the new server point for DNS?
</div>


<div>
both server DNS point to 10.12.179.13 this the IP of Server contains the AD&nbsp; DNS for both VLAN
</div>


<div>
but the server that contains the AD have tow IP one &nbsp;public and one local &nbsp;the _msdcs configuration using &nbsp;the public IP because when I trying to add PC, not in the local network is seeing the domain &nbsp;also when I try nslookup<br>Default Server: &nbsp;ne-r064-301cn.digitalyard.com<br>Address: &nbsp;10.12.179.13<br><br>&gt; type=all<br>Server: &nbsp;ne-r064-301cn.digitalyard.com<br>Address: &nbsp;10.12.179.13<br><br>*** ne-r064-301cn.digitalyard.com can't find type=all: Non-existent domain<br>&gt; type=all<br>Server: &nbsp;ne-r064-301cn.digitalyard.com<br>Address: &nbsp;10.12.179.13<br><br>*** ne-r064-301cn.digitalyard.com can't find type=all: Non-existent domain<br>&gt;
</div>


<div>
First of all you are not supposed to expose your server without required security measures.<br />
What happens if you give an internal IP back to NIC which is same range of other server IP?
</div>


<div>
10.12.179.13 &nbsp;my local IP<br>the new server &nbsp;10.12.179.14 <br>what should i do ?&nbsp;
</div>


<div>
i have tow nics VLAN in each server one for local network with rang 10.12.179.13 /255.255.255.0 and the other for internet<br>but my domain host A record using the public IP I added new host with local IP but the issue still exist
</div>


<div>
On the new DC, try the following from a CMD prompt:<br />
nslookup ne-r064-301cn<br />
<br />
(I'm presuming that the existing server's name is ne-r064-301cn)<br />
<br />
Also, I don't think &quot;type=all&quot; is valid in nslookup.<br />
<a href="https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/nslookup-set-type" rel="ugc">https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/nslookup-set-type</a>
</div>


<div>
C:\Users\Administrator&gt;nslookup ne-r064-301cn<br>Server: &nbsp;ne-r064-301cn.digitalyard.com<br>Address: &nbsp;10.12.179.13<br><br>*** ne-r064-301cn.digitalyard.com can't find ne-r064-301cn: Query refused<br><br><br><br><br>
</div>


<div>
if we can make online session will be nice &nbsp;even if there some fee
</div>


<div>
One other suggestion. &nbsp;Try this at a CMD prompt:<br />
nslookup ne-r064-301cn.<br />
<br />
(note the period at the end)
</div>


<div>
from the new server that I want to join existing <br>PS C:\Users\Administrator&gt; test-netconnection 10.12.179.13 -port 53<br><br><br>ComputerName &nbsp; &nbsp; : 10.12.179.13<br>RemoteAddress &nbsp; &nbsp;: 10.12.179.13<br>RemotePort &nbsp; &nbsp; &nbsp; : 53<br>InterfaceAlias &nbsp; : bond0 - VLAN 3408<br>SourceAddress &nbsp; &nbsp;: 10.12.179.14<br>TcpTestSucceeded : True<br><br><br><br>PS C:\Users\Administrator&gt; Resolve-DNSName digitalyard.com<br><br>Name &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Type &nbsp; TTL &nbsp; Section &nbsp; &nbsp;IPAddress<br>---- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ---- &nbsp; --- &nbsp; ------- &nbsp; &nbsp;---------<br>digitalyard.com &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;A &nbsp; &nbsp; &nbsp;10800 Answer &nbsp; &nbsp; 10.12.179.13<br><br><br>PS C:\Users\Administrator&gt;<br><br><ol><li><br></li></ol>
</div>


<div>
from the new server that I want to join existing<br>Default Server: &nbsp;ne-r064-301cn.digitalyard.com<br>Address: &nbsp;10.12.179.13<br><br>&gt; type=all<br>Server: &nbsp;ne-r064-301cn.digitalyard.com<br>Address: &nbsp;10.12.179.13<br><br>*** ne-r064-301cn.digitalyard.com can't find type=all: Query refused<br>&gt; _ldap._tcp.dc._msdcs.digitalyard.com<br>Server: &nbsp;ne-r064-301cn.digitalyard.com<br>Address: &nbsp;10.12.179.13<br><br>Name: &nbsp; &nbsp;_ldap._tcp.dc._msdcs.digitalyard.com<br><br>&gt;<br>&gt; set type=all<br>&gt;<br>&gt; _ldap._tcp.dc._msdcs.digitalyard.com<br>Server: &nbsp;ne-r064-301cn.digitalyard.com<br>Address: &nbsp;10.12.179.13<br><br>_ldap._tcp.dc._msdcs.digitalyard.com &nbsp; &nbsp;SRV service location:<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; priority &nbsp; &nbsp; &nbsp; = 0<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; weight &nbsp; &nbsp; &nbsp; &nbsp; = 100<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; port &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; = 389<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; svr hostname &nbsp; = ne-r064-301cn.digitalyard.com<br>ne-r064-301cn.digitalyard.com &nbsp; internet address = 10.12.179.13<br>ne-r064-301cn.digitalyard.com &nbsp; internet address = xxx.xxx.xxx.xxx my online IP of AD SERVER&nbsp;
</div>


<div>
from the new server that I want to join existing <br>C:\Users\Administrator&gt;nslookup ne-r064-301cn<br>Server: &nbsp;ne-r064-301cn.digitalyard.com<br>Address: &nbsp;10.12.179.13<br><br>*** ne-r064-301cn.digitalyard.com can't find ne-r064-301cn: Query refused
</div>


<div>
Try this at a CMD prompt:<br />
nslookup ne-r064-301cn.<br />
<br />
(note the period at the end)<br />
<br />
Also, type=all isn't a valid option.
</div>


<div>
I found the issue Firewall network setting when off works fine,<br>I opened &nbsp;ports but still not working when &nbsp;Firewall &nbsp; on<br><table><tbody><tr><td><br></td><td><br></td></tr><tr><td><br></td><td>135/TCP</td><td><br></td></tr><tr><td><br></td><td>464/TCP/UDP</td><td><br></td></tr><tr><td><br></td><td>49152-65535/TCP</td><td><br></td></tr><tr><td><br></td><td>389/TCP/UDP</td><td><br></td></tr><tr><td><br></td><td>636/TCP</td><td><br></td></tr><tr><td><br></td><td>3268/TCP</td><td><br></td></tr><tr><td><br></td><td>3269/TCP</td><td><br></td></tr><tr><td><br></td><td>53/TCP/UDP</td><td><br></td></tr><tr><td><br></td><td>49152 -65535/TCP</td><td><br></td></tr><tr><td><br></td><td>88/TCP/UDP</td><td><br></td></tr><tr><td><br></td><td>445/TCP</td><td><br></td></tr><tr><td><br></td><td>49152-65535/TCP</td></tr></tbody></table><br><br>
</div>


Hassan Sabra

<div>
Glad to have helped. &nbsp;Your comment about the firewall was the key.
</div>


<div>
<div class="content wysiwyg-content">
I have installed AD on my server with public &nbsp;Domain and public IP address, now I'm trying to join &nbsp;my AD &nbsp;using the second server its give me Error both servers have VLAN one for local and one for internet <br />
<br />
<br />
DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain &quot;digitalyard.com&quot;:<br />
<br />
The query was for the SRV record for _ldap._tcp.dc._msdcs.digit<wbr />alyard.com<wbr /><br />
<br />
The following domain controllers were identified by the query:<br />
ne-r064-301cn.digitalyard.<wbr />com<br />
<br />
<br />
However no domain controllers could be contacted.<br />
<br />
Common causes of this error include:<br />
<br />
- Host (A) or (AAAA) records that map the names of the domain controllers to their IP addresses are missing or contain incorrect addresses.<br />
<br />
- Domain controllers registered in DNS are not connected to the network or are not running.
</div>
</div>


I have installed AD on my server with public  Domain and public IP address, now I'm trying to join  my AD  using the second server its give me Error both servers have VLAN one for local and one for internet 


DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain "digitalyard.com":

The query was for the SRV record for _ldap._tcp.dc._msdcs.digitalyard.com

The following domain controllers were identified by the query:
ne-r064-301cn.digitalyard.com


However no domain controllers could be contacted.

Common causes of this error include:

- Host (A) or (AAAA) records that map the names of the domain controllers to their IP addresses are missing or contain incorrect addresses.

- Domain controllers registered in DNS are not connected to the network or are not running.

add DC to exist AD  issue

Windows Server 2019

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.