IT Manager

high_sobo

footech

<div>
Oh, and once a trust is created between the domains, this zone will be redundant and should be removed.
</div>


<div>
I would use conditional forwarder in DNS instead. You'll also need them for your trust, so might as well get started. <br />
<br />
<a href="https://www.dell.com/support/article/tt/en/ttbsdt1/sln164002/how-to-create-a-conditional-forwarder-on-a-windows-dns-server?lang=en" rel="ugc nofollow">https://www.dell.com/support/article/tt/en/ttbsdt1/sln164002/how-to-create-a-conditional-forwarder-on-a-windows-dns-server?lang=en</a><br />
<br />
There is a potential for issue regarding email delivery, if the DNS zone overlaps with their public email domain. If that is the case, the AD zone would need to have valid MX records for mail delivery for email being sent by the other domain, with possible SMTP delivery over the VPN (depending on the email infrastructure).
</div>


<div>
@DrDave242 so then we can move forward with the forward zone for NY in PA without having domain trust for now with no issues? We most likely would move forward with the trust, but for right now we do not have time to proceed with the trust due to project constraints. Thank you for the reminder to delete the forward zone once the trust has been established down the road. I will delete it at that time to remove the repetitive forward lookups.
</div>


<div>
Yeah, this won't cause any issues, since the zone is only for one specific name: NY-FS1.NY-domain.com. It won't affect the ability for PA users to resolve other names in the NY-domain.com domain (so mail delivery to NY-domain.com won't be affected, for example).
</div>


<div>
<div class="content wysiwyg-content">
Question regarding adding a DNS zone and manually entering a PTR record for a key File Server.<br />
<br />
I just joined our 2 offices (PA Office where I work &amp;&nbsp;NY Office) via a VPN tunnel using our SonicWalls. &nbsp;Both locations have completely separate networks, but we can now see each other servers by IP only. Were are running Windows 2008 R2 Domain Controllers and File Servers.<br />
<br />
I would like PA's staff to be able to &quot;see&quot; NY's File Server by host name versus IP, so I would like to add a PTR record for this server. &nbsp;However, PA &amp;&nbsp;NY's domain is different, so I'm thinking I can add a DNS zone in PA (non Active Directory integrated I would assume) for the NY domain for the purpose of adding a PTR record like:<br />
NY-FS1.NY-domain.com = 192.168.50.200<br />
<br />
Later, I am planning on setting up a trust between the domains, but I am not ready to do this yet. &nbsp;So I was looking to solve this problem as soon as possible. &nbsp;However I'm nervous about the implications of adding a DNS zone without knowing the implications.<br />
<br />
Thank you
</div>
</div>


Question regarding adding a DNS zone and manually entering a PTR record for a key File Server.

I just joined our 2 offices (PA Office where I work & NY Office) via a VPN tunnel using our SonicWalls.  Both locations have completely separate networks, but we can now see each other servers by IP only. Were are running Windows 2008 R2 Domain Controllers and File Servers.

I would like PA's staff to be able to "see" NY's File Server by host name versus IP, so I would like to add a PTR record for this server.  However, PA & NY's domain is different, so I'm thinking I can add a DNS zone in PA (non Active Directory integrated I would assume) for the NY domain for the purpose of adding a PTR record like:
NY-FS1.NY-domain.com = 192.168.50.200

Later, I am planning on setting up a trust between the domains, but I am not ready to do this yet.  So I was looking to solve this problem as soon as possible.  However I'm nervous about the implications of adding a DNS zone without knowing the implications.

Thank you

Question regarding adding a DNS zone and manually entering a PTR record for a key File Server.

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

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.