We host one web app on our server and the domain for this app is registerd at our isp and also the DNS records are there.
From our company computers the app is accessible via internal IP (let’s say IP A), and the outside adrress for this server is sometihg else (let’s call it IP B).
What I want is that the domain for the app is resolved into ip A, when we are browsing on our company computers.
So when I sit at my company computer I want get the following:
- thing.com -> ip B (our domain must still resolve into ip B)
- some.thing.com -> ip A (only this subdomain must resolve into ip
- no.thing.com -> ip B (any other subdomain for thing.com must resolve
into ip B)
We are runing windows 2008 server with AD and DNS installed.
If I add new zone “thing.com” under Forward Lookup Zones and then add A record for “some” which points to ip A, then it works as desired for “some.thing.com”, but for anything else it doesn’t.
Thank you very much for the help.
Add an authoritative zone for
some.thing.com, and create an
A record for
@ (windows DNS calls this “(same as parent folder)”) pointing to the internal address.
Requests for other records under thing.com will be forwarded or recursively looked up, as the server will only be authoritative for the
Leave a comment
- 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?
- Domain Administrators account policy (After PCI audit)