Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have problem with bind server configuration.

​Result for lookup on 8.8.4.4:

root@server1:~# dig @8.8.4.4 webexamplesite.com

; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> @8.8.4.4 webexamplesite.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 5563
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;webexamplesite.com.            IN  A

;; Query time: 2428 msec
;; SERVER: 8.8.4.4#53(8.8.4.4)
;; WHEN: Sat Feb 15 15:16:02 2014
;; MSG SIZE  rcvd: 30

Result for lookup on 182.64.31.121

root@server1:~# dig @182.64.31.121 webexamplesite.com

; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> @182.64.31.121 webexamplesite.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11402
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;webexamplesite.com.            IN  A

;; ANSWER SECTION:
webexamplesite.com.     14400   IN  A   182.64.31.121

;; AUTHORITY SECTION:
webexamplesite.com.     14400   IN  NS  ns1.webexamplesite.com.
webexamplesite.com.     14400   IN  NS  ns2.webexamplesite.com.

;; ADDITIONAL SECTION:
ns1.webexamplesite.com. 14400   IN  A   182.64.31.121
ns2.webexamplesite.com. 14400   IN  A   182.64.31.121

;; Query time: 1 msec
;; SERVER: 182.64.31.121#53(182.64.31.121)
;; WHEN: Sat Feb 15 15:17:39 2014

also checked for port 53 for checking firewall access.

   sweb@sweb-laptop:~$ telnet 182.64.31.121 53
    Trying 182.64.31.121...
    Connected to 182.64.31.121.
    Escape character is '^]'.

Firewal config

root@server1:~# iptables -F ; iptables -X ; iptables -P INPUT ACCEPT ; iptables -P FORWARD ACCEPT ; iptables -P OUTPUT ACCEPT
root@server1:~# iptables-save 
# Generated by iptables-save v1.4.14 on Sat Feb 15 15:22:39 2014
*filter
:INPUT ACCEPT [7:508]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [4:592]
COMMIT
# Completed on Sat Feb 15 15:22:39 2014
# Generated by iptables-save v1.4.14 on Sat Feb 15 15:22:39 2014
*nat
:PREROUTING ACCEPT [37:2400]
:INPUT ACCEPT [1004:70326]
:OUTPUT ACCEPT [11:760]
:POSTROUTING ACCEPT [11:760]
-A PREROUTING -d 182.64.31.121/32 -p udp -m udp --dport 53 -j REDIRECT --to-ports 1194
-A POSTROUTING -s 10.8.0.0/24 -j SNAT --to-source 182.64.31.121
COMMIT
# Completed on Sat Feb 15 15:22:39 2014

What's my problem?

share|improve this question
1  
What are those NAT rules for? –  Michael Hampton Feb 15 at 14:26
    
@MichaelHampton Idont know i just want to completly deactive my firewall for check issue. how can i do this. That command gave from some debian admin server for reset iptables rules –  sweb Feb 15 at 14:28

1 Answer 1

Try to use netstat to figure out what's listening on port 1194

netstat -tlpne

and if it's not a DNS service make sure to remove this suspicious nat with:

iptables -D PREROUTING -d 182.64.31.121/32 -p udp -m udp --dport 53 -j REDIRECT --to-ports 1194
share|improve this answer
    
iptables: Bad rule (does a matching rule exist in that chain?) –  sweb Feb 15 at 18:54
    
sorry I forgot you must add "-t nat" eg, before -D... –  alxgomz Feb 15 at 21:24

Your Answer

 
discard

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.