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

Dns to Point an ip-address to another IP address

Hi,

I'm trying to use the A-record in MS server 2008 R2 environment using DNS. I have an external IP address 192.168.156.232 pointing to an internal IP 10.62.90.2, which is our legacy IP-range.
I need the internal IP 10.62.90.2 to point to another Internal IP 10.80.20.12. from our new range , both IP ranges can communicate between each other. Any ideas how i can do this please?

ps. all the ipaddress are made up for security reasons.

Thank, AA
0
techaa
Asked:
techaa
  • 4
  • 2
  • 2
  • +1
1 Solution
 
PapertripCommented:
I'm not sure what you are asking.  You can't point 1 IP to another IP in DNS, you only point IP's to hostnames.

Can you explain your situation again please, and provide some records or config excerpts or something that can help us understand what you are trying to say.

Oh and to make things easier for us, if you are making up an external IP, please don't use RFC 1918 private address space, it's just confusing.
0
 
PapertripCommented:
You mentioned A record but I see no A record, all you are giving us for examples are IP's.
0
 
BCipolloneCommented:
Not sure what you are trying to do exactly, however you could make a CName for the IP you need and create a seperate name for it if thats what you are trying to do...
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows PowershellĀ® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Darius GhassemCommented:
Well you would need to setup IP forwarding within your network switches and routers to forward the old IP to new IP.
0
 
techaaAuthor Commented:
sorry for the delay in replying:

situation: last year our organisation changed and the new owners decide to migrate our domain to be part of a forest where we are a child domain:

I have limited information but I can confirm we had a range of 10.60.* .*(lets call is IP-1) before and now are on 10.70.*.*(call it IP-2)

to explain our current network: for e.g the terminal services server's external IP address (lets call it IP-ext) still points to an ip address from the old range(IP-1), but that is some-how forwarded to an IP address from the new range(IP-2). the TS server is on the new IP range(IP-2).

I found this out as when I pinged say 10.60.0.10(from IP-1), I get a reply from 10.70.0.11(the actual server address(from IP-2))
this is because our ISP provider will only publish to the old range.

I have installed a new Remote Desktop Gateway server and need to test it before I can go live: so I have got my ISP to publish an external IP-address(IP-ext) to an internal IP-address range (IP-1) and now I need to forward it(IP-1) to an actual server IP-address(IP-2) or the server domain name?

dariusg: i think you're pointing me to the right direction, can this be done on the DC/DNS server of does it have to go on the network/core switch?
any links to 'how to setup/configure IP forwarding' on HP switches will be fabulous :). tried searching on google but not much luck.

Thanks.
0
 
PapertripCommented:
the terminal services server's external IP address (lets call it IP-ext) still points to an ip address from the old range(IP-1)
so I have got my ISP to publish an external IP-address(IP-ext) to an internal IP-address range (IP-1)

I am thoroughly confused now.  What exactly is your ISP "publishing" and why are you mixing up external and internal IP's?  Does your ISP manage your router and setting up NAT for you?
0
 
techaaAuthor Commented:
i've attached a diagram on how it works, it atleast explains the network diagram for how the external connection is for the Remote logins. dodgy-connection-diagram.docx
0
 
PapertripCommented:
By that diagram, your ISP is doing NAT for you.  Why won't your ISP setup NAT to 10.70?  I can't think of any reason they wouldn't... they shouldn't care what private IP space you choose to use.
0
 
Darius GhassemCommented:
No, you can not setup DNS to forward from one domain to another. Port Forwarding starts when the user comes into the internal network from the external DNS request. When the user is external they get their IP address to access your TS server from the external DNS servers once they have the IP address DNS is out of the loop for good unless they hit a internal website that has another link to point to a different address
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

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