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

remote.mydomain.com sub domain issues

Hi all,

Quick question, if I  ping <servername> from inside the network I get

192.168.0.3 (which is correct).

If I ping remote.<ourdomain>.com from inside the network for some reason i get 192.168.0.2?

However is I access https://remote.<ourdomain>.com/remote from outside the network it load just fine?

TOp and bottom is when I am inside the network for some reason it is associating remote. with .0.2 instead os .0.3 what coudl be causing this redirection?
0
flynny
Asked:
flynny
  • 4
1 Solution
 
flynnyAuthor Commented:
oh an dby the way just to add I have checked the hosts file but this has nothing referencing it.
0
 
David Johnson, CD, MVPOwnerCommented:
check your dns records.

nslookup remote.domain.com should resolve to 192.168.0.3

There are ways within iis i.e. 301 redirect  to have remote.domain.com point to 192.168.0.2 and the webserver on 192.168.0.2 redirect all requests to 192.168.0.3
0
 
flynnyAuthor Commented:
@ve3ofa

if i nslookup form RDP on the server it is resolving to 192.168.0.2 rather than .0.3

where do i check to change this in IIS please?
0
 
flynnyAuthor Commented:
Hi i have managed to resolve it with you help.

There was a forward lookup zone redirecting to .0.2.

I have ammended this to be .0.3
0
 
flynnyAuthor Commented:
many thanks for the prompt response.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

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