Used to work but now it doesnt ???

Hello,

I have a RedHat system running primary DNS for my domain eziekiel.com, well at least it use to. I have secondary backup DNS being done by easydns.com. Im running 9.2.1.

I have a firewall in front of this machine with static IP but have port forwarding setup & am confidant this is not the cause of problem. I see named running still as a process & dont see any errors in logs or on start of service. But checking, say online DNS checking at dnsreports.com i am getting multiple errors concerning my domain.
I used to see port 53 listening on say 127.0.0.1 & the internal IP it is runnig on 192.16.8.0.2 but now i dont see this.
Also if i do a nslookup of a domain i get the following

[root@echelon root]# dig mx www.iprimus.com.au

Server: 127.0.0.1
Address: 127.0.0.1#53

** server can't find www.iprimus.com.au: SERVFAIL


What can i send through to help anyone here resolve this for me..

Kind Regards

Andrew

Is 203.134.64.67 your server? Cause it appears to work fine. If that's not your server, what is the address of your server? Also, please attach your named.conf (don't paste).

Thankyou,

No that IP is not mine that is just a domain i was attempting to dig to show the type of failure i am getting (IPRIMUS)

Mine is ns.eziekiel.com & static IP attached to my connection is 220.233.6.187. Port 53 hits tthis machine (a firewall) & than port forwards it to an internal 192.168.0.2 machine internal to network.

Used to be fine & now service is started but named is not functioning.

named.conf in zip format attached below


Thanks

Andrew

Your named.conf looks like it was generated by something. It doesn't do a good job.

Now to gather some information. I want you to paste the results to this command:

ps -Af | grep 'named'

And this command:

netstat -an | grep '53'

And finally this command:

named -u named -g

ps -Af | grep 'named'

named 18030 1 0 17:15 ? 00:00:00 named -u named
named 18032 18030 0 17:15 ? 00:00:00 named -u named
named 18033 18032 0 17:15 ? 00:00:00 named -u named
named 18034 18032 0 17:15 ? 00:00:00 named -u named
named 18035 18032 0 17:15 ? 00:00:00 named -u named

netstat -an | grep '53'

tcp 0 0 192.168.0.2:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN
udp 0 0 192.168.0.2:53 0.0.0.0:*
udp 0 0 127.0.0.1:53 0.0.0.0:*

named -u named -g

Jun 28 17:23:25.160 starting BIND 9.2.1 -u named -g
Jun 28 17:23:25.161 using 1 CPU
Jun 28 17:23:25.172 loading configuration from '/etc/named.conf'
Jun 28 17:23:25.207 no IPv6 interfaces found
Jun 28 17:23:25.207 listening on IPv4 interface lo, 127.0.0.1#53
Jun 28 17:23:25.209 binding TCP socket: address in use
Jun 28 17:23:25.209 listening on IPv4 interface eth0, 192.168.0.2#53
Jun 28 17:23:25.209 binding TCP socket: address in use
Jun 28 17:23:25.216 couldn't add command channel 127.0.0.1#953: address in use
Jun 28 17:23:25.216 ignoring config file logging statement due to -g option
Jun 28 17:23:25.219 zone 0.0.127.in-addr.arpa/IN: loaded serial 2004040509
Jun 28 17:23:25.221 zone 0.168.192.in-addr.arpa\032/IN: loaded serial 2004040509
Jun 28 17:23:25.224 zone eziekiel.com/IN: loaded serial 2004041905
Jun 28 17:23:25.224 running
Jun 28 17:23:25.225 zone eziekiel.com/IN: sending notifies (serial 2004041905)
Jun 28 17:23:25.228 zone 0.168.192.in-addr.arpa\032/IN: sending notifies (serial 2004040509)
Jun 28 17:23:25.230 zone 0.0.127.in-addr.arpa/IN: sending notifies (serial 2004040509)

Ok now let's see the results for this command:

dig @192.168.0.2 eziekiel.com any

[root@echelon root]# dig @192.168.0.2 eziekiel.com any

; <<>> DiG 9.2.1 <<>> @192.168.0.2 eziekiel.com any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46504
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 11, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;eziekiel.com. IN ANY

;; ANSWER SECTION:
eziekiel.com. 86400 IN A 220.233.6.187
eziekiel.com. 86400 IN SOA NS.eziekiel.com. hostmaster.ezie
kiel.com. 2004041905 10800 3600 604800 86400
eziekiel.com. 86400 IN NS ns1.easyDNS.com.
eziekiel.com. 86400 IN NS ns2.easyDNS.com.
eziekiel.com. 86400 IN NS remote1.easyDNS.com.
eziekiel.com. 86400 IN NS remote2.easyDNS.com.
eziekiel.com. 86400 IN NS remote3.easyDNS.com.
eziekiel.com. 86400 IN NS NS.eziekiel.com.
eziekiel.com. 86400 IN MX 50 mail.optusnet.com.au.
eziekiel.com. 86400 IN MX 25 mail.eziekiel.com.
eziekiel.com. 86400 IN TXT "Eziekiel Design"

;; ADDITIONAL SECTION:
NS.eziekiel.com. 86400 IN A 220.233.6.187
mail.eziekiel.com. 86400 IN A 220.233.6.187

;; Query time: 3 msec
;; SERVER: 192.168.0.2#53(192.168.0.2)
;; WHEN: Mon Jun 28 18:55:25 2004
;; MSG SIZE rcvd: 337

Hello

Just for abit more information these are some latest logs from named. Do you think this would indicate a problem with my firewall that has my external IP. Im trying to treat rhis as a troubleshooting challenge but it can become quite annoying so thanks for your help


Jun 28 20:18:19.934 general: debug 1: zone 0.0.127.in-addr.arpa/IN: skipping load: master file older than last load
Jun 28 20:18:19.935 general: debug 1: zone 0.168.192.in-addr.arpa\032/IN: skipping load: master file older than last load
Jun 28 20:18:19.935 general: debug 1: zone eziekiel.com/IN: skipping load: master file older than last load
Jun 28 20:18:19.935 general: debug 1: dns_zone_maintenance: zone eziekiel.com/IN: enter
Jun 28 20:18:19.935 general: debug 1: dns_zone_maintenance: zone 0.168.192.in-addr.arpa\032/IN: enter
Jun 28 20:18:19.935 general: debug 1: dns_zone_maintenance: zone 0.0.127.in-addr.arpa/IN: enter
Jun 28 20:18:19.935 general: debug 1: dns_zone_maintenance: zone version.bind/CH: enter
Jun 28 20:18:19.935 general: debug 1: dns_zone_maintenance: zone version.bind/CH: enter
Jun 28 20:18:19.936 notify: debug 1: zone 0.168.192.in-addr.arpa\032/IN: notify to 220.233.6.187#53 failed: operation canceled
Jun 28 20:18:19.937 notify: debug 1: zone 0.0.127.in-addr.arpa/IN: notify to 220.233.6.187#53 failed: operation canceled

Well it seems pretty obvious to me what's wrong. I've taken ya every step of the way. We confirmed it's running, we confirmed it's bound and listening to the right ports, we've seen no errors in the startup messages, and we've successfully made a request for a domain that's being hosted.

It's most definately router or firewall related. Well, I suppose it could be ISP blockage related too.

Hi There,

I seem to be slowly getting things happening but i have to pain you with some more questions.

My resolv.conf file had the following

domain eziekiel.com
search eziekiel.com
nameserver 127.0.0.1
nameserver 192.168.0.2

With only this in it i could not ping a host name but as soon as i add 192.168.0.1 which is the internal interface of my firewall which is assigned DNS servers of my DSL provider it started working. Also say i do a dig. If i remove 192.168.0.1 & just leave my DNS IP's (127.0.0.1 & 192.168..0.2) it hangs & comes back with

dig mx bmw.com

; <<>> DiG 9.2.1 <<>> mx bmw.com
;; global options: printcmd
;; connection timed out; no servers could be reached

& i get status: SERVFAIL,

Can you give me an educated guess on why

Again this is firewall related problems. Add this to your named.conf in the "options" block.

query-source address * port 53;
notify-source * port 53;
transfer-source * port 53;

Then you can use the BIND dns server as your resolver.