Set routes to test domain joined computer as if it were off the network

So I changed the DNS of my machine at work to public DNS (I am remoted in to it).
Unfortunately, it is not acting exactly as it normally would if I had it at home.
When I do trace routes it times-out unlike as if it were at home.
Any steps I could take to make this work?

Thank you.
K BAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

traceroute has nothing to do with DNS checking. Traceroute acting at the IP level in the TCP/IP architecture, and DNS resides at the Application level of the TCP/IP architecture.

times outs in trace route can occurs when the route passes routers configured to not respond at ping (ICMP packets)
K BAuthor Commented:
I see.. At the same time the computer does not browse websites as it would from the outside.. any idea why?  Is it having to leave and then come back in?
What exactly did you do when you said "I changed DNS"?

Did you change the IP in a zone of a DNS server, or you changed the DNS IP of the network configuration?
Rowby Goren Makes an Impact on Screen and Online

Learn about longtime user Rowby Goren and his great contributions to the site. We explore his method for posing questions that are likely to yield a solution, and take a look at how his career transformed from a Hollywood writer to a website entrepreneur.

K BAuthor Commented:
I changed the name servers that the workstation uses for DNS resolution

Aha, perfect!

Can you ping and/or

If the answer is yes, can you telnet 53 and/or telnet 53 ?

53 is the port where your machine ask and for DNS request. if you cannot ping it is a connection issue or a firewall rule which forbid connection to Google's public DNS.

If you can ping but you cannot telnet, is definitely a forbidden rule in firewall which restrict port 53.

To see if it is a connection problem if the ping fails, try ping to an IP address from you ISP, preferable the Gateway IP which ISP provided to you
K BAuthor Commented:
I can successfully ping and telnet to both
K BAuthor Commented:
I can get to any public website except the internal site I am trying to test.
In this case it means that your internet site is just internal and not public on the Internet. To make it public, you have to add in the DNS in the zone of your domain an A record with an IP public address where the site responds
K BAuthor Commented:
It is publicly available on the Internet.
The record exists in DNS.
I can access it from my home computer.
can you ping from the server you just changed the DNS the site by name? How about pinging the IP public address of the site?
... you've just changed ...
K BAuthor Commented:
I can telnet to FQDN port 443 from home but not from the machine in question
Look at your local route table as well as your host file. You may need to add in a route in your route table and or edit your host file so that the machine on the inside can see your internal site. You may also want to check any potential NAT settings that may be in place.

K BAuthor Commented:
Anything NAT related would be a major undertaking with change requests.  Could you guide me with the static routes on my workstation however?
To view the IP routing table
Open A Command Prompt.

At the command prompt, type:

route print

Post your display
As long as telnet FDQN is not working:

- if ping FDQN is working, it is a firewall problem
- if ping FDQN is not working but ping IP is working, it is a DNS issue
 - if ping IP is not working it is a routing issue. In a CMD type netstat -r and see if there is a route to the site's IP class. If there is a route try to ping the gateway

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
K BAuthor Commented:
cannot ping to IP or FQDN from outside
cannot telnet (443) to IP or FQDN from inside (with public DNS manually entered)
CAN telnet (443) to IP or FQDN from inside (with normal DNS given out  by DHCP)
The IP that you can telnet with the DNS given by DHCP, is public or private?
K BAuthor Commented:
OK! The corresponding public address of the site is configured on the machine where the site resides, or is on a router which makes port forwarding to the private IP address?
As I figure so far: in your DNS it is a record of with a private address, but not a record with with a public address, or
the DNS where the zone configuration resides is not visible/accesibe from Internet

But: As long as you cannot ping IP_public_address from Internet, maybe you have a misconfiguration of IP_public_address or a misconfiguration of port forwarding

Best regards!
K BAuthor Commented:
I think that was a comment for another question Matrix?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Network Architecture

From novice to tech pro — start learning today.