Accessing external terminal server name internally
We access our terminal server from outside the network via ts.domainname.com
Internally we use domainname.local
What do I need to do to make the internal clients be able to connect using the external name?
I found this thead is thei the answer?
https://www.experts-exchange.com/questions/23006462/Accessing-an-internal-webserver-with-an-external-domain-name.html
Internally we use domainname.local
What do I need to do to make the internal clients be able to connect using the external name?
I found this thead is thei the answer?
https://www.experts-exchange.com/questions/23006462/Accessing-an-internal-webserver-with-an-external-domain-name.html
Create a new domain/zone in DNS called "ts.domainname.com"
Create a A record where the name is blank (ie - uses the parent domain name)
Plug in the internal IP address
As an example below, I have done this using www.google.com as the zone name, this shows that it does not break normal name lookups for the rest of the zone as it is only for the domain name that you have entered:
C:\>nslookup www.google.com
Server: localhost
Address: 127.0.0.1
Name: www.google.com
Address: 192.168.230.131
C:\>nslookup google.com
Server: localhost
Address: 127.0.0.1
Non-authoritative answer:
Name: google.com
Addresses: 64.233.187.99, 64.233.167.99, 72.14.207.99
C:\>nslookup mail.google.com
Server: localhost
Address: 127.0.0.1
Non-authoritative answer:
Name: googlemail.l.google.com
Addresses: 66.249.83.83, 66.249.83.19
Aliases: mail.google.com
Create a A record where the name is blank (ie - uses the parent domain name)
Plug in the internal IP address
As an example below, I have done this using www.google.com as the zone name, this shows that it does not break normal name lookups for the rest of the zone as it is only for the domain name that you have entered:
C:\>nslookup www.google.com
Server: localhost
Address: 127.0.0.1
Name: www.google.com
Address: 192.168.230.131
C:\>nslookup google.com
Server: localhost
Address: 127.0.0.1
Non-authoritative answer:
Name: google.com
Addresses: 64.233.187.99, 64.233.167.99, 72.14.207.99
C:\>nslookup mail.google.com
Server: localhost
Address: 127.0.0.1
Non-authoritative answer:
Name: googlemail.l.google.com
Addresses: 66.249.83.83, 66.249.83.19
Aliases: mail.google.com
ASKER
Since I would like to also be able to access owa internally I should just created a zone that matches my external name with just those records (email server ip and ts server ip)?
It really depends, if you have A records in the external zone that are hosted externally (a lot of them), you may just want to create two internal zones, one for TS and the other for OWA, and configure appropriate blank A records in both zones.
What you do is entirely up to you.
What you do is entirely up to you.
ASKER
Thats right - everything hosted offsite would also have to be added to a single zone.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
BTW, if you actually create a zone called domainname.com, your server will end up being authorative for the whole zone, so you will need to fill the zone with all the records that exist in the external copy of the zone. Hence my feeling that it may be easier for you if you just create two new zones for OWA and TS only, this way your internal DNS will not be authorative for the domainname.com zone.
I thought i should write this as it puts some reasoning behind what i have listed above.
I thought i should write this as it puts some reasoning behind what i have listed above.
ASKER
Thank you good answer
ASKER