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

What does the second address mean when I do a NSLOOKUP on my Citrix external URL?

Hello,

I'm troubleshooting my Citrix outside connection and I did a NSLOOKUP for citrix.myrapadocs.com and noticed that I got two addresses that responded. The 12.49.168.67 is correct, but what is the 68.178.232.99. Some of my users see that Citrix is trying to connect to that address and timeout, when it supposed to connect to 12.49.168.67. Anyone have any idea why this is happening?

This is the response I get when i nslookup citrix.myrapadocs.com

C:\Users\JaimeC.RAPA.000>nslookup citrix.myrapadocs.com
Server:  fileserver.rapa.local
Address:  192.168.1.2

Non-authoritative answer:
Name:    myrapadocs.com
Addresses:  12.49.168.67
          68.178.232.99
Aliases:  citrix.myrapadocs.com

Thanks,

nimdatx
0
Jaime Campos
Asked:
Jaime Campos
  • 3
  • 3
2 Solutions
 
pmannoCommented:
Looks like you have two A records in DNS.
0
 
Jaime CamposAuthor Commented:
What can I do to fix it? Would that be causing any issues?
0
 
Jan SpringerCommented:
Go into domaincontrol.com panel and remove the incorrect A record and then flush your DNS cache on your local machine.
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
Jaime CamposAuthor Commented:
I'm using Godaddy. Is that where I need to change/modify settings?
0
 
pmannoCommented:
Log in
Domain Manager
Click on the domain
Under "Total DNS" click on "Total DNS Control"

There you can create/modify/delete all your DNS records.
0
 
Jaime CamposAuthor Commented:
Got it. What errors could have this cause on the client side? Thanks.
0
 
pmannoCommented:
Typically none.  The creation of A records in DNS is usually a manual process (unless you've configured your clients to dynamically update DNS, then they'd have to be pointing to the godaddy DNS servers and they'd have to be authorized to make the changes, which is unlikely).  So somebody, at some point, probably created those records for you.  By doing a whois by ip address, I find that  68.178.232.99 is owned by godaddy.  Probably when you registered your domain name, some A records that point to godaddy servers were created automatically and they were never removed.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

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