Hello,

I'm having a bad week, therefore all these questions ;)

Please check this:
http://www.dnsreport.com/tools/dnsreport.ch?domain=ripnetwork.net


ERROR: You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame:
x.x.x.x
x.x.x.x


Does anyone know what the problem is?

According to WHM those nameservers are assigned.


I tried to restart Bind and I get this:


named started ok Dec 28 23:29:23 xxx named[3710]: shutting down Dec 28 23:29:23 xxx named[3710]: no longer listening on 127.0.0.1#53 Dec 28 23:29:23 xxx named[3710]: no longer listening on 83.149.65.205#53 Dec 28 23:29:23 xxx named[3710]: no longer listening on 83.149.65.206#53 Dec 28 23:29:23 xxx named[3710]: no longer listening on 83.149.65.207#53 Dec 28 23:29:23 xxx named[3710]: no longer listening on 83.149.65.208#53 Dec 28 23:29:23 xxx named[3710]: no longer listening on 83.149.65.209#53 Dec 28 23:29:23 xxx named[3710]: exiting Dec 28 23:29:23 xxx named: named shutdown succeeded Dec 28 23:29:24 xxx named[5916]: starting BIND 9.2.4rc6 -u named Dec 28 23:29:24 xxx named[5916]: using 4 CPUs Dec 28 23:29:24 xxx named[5916]: loading configuration from '/etc/named.conf' Dec 28 23:29:24 xxx named[5916]: no IPv6 interfaces found Dec 28 23:29:24 xxx named[5916]: listening on IPv4 interface lo, 127.0.0.1#53 Dec 28 23:29:24 xxx named[5916]: listening on IPv4 interface eth0, 83.149.65.205#53 Dec 28 23:29:24 xxx named[5916]: listening on IPv4 interface eth0:0, 83.149.65.206#53 Dec 28 23:29:24 xxx named[5916]: listening on IPv4 interface eth0:2, 83.149.65.207#53 Dec 28 23:29:24 xxx named[5916]: listening on IPv4 interface eth0:3, 83.149.65.208#53 Dec 28 23:29:24 xxx named[5916]: listening on IPv4 interface eth0:4, 83.149.65.209#53 Dec 28 23:29:24 xxx named: named startup succeeded Dec 28 23:29:24 xxx named[5916]: /etc/named.conf:19: couldn't install keys for command channel 127.0.0.1#953: not found Dec 28 23:29:24 xxx named[5916]: /etc/named.conf:19: couldn't add command channel 127.0.0.1#953: not found Dec 28 23:29:24 xxx named[5916]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700 Dec 28 23:29:24 xxx named[5916]: zone localhost/IN: loaded serial 42 Dec 28 23:29:24 xxx named[5916]: zone ripnetwork.net/IN: loaded serial 2004122804 Dec 28 23:29:24 xxx named[5916]: running Dec 28 23:29:24 xxx named[5916]: zone ripnetwork.net/IN: sending notifies (serial 2004122804) Dec 28 23:29:24 xxx named[5916]: received notify for zone 'ripnetwork.net'


Any idea? :confused:

Thanks


EDIT:

Btw this is inside my named.conf around line 19:

controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};

Hello,
That error is not an error when I click that link. It says "Pass" for me.

The only error mentioned there is RDNS for the MX records. Let us know if you need more help with that? or have you just fixed it now?

That's strange, I didn't change anything... :o

For the reverse DNS of the MX entries I have to contact my datacenter I guess? Or can I do it myself?

EDIT: Btw is it normal to receive the following error when I modify a zone file:


Bind reloading on xxx using rndc zone: [ripnetwork.net]
Error reloading bind on xxx: rndc: connect failed: connection refused


I restarted Bind myself, maybe that's why it was fixed: Bind doesn't restart automatically ?

Send an email to the datacenter with the details and they can set this up. Normally they have it set up already though but seems like in this case it is not.

Ok thank will do that :)
But I'm still concerned about the problem I stated in my previous post (I editted it, regarding the bind not reloading automatically)

Hello,
I am not sure with WHM as we use MS Windows for this so someone else will be able to help on that side of things.

Well I fixed it now. It seems like something was wrong with the rndc.conf file. This is really strange, normally with fresh WHM installs these things are already taken care of :\

Thanks for the help anyway :)