Displaying 2 results from an estimated 2 matches for "hostname_2_1".
2018 Apr 13
1
DNS backend SAMBA_INTERNAL name resolution through VPN
...------+
| hostname_1_1
| hostname_1_2
| ...
| hostname_1_N1
+---------------------------+
|
|
|
VPN
|
|
|
+--------------------------+
| SUBNET: 192.168.2.0/24
+--------------------------+
| SAMBA AD DC DNS server 2
+--------------------------+
| DOMAIN: company.elmts
+--------------------------+
| hostname_2_1
| hostname_2_2
| ...
| hostname_2_N2
+--------------------------+
Sedentary machines: have their hostname registered either on SAMBA AD DC DNS
server 1 or (exclusive) SAMBA AD DC DNS server 2.
Nomad machines: have their hostname registered on both SAMBA AD DC DNS
servers.
-----------------------...
2018 Apr 13
0
VPN remote Samba AD DC not located
...stname_1_1.company.elmts." and IP "192.168.1.11"
and that there is another one which FQDN is
"hostname_1_2.company.elmts." with IP "192.168.1.12"
Etc.
Currently, the problem is:
When I am on machine "hostname_1_1.company.elmts."
and I "ping hostname_2_1.company.elmts."
the local Samba DNS server doesn't know the name
"hostname_2_1.company.elmts.".
Because the two Samba AD DC do not know each other.
Because the DNS servers (Bind remote and SAMBA_INTERNAL local) do not
know each other.
I don't know how to make them be aware...