View Single Post
Old 10-06-2010, 13:54   #8
Ignitionnet
Inactive
 
Join Date: Jun 2008
Location: Leeds, West Yorkshire
Age: 47
Posts: 13,995
Ignitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny stars
Ignitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny stars
Re: Traceroute lookup reversing the IP address

Quote:
Originally Posted by Turkey Machine View Post
Hi guys, wonder if the nerds out there can help with the following query that's left me a bit braindead.

What could be the cause of an IP address being reversed when it has a traceroute performed against it?

As an example, IP address 208.69.34.231 comes up in the traceroute as 231.34.69.208.

This is having problems with domain resolution for a SMTP server one of my colleagues uses to work from home.

And just to clarify, this is happening with DNS lookups, not just traceroutes.

Any ideas chaps and lasses?

Thanks in advance

TM
This is fine, apart from one thing - they missed a bit out.

They put in a pointer record to pass a forward-confirmed reverse DNS check however they forgot the .in-addr.arpa bit at the end.

Get him to flush his DNS cache, if the correct DNS information has been input since it should then work ok.
Ignitionnet is offline   Reply With Quote