Paul Walsh
asked on
Internal DNS entry
Hi,
We have a domain abc.local and a website that is not hosted by ourselves as abc.co.uk. We have an internal server running a web based platform that is working fine, however we would like it to be accessible via a more user friendly name 9URL) as server.abc.co.uk. When we add the name server.abc.co.uk to our local dns, the user friendly name works fine, however we then cannot access our website abc.co.uk internally. How do we add the entry so that the web server and our external website are both accessible?
Incidentally we will be publishing the web server externally. Once this has been done do we even need the internal dns entry to give it a more user friendly url?
Cheers,
Paul
We have a domain abc.local and a website that is not hosted by ourselves as abc.co.uk. We have an internal server running a web based platform that is working fine, however we would like it to be accessible via a more user friendly name 9URL) as server.abc.co.uk. When we add the name server.abc.co.uk to our local dns, the user friendly name works fine, however we then cannot access our website abc.co.uk internally. How do we add the entry so that the web server and our external website are both accessible?
Incidentally we will be publishing the web server externally. Once this has been done do we even need the internal dns entry to give it a more user friendly url?
Cheers,
Paul
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
create another primary zone in your DNS for abc.co.uk
add two A records in it.
1. abc.co.uk pointing you actual (external hosting IP).
2. server.abc.co.uk which should point your internal web server's IP.
so, when internally when you query for server.abc.co.uk it should return by external IP.
add two A records in it.
1. abc.co.uk pointing you actual (external hosting IP).
2. server.abc.co.uk which should point your internal web server's IP.
so, when internally when you query for server.abc.co.uk it should return by external IP.
When we add the name server.abc.co.uk to our local dns, the user friendly name works fine, however we then cannot access our website abc.co.uk internally.
Did you do this by adding a zone named abc.co.uk and a host record named server in that zone? If so, that's what's causing this behavior. Delete that zone and instead add a zone named server.abc.co.uk, then create a blank host record within the zone and give that record the IP address of the server. This way, only the name server.abc.co.uk will be resolved by that zone, while other *.abc.co.uk names will still use external DNS for resolution.
Edit: I just realized that this is the same thing Chris posted above. He's correct.
You said, "When we add the name server.abc.co.uk to our local dns, the user friendly name works fine, however we then cannot access our website abc.co.uk internally."
This is likely because you have 2x DNS configs fighting with each other.
Fast way to resolve this is to only use one public DNS config + change all your local DNS to caching only.
This gives you the speed of local lookups with zero headaches of conflicting DNS configs.
This is likely because you have 2x DNS configs fighting with each other.
Fast way to resolve this is to only use one public DNS config + change all your local DNS to caching only.
This gives you the speed of local lookups with zero headaches of conflicting DNS configs.
Fast way to resolve this is to only use one public DNS config + change all your local DNS to caching only.
That won't work with their internal domain, though. AD requires an internal DNS infrastructure, and I would be really hesitant, if not downright opposed, to putting that on a public DNS server.
This means you only have one set of DNS servers + records to manage.
Using this approach dramatically simplifies DNS setup + ongoing maintenance, especially you'll reduce your debugging time to zero... because DNS will just work.