AlphaLolz
asked on
identifying failures to resolve names to addresses on Redhat Linux.
We're having a problem with resolving a name to an address with a Linux apps. We have an activity where we're moving images from one company network to another. We have been trying to ensure all references to domain names have been changed, but we're still getting an error and so we're thinking we've missed one (or more). Is there something that can trap attempts to resolve a name to an address we can turn on or check (either on our server or the network)? I'm not even sure if a sniffer might help, but we're looking for any ideas that people may have.
Well the program doing the moving needs to resolve the name, and should complain when it can't.
There is no "official" method to trap failures.
What you could do is scan the network packets for port 53 udp (DNS queries) and all responses that have failures filtered out using f.e. wireshark.
There is no "official" method to trap failures.
What you could do is scan the network packets for port 53 udp (DNS queries) and all responses that have failures filtered out using f.e. wireshark.
ASKER
There is no program moving anything. People moved the server.
Does Wireshark exist for Linux?
Does Wireshark exist for Linux?
ASKER
sorry, I checked on Linux myself. That's a possibility.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We may need to do this, however we've also been making other changes with input from Oracle (this is for an Oracle product) that may be negating the need or resolving an issue elsewhere that is causing this problem. TBD.
ok np. good luck solving the moving issues.
Already closed, but from within Linux you can run tcpdump (as root) for a while and store the captured data in a file.
Then use Wireshark to load the capture file and look for DNS requests that fail, or possible other issues like connects that fail to non-existing ip addresses.
Then use Wireshark to load the capture file and look for DNS requests that fail, or possible other issues like connects that fail to non-existing ip addresses.
ASKER