We help IT Professionals succeed at work.

Internal DNS records help

We have an external DNS domain called tester.org..so our external website is tester.org

We have our internal active directory domain called ad.tester.org

Some developed an internal intranet site called inside.tester.org and so to access the site it's inside.tester.org/tester. They asked us to put this in our internal Active Directory DNS.

So I'm attempting to enter a new 'A Record' or should it be a 'CName' record to point to inside.tester.org/tester ,but when I enter it comes up as inside.ad.tester.org automatically giving it the parents domain.

How can I create a record in my DNS that will allow the users to get to inside.tester.org/tester? Also eventually I'll need to add this to group policy, so the users won't need to type it in and I can make the intranet site their home page
Comment
Watch Question

Nick RhodeIT Director
Top Expert 2013

Commented:
In DNS you have to create a new zone for this.  Create a Zone with the targeted DNS you wish to have.  So zone name would be tester.org or whatever you need.

Just open up DNS and right-click Forward Lookup Zones > New Zone
Distinguished Expert 2018

Commented:
You cannot create a DNS record that will point to <anything>/tester. DNS only resolves a domain name to an IP address. It does not manage or manipulate full URLs.
Nick RhodeIT Director
Top Expert 2013

Commented:
The zone created would be tester.org

Within that zone an A record would be created called inside so it would show as inside.tester.org which would resolve to the target ip he specifys.  the /tester is a sub-page which is irrelevant to DNS like Cliff said
Brian PringleSystems Analyst II, SCM, ERP

Commented:
You would just create an A record that points to inside.tester.org with its current IP address.
Principal Support Engineer
Commented:
The problem with creating an internal zone named tester.org is that anything in the external tester.org domain that needs to be accessed from inside will need a record in that zone. This isn't bad if there are only a couple of hosts that fit this description and their addresses won't change, but otherwise it can be a hassle.

To avoid the potential hassle, you can create an internal zone named inside.tester.org, then create a blank host record inside it and give that record the IP address of the intranet site. This way, inside.tester.org will resolve to the intranet site's address, but other tester.org names will be handled by the public DNS. Users will still have to append /tester manually to the URL, though, as mentioned above.

Author

Commented:
Thanks everyone,

DrDave242 - Correct, this is what i'm afraid of. Our External domain is tester.org. and presently the users default home page goes out tester.org

There already a zone called insider.tester.org., our internal Active Directory domain is insider.tester.org. This is where everything lives. Servers, PC's, printers, users etc. are all a part of insider.tester.org already.

So I'd need to create a zone called tester.org within our internal AD DNS and rush to create A records for external sites that have tester.org that our users are presently accessing from inside now?
DrDave242Principal Support Engineer

Commented:
There already a zone called insider.tester.org., our internal Active Directory domain is insider.tester.org.
You mentioned in the original question that your AD domain is ad.tester.org. Which one is it?

Author

Commented:
My apologies if I've worded the original wrong..

We have an external DNS domain called tester.org..so our external website is tester.org
 We have our internal active directory domain called ad.tester.org

Internal domain - ad.tester.org
External domain - tester.org

Thanks
DrDave242Principal Support Engineer

Commented:
And the new intranet site is still inside.tester.org/tester? If so, my recommendation stands: create a forward lookup zone named inside.tester.org in your internal DNS, then create a blank host record in that zone and give it the IP address of the intranet site.

If the intranet site is actually at ad.tester.org/tester, that could get complicated.
Top Expert 2014

Commented:
What about the chance of using the FQDN "inside.ad.tester.org"?  Since it's an intranet app I would lean towards having its record in the same zone as the rest of the "ad" domain.

If that's not possible, I would follow DrDave242's advice and create the inside.tester.org zone.

Author

Commented:
Thanks Everyone....

I've done exactly what DrDave242 suggested

Created a new zone,
Named the zone inside.tester.org
Create a new blank A record inside of the new zone and gave it the IP Address of the new Intranet.

Thanks for everyone's input