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

clients unable to resolve internal DNS address's that point to another location

Hello,

I have internal users who are unable to resolve internal IP address's which are A records that point them to systems that run at our remote site. I am unable to ping or tracert to the internal address's. However if I change the A record entry and route over the internet it is okay and they can connect. When I attempt to do a nslookup on my client I am receiving this, which I have never seen before.

C:\Users\Seth>nslookup
21.63.70.10.in-addr.arpa
        primary name server = localhost
        responsible mail addr = nobody.inval
        serial  = 1
        refresh = 600 (10 mins)
        retry   = 1200 (20 mins)
        expire  = 604800 (7 days)
        default TTL = 10800 (3 hours)
Default Server:  UnKnown
Address:  10.70.63.21

Thank you
0
sethendres
Asked:
sethendres
1 Solution
 
kevinhsiehCommented:
Your nslookup syntax is wrong. If you want the A record, just do 'nslookup hostname.domain.tld'. If you want the reverse lookup, do 'nslookup 10.70.63.21'.

You tried to do a lookup on a non-existant zone.
0
 
wdurrettCommented:
For the ping and tracert, please take a look at the firewalls between the two sites and make sure there is a tunnel and route set up.
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

Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

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