Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Relevant output:

/etc/hosts               localhost localhost.localdomain localhost4  localhost4.localdomain4
::1             localhost localhost.localdomain localhost6 localhost6.localdomain6
servers_ip_address   server

#Generated by NetworkManager

Some stuff from tcpdump

07:46:28.795843 IP server_ip.42841 > 60253+ PTR? (44)
07:46:28.795980 IP server_ip.54001 > 7390+ PTR? (43)
07:46:28.804029 IP server_ip.59667 > 58876+ PTR? (45)
07:46:28.884171 IP server_ip.46255 > 63027+ PTR? (45)
07:46:28.884217 IP server_ip.35426 > 10538+ PTR? (44)
07:46:28.884253 IP server_ip.53635 > 29928+ PTR? (43)
07:46:28.884286 IP server_ip.45787 > 41151+ PTR? (44)
07:46:28.946045 IP server_ip.47246 > 43103+ PTR? (43)
07:46:28.946066 IP server_ip.33208 > 61117+ PTR? (44)

Anyone have any input as to what is causing this?

share|improve this question
Can you paste the command you're running and the exact response. – EightBitTony Jun 11 '12 at 12:57
also add a nslookup – Mike Jun 11 '12 at 13:08
Ew. NetworkMangler. – Tom O'Connor Jun 11 '12 at 13:09
-1: This question is poorly worded and doesn't explain the actual problem is. I'd edit it myself to correct, but I can't really figure it out enough to even do that. I'll remove the minus one once the question is corrected to be clear enough to determine what it is actually asking. – Jed Daniels Jun 11 '12 at 14:29

I'm only seeing one-way traffic in that tcpdump, no responses. Did you specify only outbound DNS requests (say, dst port 53) or are you not getting any responses?

Can you make any DNS requests at all? (Use dig to test this.)

share|improve this answer
dig and nslookup always fail to connect to host no matter what arguments I use. this is the tcpdump command i used: tcpdump -n not port ssh and not port 4838 and not port 80 and not port 6667 I have stopped iptables, restarted and made sure port 53 was allowed etc. I can ping all IP addresses fine but no domains resolve. – Tar Jun 11 '12 at 13:45
Do you have a hardware firewall or does your hosting provider run one for you? That's what I'm leaning towards for the cause of this. Does your hosting provider also provide DNS servers? They might block DNS requests to any other DNS provider. Also, can you ping and – Ladadadada Jun 11 '12 at 13:50
Yes, I can ping them. It's weird because I've been using google DNS ever since we switched to this server like 2 months ago with no problems. I emailed them and asked about a default DNS server. My host does have a hardware firewall but I can't imagine why it would start happening just now. – Tar Jun 11 '12 at 13:57

I have two servers running Debian Squeeze with this configuration and everything if fine without using nslookup


Maybe you forgot to set a correct route.

share|improve this answer
Here is the output of route -n server_ip U 0 0 0 em1 U 1002 0 0 em1 server_ip UG 0 0 0 em1 – Tar Jun 11 '12 at 13:43

It is a problem reaching your DNS server or with return DNS packets. You can start debugging by running traceroute on the port 53/UDP:

traceroute -np 53

This will show if it is your local firewall or a remote problem.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.