We have several domains under our belt.
Domain Controller A 10.10.10.92 (Brazil_CLOUD)
Domain Controller B 10.10.10.127 (Canada_CLOUD)
Domain Controller C 10.10.10.54 (CLOUD_RESOURCES)
ClientA, in geographical location "BRAZIL" in subnet 10.10.20.x is joined to Domain A in Brazil_Cloud
We now have a singular print server that sits in 10.10.10.x subnet "CLOUD_RESOURCES" They did this to have a singular print server, instead of managing thousands of printers in many spots.
Client A can ping "print server in cloud" by IP.
Client A cant resolve printserver. UNLESS...I build a static record in Domain A DNS
printserver.canada.local which resolves to 10.10.10.127, but THE FACT IS THAT PRINTSERVER does not belong to canda.local it belongs to cloud.local
You can ping all over the place by IP, with no issues, from Domain A CLIENT in brazil on 10.10.20.x, but you cant resolve names outside of domain A, which is the problem as the printerserver resides in domain C
There is a trust already between the domains, and its working. If i go \\10.10.10.54 to the printerserver it works.
How can I get the IP to resolve to a name properly?
From Client A in Brazil, I want to ping printserver and it resolve printserver.cloud_Resources.local. This way when the guys are installing printers in any domain, they type \\printserver and it will come up easily and simply, they then select the printer that they need and off they go.