• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 894
  • Last Modified:

Windows DNS redirect

Hey everyone,

I am trying to make a static A record entry for a single domain, that is served by our domain controller, however I want all other entries for that domain, to go to an external DNS server (the normal route).

Basically:

(static record on domain controller) blah.internal.com -> 192.168.1.1
(request external DNS) blah2.internal.com -> 66.61.53.13
(request external DNS) blah3.internal.com -> 66.61.53.14

So basically only that first entry is served to internal clients as the internal IP, for everyone other entry, it queries external DNS, like normal. It is basically the equivalent of adding that static entry to everyone's LMHOSTS file... there may be another/better way to do it, so let me know :) Or if it is even possible.
0
malken00
Asked:
malken00
  • 2
1 Solution
 
markpalinuxCommented:

I had looked for this a year or two ago, what I found was that it was.....

Not possible to do this with Microsoft DNS. I think bind has options for different setups, however no not in MS DNS. Bind has a concept of client views.

With MS DNS you either are authoritative for the domain, or not authoritative.

Like you said maybe a hosts file, just remember if you have laptops how things would work if the user is internal or external to the network.

Mark
0
 
KCTSCommented:
What are you trying to achieve ? Perphaps there is a better way ?
0
 
markpalinuxCommented:

You could of course leave the blah.internal.com in DNS  if you just have a single entry that you want to have which has only an internal non-routed IP address.
10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255


(static record on domain controller) blah.internal.com -> 192.168.1.1
(request external DNS) blah2.internal.com -> 66.61.53.13
(request external DNS) blah3.internal.com -> 66.61.53.14

The problem would come when you want to use the same name for a host and would need to publish different IP addresses for internal and external.

In that case you would need to lookup split brian dns. if you google for that you will see some answers.

What I would suggest, if the number of external DNS records is small < 100,
then for external dns let an outside company host the external dns -

1) like your name registar  (godaddy.com, netsol.com, etc)
2) a company that focus on dns - dnsmadeeasy.com or others.
3) your isp

Most have workable dns management via a browser, in the old days or older ISPs have you log tech support tickets - which complicated things when you wanted a change.

That way the only dns servers you need to worry about is your internal one. This configuration would fall under the split brian setup.

Hope this helps,
Mark
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now