DNS - replicate an external address in network

Olleco
Olleco used Ask the Experts™
on
We have a server that I want to add a DNS for testing:

- Example server:   IP: 1.1.1.1  
- I want to call it Server.domain.co.uk (domain.co.uk being our external facing domain name)
- Our current AD domain is called company.local
- Eventually we will open our firewall to let the traffic from the internet through (after testing service)

I want to route all internal people to the server direct in our network and to be able to use our SSL cert.  I could add another zone (domain.co.uk) but this messes up our connections to other services e.g. our website that is controlled externally.

Looking for helpful ideas...

Kind regards
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
AlexSenior Infrastructure Analyst

Commented:
This doesn't entirely make sense.

So you have an external domain Server.external.co.uk

You want to route all internal users to your internal server

Server.internal.co.uk


What I don't understand is why you don't just use the internal server hostname to get them to go there.  If you wanted to route

Server.external.co.uk to server.Internal.co.uk you can just use a CName.
yo_beeDirector of Information Technology

Commented:
I would rather create a new Zone on your internal DNS server called domain.co.uk instead of a CNAME. Once created you will need to add your A Records for the internal servers.

All your internal calls will first go to the internal DNS and if it is not found then it will forward to your DNS forwarders.

https://docs.microsoft.com/en-us/windows-server/networking/technologies/ipam/create-a-dns-zone

I find this to be a much more controlled method as well as organized.
OllecoTechy

Author

Commented:
yo_bee  this is what I expected (I created the DNS zone) to happen but it then it didn't send on requests if address not resolved e.g. it would not resolve out to the internet page.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Commented:
If you don't want conflicts with the public DNS records, don't add domain.co.uk , but add Server.domain.co.uk.
OllecoTechy

Author

Commented:
Hi Kimputer

This would work except for how would I add the DNS record e.g. it would be server.server.domain.co.uk pointing to my internal server (sorry this makes sense in my head)

Is there a way to make all addresses under server.domain.co.uk go to the internal server?

Thanks
yo_beeDirector of Information Technology

Commented:
In my environment I have the original domain.local that is populated automatically. I then created domain.com and manually created A Records for each of the servers that I wanted to have resolved.  In those A records this is where I entered either the internal IP or External.

e.g.
www.domain.com is public so i created the new A Record under my new zone and populated it with the public IP.  Now for the servers that I need to get to internally as well as when I am external I created the A Record with the internal IP on this zone and when the user left the environment  their DNS call would be handled by what ever DNS they are connected to outside the environment


I hope that makes sense.
Commented:
There would be a server.server.domain.co.uk if you'd create a server.domain.co.uk zone, with an extra A record for server . If you create an A record for the root, server.domain.co.uk will point to that server you want.
OllecoTechy

Author

Commented:
Very helpful.

Just having the ability to run things by someone and ending up with such a simple answer is perfect!

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial