How can an internal DNS server work in relation to a domain name we currently own?
If my company’s website is
example.com and it currently points to a DNS server elsewhere that points to the website’s server, also elsewhere… how does it work to set up locally available addresses?
For example: We have 3 development servers and 3 staging servers. I would like each to point to:
something.example.com somethingelse.example.com etc...
However this only needs to be available locally, each available on… 192.168.0.XXX
Note: I doubt I can point the external DNS server back to my local servers since I do not have a static IP to address these properly.
Is this possible to set up? How does it work, conceptually? Any information on the subject that could help me understand this would be greatly appreciated.
What you need to set up (called by any other name) is split horizon DNS.
- Internal DNS Server’s Interactions with Local Client Computers… How do they work?
- DHCP: How can I forward DNS requests to an internet DNS server but serve local DNS requests from a local DNS server?
- BIND9 forwarders not working. Internal DNS resolves but doesn’t forward requests it can’t process
- Update internal DNS server in my organization
- How can I set up a local nameserver and modify DNS zones on it?
Leave a comment
- Understanding redundant power supplies
- Is there a way for administrators to disable users from installing Firefox extensions?
- Is there research material on NTP accuracy available?
- How to create a limited “domain admin” that does not have access to domain controllers?
- Can Windows RDC admin users be immune from being kicked?