Lame nameservers

[benito]

Hi!

Those are my firsts experiences with DNS clustering on Cpanel. I have two servers running cpanel.

Server 1: ns1.example.com 1.1.1.1
Server 2: ns2.example.com 2.2.2.2

Everything looks fine and its working. DNS changes are replicated on each server, no rndc errors. But on dnsreports i get:

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: 2.2.2.2

How i can remove the Lame Nameservers error ? What i miss when i set my second dns server ?

[benito]

up to the roof.

[rhenderson]

Hi!

Those are my firsts experiences with DNS clustering on Cpanel. I have two servers running cpanel.

Server 1: ns1.example.com 1.1.1.1
Server 2: ns2.example.com 2.2.2.2

Everything looks fine and its working. DNS changes are replicated on each server, no rndc errors. But on dnsreports i get:

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: 2.2.2.2

How i can remove the Lame Nameservers error ? What i miss when i set my second dns server ?

The problem probably lies in the individual DNS zone settings for the domain in question.

[benito]

I solved the lame problem adding a line to named.conf:

server2:
listen-on { 2.2.2.2; };

But now, lame problem is fixed adding that line ! Now i only have two warns.

All nameservers report identical NS records: WARNING: At least one of your nameservers did not return your NS records (it reported 0 answers). This could be because of a referral, if you have a lame nameserver (which would need to be fixed).

2.2.2.2 returns 0 answers (may be a referral)

And

TCP Allowed: WARNING: One or more of your DNS servers does not accept TCP connections. Although rarely used, TCP connections are occasionally used instead of UDP connections. When firewalls block the TCP DNS connections, it can cause hard-to-diagnose problems. The problem servers are:

2.2.2.2: Error [Connection refused (10061)].

Maybe i need to work with my firewall.

[rhenderson]

I solved the lame problem adding a line to named.conf:

server2:
listen-on { 2.2.2.2; };

But now, lame problem is fixed adding that line ! Now i only have two warns.



And


Maybe i need to work with my firewall.

Sounds like you are on the right track, since the connection was refused.

[benito]

It fail even if my firewall are disabled, maybe i miss anything else on named.conf

[Jesepi]

I am also having this problem, it started 2 days ago out of nowhere... nothing on the server had been changed relating to DNS... I fixed my issue by downloading the site's files (all static pages and images, no dynamic content or databases) deleting the account, and then recreating it with the same settings as I used to set it up.

The bad thing is, today the same problem arose with yet another domain on the machine. I am trying to figure out what would be causing this if nobody is playing with the dns settings.

[Jesepi]

I fixed my issue, this is what I did:

- ssh into the server, and viewed /etc/named.conf
- did a search for the domain and found that it was not present in the file
- went to the bottom of the file and added:

zone "domainthatwasmissing.com" {
        type master;
        file "/var/named/domainthatwasmissing.com.db";
};

-saved and closed the file


-went and looked inside the /var/named directory and confirmed that there was a file that was called domainthatwasmissing.com.db

-ran the following:
scripts/restartsrv_named
scripts/restartsrv_bind


The site loads fine now

[XzaB]

I fixed my issue, this is what I did:

- ssh into the server, and viewed /etc/named.conf
- did a search for the domain and found that it was not present in the file
- went to the bottom of the file and added:

zone "domainthatwasmissing.com" {
        type master;
        file "/var/named/domainthatwasmissing.com.db";
};

-saved and closed the file


-went and looked inside the /var/named directory and confirmed that there was a file that was called domainthatwasmissing.com.db

-ran the following:
scripts/restartsrv_named
scripts/restartsrv_bind


The site loads fine now

is very weired from me to update thread since 2006
anyway I faced the same issue today on cPanel DNS Only, and it been fixed by same method as u said by using
WHM >> Synchronize DNS Records
Ticking for "Synchronize zones that are not configured on this server"