Web Troubleshooting: How to Find DNS IP and IP Location

As an IT professional, few tasks are more important than being able to quickly diagnose issues with web applications and internet-based services. Whether it‘s tracking down connectivity problems or analyzing suspicious traffic, having the right troubleshooting tools at your fingertips is essential.

In this guide, I‘ll provide a comprehensive overview of the two most important troubleshooting techniques: DNS lookups to find domain IPs and IP geolocation to identify location data. I‘ve been working in IT infrastructure for over 5 years, and these are the go-to tools I rely on for insights into DNS and IP behavior.

We‘ll cover:

• When to use DNS lookups vs IP geolocation
• Step-by-step guides for 2 recommended DNS tools
• Step-by-step guides for 2 recommended IP lookup tools
• Detailed examples and use cases for applying these techniques
• Extra tips for analyzing DNS and IP data

Follow along for everything you need to know to leverage DNS and IP lookups for web troubleshooting.

When to Use DNS Lookups vs IP Geolocation

DNS and IP lookups serve different but complementary purposes:

• DNS lookups resolve domain names to IP addresses. Use when troubleshooting connectivity issues reaching a domain.

• IP geolocation identifies an IP‘s geographic and ISP data. Use when inspecting traffic patterns or suspicious IP behavior.

Here‘s a breakdown of when to use each technique:

When to Use DNS Lookups

• Web application unable to connect to a domain/website
• APIs or integrations failing to reach an external domain
• Downloads timing out when contacting remote hosts
• "Unknown host" errors trying to resolve a domain name

These types of connection issues are often caused by DNS resolution problems. A DNS lookup will show you which IPs are tied to the domain to help diagnose.

When to Use IP Geolocation

• Uncover where website visitors are located
• Check if traffic is coming from expected locations
• Identify if requests are coming from suspicious regions
• Determine hosting provider/ISP of an IP address

IP lookups help uncover patterns about IPs contacting your apps and services. This reveals if traffic aligns with expectations or looks anomalous.

When to Use Both

Sometimes both DNS and IP analysis provides useful signals. For example, if your app has a spike in traffic from Russia, IP geolocation helps confirm the location. But DNS lookups on the reverse IP can also identify if it‘s a known server IP vs residential IP.

Combining these troubleshooting techniques gives you multiple data points to pinpoint issues.

Now let‘s dive into the recommended tools and walkthroughs for DNS and IP lookups.

Recommended DNS Lookup Tools

When troubleshooting DNS issues reaching a domain, the first step is identifying the IP addresses tied to that domain name. Here are two easy-to-use DNS lookup tools I recommend:

DNSWatch

DNSWatch is my top choice for fast DNS record lookups. Here‘s how to use it:

1. Go to DNSWatch
2. Enter the domain name
3. Click "Resolve"

You‘ll then see the DNS records, including the A record with IP addresses:

DNSWatch is incredibly fast – results pop in under a second. It‘s also simple and clutter-free.

Pros:

• Very fast DNS resolver
• Clean, straightforward interface
• Few ads/distractions

Cons:

• Only shows the basic DNS records
• No advanced query options

Overall, the speed and ease-of-use makes DNSWatch my go-to for most lookups.

Geekflare DNS Lookup

Geekflare‘s DNS Lookup tool is another solid option:

1. Go to Geekflare DNS Lookup
2. Enter domain name
3. Click "Lookup DNS"

It returns the key DNS records, including IPs:

Geekflare‘s tool has a simple design and is very user-friendly.

Pros:

• Easy-to-use browser-based tool
• Checks blocklists
• No ads

Cons:

• Slower than DNSWatch
• Less detailed than some advanced tools

Between DNSWatch for fastest lookups and Geekflare for blocklist checks, you‘re equipped to troubleshoot most DNS issues.

When to Use 3rd Party DNS Tools

For deeper analysis, tools like DNSLookup.io and Intodns offer advanced features:

• Query different record types like SSHFP, TLSA, SPF
• Analyze DNSSEC validation
• Debug zone transfers
• Validate mail server configs

However, for most troubleshooting, DNSWatch and Geekflare provide the essential A/AAAA records to identify domain IPs. The advanced tools are best for domain admins and security researchers.

Real-World DNS Lookup Examples

Let‘s walk through some real-world examples using DNS lookups to troubleshoot issues.

Example 1: API Failing to Connect

Your web app communicates with a 3rd party API at api.partner.com, but you notice intermittent timeouts and SSL errors. A DNS lookup for api.partner.com reveals 2 IPs, one of which is flagged as suspicious on blocklists.

This hints that the flagged IP is a problematic endpoint causing the API connectivity problems. You can report the finding to the partner.

Example 2: Malformed Domain

A customer reports they can‘t access your website. You ask them to check the URL entered. They try wwww.yourdomain.com (with 4 w‘s) which fails. You do a DNS lookup and get no records, proving it‘s an invalid domain causing the error.

Example 3: CDN Woes

Your site loads slowly despite using a CDN. Looking up the CDN domain shows just 2 IPs instead of many global IPs. This lack of diverse IP ranges indicates the CDN may not be configured properly. Engaging CDN support with your finding can help resolve the issue.

These examples demonstrate where DNS lookups can provide useful clues to get to the bottom of domain and connectivity issues.

Recommended IP Geolocation Tools

In addition to DNS analysis, IP geolocation lookups are indispensable for identifying key details about IP addresses. Here are my top 2 tools for this:

IPLocation

IPLocation is the gold standard for thorough IP geolocation. To use:

1. Go to IPLocation
2. Enter the IP address
3. Click "Lookup"

It then aggregates results from 5+ geolocation databases:

IPLocation taps into multiple sources to provide an extensive report:

• Country, region, city
• Latitude and longitude
• ISP and domain names
• Connection type (hosting provider, business, residential)
• Threat and usage reputation flags
• Precision radius in km

This level of detail allows deep analysis of IP patterns.

Pros:

• Data from 5+ geolocation databases
• Very granular into specific neighborhoods
• Identifies high risk IPs/VPNs

Cons:

• Slow compared to other tools
• Details can be overwhelming for basic lookups

For in-depth inspection, IPLocation is hard to beat. It compiles the most exhaustive data on IP locations and behavior.

Geekflare IP Lookup

For quick IP lookups, Geekflare‘s tool is ideal:

1. Go to Geekflare IP Lookup
2. Enter IP address
3. Hit "Lookup"

It displays core details like country, region, city, ISP, latency, and organization:

I like Geekflare for fast checks when I just need the high-level location info.

Pros:

• Very fast results
• Clean and mobile-friendly interface
• No ads or clutter

Cons:

• Less comprehensive than IPLocation
• Limited to core geolocation data

Geekflare IP Lookup is ideal for quick ad-hoc analysis. IPLocation provides deeper forensic analysis for high-risk IPs. Together they make a great troubleshooting toolkit.

When to Use Paid Tools

Premium IP geolocation tools like IP2Location and MaxMind offer enhanced data like:

• Carrier information
• Connection type classifications
• Detecting proxies and VPNs
• Granular demographics like organization size

Paid solutions can provide further nuanced insights, but are overkill for most troubleshooting needs. The free tools above give you 80% of the value for standard lookups.

Real-World IP Lookup Examples

Here are some examples of applying IP analysis to troubleshoot web apps:

Example 1: Suspicious Traffic Source

Your site has a spike in traffic from a Russian IP. An IP lookup reveals it‘s a hosting provider with mostly high risk clients. This adds credibility to the signals that the traffic looks bot-driven or otherwise suspicious.

Example 2: Web Scraping

Your app logs show repeated access attempts from an unfamiliar IP. A lookup indicates it‘s a residential broadband connection – unlikely to be a real user. This points to probable web scraping from that IP.

Example 3: Slow Office Users

Remote employees report slow connectivity to your web app. IP analysis reveals they‘re out of state on vacation, causing higher network latency from the hotel WiFi. This explains the temporary performance issue.

IP intelligence provides valuable context around suspicious or anomaly traffic patterns. It can validate your suspicions or offer surprises that lead to root cause identification.

Extra Tips for Using DNS and IP Data

Beyond the basic lookups, here are some pro tips for extra analysis:

Analyze DNS TTL

Check the TTL (time to live) in DNS records. Short TTLs like 60 seconds indicate dynamic/CDN IPs. Long TTLs like days suggest stable IPs.

Compare With Passive DNS

Services like PassiveTotal aggregate DNS data from across the internet. Comparing it with your lookup can identify changed IPs.

Enrich IP Context

Plug IP addresses into tools like AbuseIPDB and GreyNoise for reputation data.

Monitor Over Time

Repeated lookups can map DNS/IP changes and catch fresh domain names or IPs associated with issues.

Visualize IP Ranges

Plot out IP ranges from lookups on a geo map to spot suspicious concentrations of traffic.

These tips demonstrate how DNS and IP data can serve as powerful sources of evidence for troubleshooting when utilized creatively.

Conclusion

Quick access to DNS and IP intelligence provides tremendous advantages troubleshooting web applications and infrastructure. I hope this guide has equipped you with a methodology and toolset to leverage DNS and IP lookups effectively.

Here are some key takeaways:

• DNS lookups help diagnose domain and website connection issues by revealing IPs. Use DNSWatch and Geekflare‘s resolver for fast and easy lookups.

• IP geolocation identifies key details about IP locations and organizations to profile traffic sources. IPLocation and Geekflare‘s IP lookup provide thorough and fast analysis respectively.

• Complement basic lookups with extra techniques like analyzing TTLs, comparing with passive DNS, and monitoring over time to extract as much insight as possible from DNS and IP data.

With practice, you‘ll be able to pinpoint the exact causes behind web application problems much faster by combining smart DNS and IP analysis. Troubleshooting with data avoids guesswork so you can focus on permanent solutions.

Now you have no excuse not to level up your web troubleshooting skills with DNS and IP lookups! Let me know if you have any other questions. I‘m always happy to help fellow technologists master tools that make our jobs easier.