Solved

Reverse DNS look up error loop?

Posted on 2007-03-28
10
555 Views
Last Modified: 2008-02-01
For some reason when I do a reverse DNS look up on DNSstuff.com, I get an error saying "It looks like you've stuck me in a loop."  

How can I fix it?  I have called our ISP to set it up and they said it has  been done.
0
Comment
Question by:ITcrowd
  • 6
  • 4
10 Comments
 
LVL 70

Expert Comment

by:Chris Dent
Comment Utility

It depends what's wrong.

The message implies that you never get anything more than referrals to other DNS servers when trying to get the answer.

Are you willing to post the IP so we can try it out?

Chris
0
 

Author Comment

by:ITcrowd
Comment Utility
sure I trust you guyz,  the IP is 69.4.191.155.
0
 
LVL 70

Accepted Solution

by:
Chris Dent earned 250 total points
Comment Utility

Ohh yeah that's quite nasty.

The problem is quite a long way up the chain, either the delegation for the IP range is wrong on the ARIN servers, or Level3.net are missing the zone.

Your ISP will have to pass it up the chain for you which is helpful. I suspect your ISP probably have done what they needed to, I would be very very surprised if you were being served by level3 directly, so the problem will be a tier or two up from your ISP.

You can try contacting the NOC (Network Operations Centre) for Level 3 directly, but I'm not too sure that'll be an easy thing to do.

Chris
0
 
LVL 70

Expert Comment

by:Chris Dent
Comment Utility

Oh and make sure that when you contact your ISP that you make clear it's looping between ARIN and Level3.net, perhaps give them a copy of your output from dnsstuff:


Asking e.root-servers.net for 155.191.4.69.in-addr.arpa PTR record:  
       e.root-servers.net says to go to indigo.arin.net. (zone: 69.in-addr.arpa.)
Asking indigo.arin.net. for 155.191.4.69.in-addr.arpa PTR record:  
       indigo.arin.net [192.31.80.32] says to go to ns1.level3.net. (zone: 191.4.69.in-addr.arpa.)
Asking ns1.level3.net. for 155.191.4.69.in-addr.arpa PTR record:  
       ns1.level3.net [209.244.0.1] says to go to K.ROOT-SERVERS.NET. (zone: (root))
Asking K.ROOT-SERVERS.NET. for 155.191.4.69.in-addr.arpa PTR record:  
       k.root-servers.net [193.0.14.129] says to go to indigo.arin.net. (zone: 69.in-addr.arpa.)
Asking indigo.arin.net. for 155.191.4.69.in-addr.arpa PTR record:  
       indigo.arin.net [192.31.80.32] says to go to ns2.level3.net. (zone: 191.4.69.in-addr.arpa.)
Asking ns2.level3.net. for 155.191.4.69.in-addr.arpa PTR record:  
       ns2.level3.net [209.244.0.2] says to go to M.ROOT-SERVERS.NET. (zone: (root))
Asking M.ROOT-SERVERS.NET. for 155.191.4.69.in-addr.arpa PTR record:  
       m.root-servers.net [202.12.27.33] says to go to figwort.ARIN.NET. (zone: 69.in-addr.arpa.)
Asking figwort.ARIN.NET. for 155.191.4.69.in-addr.arpa PTR record:  
       figwort.arin.net [192.42.93.32] says to go to ns1.level3.net. (zone: 191.4.69.in-addr.arpa.)
Asking ns1.level3.net. for 155.191.4.69.in-addr.arpa PTR record:  
       ns1.level3.net [209.244.0.1] says to go to D.ROOT-SERVERS.NET. (zone: (root))
Asking D.ROOT-SERVERS.NET. for 155.191.4.69.in-addr.arpa PTR record:  
       d.root-servers.net [128.8.10.90] says to go to epazote.ARIN.NET. (zone: 69.in-addr.arpa.)
Asking epazote.ARIN.NET. for 155.191.4.69.in-addr.arpa PTR record:  
       epazote.arin.net [192.41.162.32] says to go to ns2.level3.net. (zone: 191.4.69.in-addr.arpa.)
Asking ns2.level3.net. for 155.191.4.69.in-addr.arpa PTR record:  
       ns2.level3.net [209.244.0.2] says to go to L.ROOT-SERVERS.NET. (zone: (root))
Asking L.ROOT-SERVERS.NET. for 155.191.4.69.in-addr.arpa PTR record:  
       l.root-servers.net [198.32.64.12] says to go to indigo.arin.net. (zone: 69.in-addr.arpa.)
Asking indigo.arin.net. for 155.191.4.69.in-addr.arpa PTR record:  
       indigo.arin.net [192.31.80.32] says to go to ns1.level3.net. (zone: 191.4.69.in-addr.arpa.)
Asking ns1.level3.net. for 155.191.4.69.in-addr.arpa PTR record:  
       ns1.level3.net [209.244.0.1] says to go to M.ROOT-SERVERS.NET. (zone: (root))
Asking M.ROOT-SERVERS.NET. for 155.191.4.69.in-addr.arpa PTR record:  
       m.root-servers.net [202.12.27.33] says to go to henna.ARIN.NET. (zone: 69.in-addr.arpa.)
Asking henna.ARIN.NET. for 155.191.4.69.in-addr.arpa PTR record:  
       henna.arin.net [192.26.92.32] says to go to ns2.level3.net. (zone: 191.4.69.in-addr.arpa.)
Asking ns2.level3.net. for 155.191.4.69.in-addr.arpa PTR record:  
       ns2.level3.net [209.244.0.2] says to go to B.ROOT-SERVERS.NET. (zone: (root))
Asking B.ROOT-SERVERS.NET. for 155.191.4.69.in-addr.arpa PTR record:  
       b.root-servers.net [192.228.79.201] says to go to epazote.ARIN.NET. (zone: 69.in-addr.arpa.)
Asking epazote.ARIN.NET. for 155.191.4.69.in-addr.arpa PTR record:  
       epazote.arin.net [192.41.162.32] says to go to ns1.level3.net. (zone: 191.4.69.in-addr.arpa.)
Asking ns1.level3.net. for 155.191.4.69.in-addr.arpa PTR record:  
       ns1.level3.net [209.244.0.1] says to go to B.ROOT-SERVERS.NET. (zone: (root))

Error: It looks like you've stuck me in a loop!.


Chris
0
 

Author Comment

by:ITcrowd
Comment Utility
Wow, is it really that complicated?  My ISP says there''s nothing we can do but wait.  I'm just making efforts to speed up the process.  I've been calling them twice, everyday to get an update, but nothing has changed for the past whole week when I called in the request for the reverse DNS
0
Do You Know the 4 Main Threat Actor Types?

Do you know the main threat actor types? Most attackers fall into one of four categories, each with their own favored tactics, techniques, and procedures.

 
LVL 70

Expert Comment

by:Chris Dent
Comment Utility

Helpful of them, it's entirely possible that something is being setup, but I'm not convinced, they're just not that slow.

Unless they have definate grounds for doing it differently, as far as I can see it should be raised with your ISP's ISP. Doesn't leave you in a very helpful position though.

Chris
0
 

Author Comment

by:ITcrowd
Comment Utility
OK it looks like they finally fixed it.  But I still can't email AOL.  

I did a test email to ipconfirm@postmaster.aol.com and I got a

"Your connecting IP is: 69.4.191.154" This is our Firewall IP

How can I get my exchange server to connect with  69.4.191.155? THis is my Exchange external IP

Please help
0
 
LVL 70

Expert Comment

by:Chris Dent
Comment Utility

That's down to your Firewall, afraid I can't help too much with that aspect I'm afraid.

I believe you need to configure it so it translates the internal IP of the Exchange to the Public IP and sends out traffic with that as a source. Basically, NAT in the other direction (outbound as well as inbound).

Chris
0
 

Author Comment

by:ITcrowd
Comment Utility
Thanks for your help Chris!  Yah it was a setting on my Firewall that I forgot to configure.

Im just happy I that the Reverse DNS is working now!
0
 
LVL 70

Expert Comment

by:Chris Dent
Comment Utility

Great stuff :)

Chris
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Join & Write a Comment

Please see preceding article here: http://www.experts-exchange.com/Networking/Operating_Systems/A_11209-Root-Bridge-Election.html Figure 1 After Root Bridge has been elected, then what?..... Let's start by defining a Root Port in la…
A quick step-by-step overview of installing and configuring Carbonite Server Backup.
Viewers will learn how to properly install and use Secure Shell (SSH) to work on projects or homework remotely. Download Secure Shell: Follow basic installation instructions: Open Secure Shell and use "Quick Connect" to enter credentials includi…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now