BIND 9 giving problems...

[rpmws]

I have 5 cases like this now ...all different ISPs. I rebuilt the zones and same thing.

[4web-space]

Bind gives those problems all too frequently why doesnt CPanel use a tried and tested DNS like DJBDns. It doesnt require patching every five minutes. It runs via daemon tools and is so much faster and reliable. We have already switched all our Plesk boxes to this and noticed the differences immediately.

We were getting b+ reports from dnsstuff.com now we get A+ most of the time.

Robbie
4web-space.com

[furquan]

hi 4-web space

I am using cpanel with bind 9 and facing the same probs,
So, can u tell me as to how do i replace my Bind with DjBdns and to what version.

If you could mention the procedures that you took to do replacement it will be great.

Thanks/-

[jamesbond]

It seems I had the same problem.

One person couldn't connect to one of my domains, I checked the zone file and it seemed fine.

He could reach the other domains on the server though.
I restarted BIND, and the next day the domain resolved for him...

It's not clear to me what the cause is of these problems with domains not resolving.
I did notice many non CPanel providers are switching to djbdns.
Maybe CPanel should follow the same path.

[ThunderHostingDotCom]

This thread goes back to Aug. Has anyone put in a bug for this and if not WHY?

If the problem seems to go away after restarting BIND couldn't we setup a cron to restart BIND say like every morning at 2 or 3am?

[JustinK]

As in stormtroopers example, we've found that adding A records for the nameservers to the dns zone helps. Basically the nameservers being used need to match to the nameservers set in the dns zone and A records for the nameservers need to exist in the main domain's zone file.

[vinc_dc43]

I was experiencing the same issues / problems where the primary / master DNS server would resolve domains and the secondary and tertiary domain servers wouldn't.

I think the problem is related to a combination of issues:

1 - bind 9
2 - the hostname being a user domain that is hosted on the same machine
3 - the hostname domain SOA pointing to third party DNS servers.

ultimately i resolved the issue by putting the A record for the ns1, ns2, ns3 server into the respective domain zone file ... and syncing it across the three servers.

i hope this makes sense!

essentially if your hostname is:

server1.domain.com and domain.com is a user account on your server, a zone would have been ccreated for it. Simply add the A records for ns1.domain.com and so on and so forth into your zone file.

perhaps people can follow this up and confirm it

[resellerscpanel]

Hello friends.
I am trying to set up a new server and I am getting strange errors.
The zone whcih I am trying to set up is
punchserver.com

Everything is working fine.All the steps which are taken are similar to what we usually do.
when I check the DNS zone file information at dnsreport.com . I get the following

Your SOA record [TTL=0] is:
Primary nameserver:
Hostmaster E-mail address:
Serial #: 0
Refresh: 0
Retry: 0
Expire: 0
Default TTL: 0
-----------------------------


This is strange since when I check from DNS edit zone I am able to see the SOA records in proper order.

all values are set but it seems that the information is not propogated properly.


Let me know if anyone can help me.

Thanks

Resellerscpanel
http://www.resellerscpanel.com

[salubrium]

**I've tried to make this as simple, detailed and straightforward as possible

Ok, we had the same problem as everyone else. First it started with one user and an MX record playing up. We are just resellers and were getting no response from our hosts.. Should I mention their name?

We fixed that by redirecting the MX record to another server and redirecting the clients to collect mail from that server...

Ok then today ALL ACCOUNTS INACCESSIBLE.. The $#% hit the fan.

When you go to www.dnsstuff.com and do a DNSLookup for the A record you might get the following:

How I am searching:
Searching for A record for mydomain.com at c.root-servers.net: Got referral to A.GTLD-SERVERS.NET. [took 102 ms]
Searching for A record for mydomain.com at A.GTLD-SERVERS.NET.: Got referral to ns1.mynameserver.com. [took 54 ms]
Searching for A record for mydomain.com at ns1.mynameserver.com.: Server failure! [took 98 ms].

Answer:
Server failure. There's a problem with the DNS server for mydomain.com.

Resolution:

In WHM, go to

DNS Functions->Edit Zone Templates (it will or should look like below)

; cPanel %cpversion%
; Zone file for %domain%
$TTL %ttl%
@ IN SOA %nameserver%. %rpemail%. (
%serial% ; serial, todays date+todays
14400 ; refresh, seconds
7200 ; retry, seconds
3600000 ; expire, seconds
86400 ) ; minimum, seconds

%domain%. IN NS %nameserver%.
%domain%. IN NS %nameserver2%.
%domain%. IN NS %nameserver3%.
%domain%. IN NS %nameserver4%.

%domain%. IN A %ip%

localhost.%domain%. IN A 127.0.0.1

%domain%. IN MX 0 %domain%.

mail IN CNAME %domain%.
www IN CNAME %domain%.
ftp IN CNAME %domain%.


Then you need to know the name and IP address of your nameservers so you can modify your template to look like this

; cPanel %cpversion%
; Zone file for %domain%
$TTL %ttl%
@ IN SOA %nameserver%. %rpemail%. (
%serial% ; serial, todays date+todays
14400 ; refresh, seconds
7200 ; retry, seconds
3600000 ; expire, seconds
86400 ) ; minimum, seconds

%domain%. IN NS %nameserver%.
%domain%. IN NS %nameserver2%.
%domain%. IN NS %nameserver3%.
%domain%. IN NS %nameserver4%.

ns1.yournameserver.com 14400 IN A 69.57.130.108
ns2.yournameserver.com 14400 IN A 69.57.130.109

%domain%. IN A %ip%

localhost.%domain%. IN A 127.0.0.1

%domain%. IN MX 0 %domain%.

mail IN CNAME %domain%.
www IN CNAME %domain%.
ftp IN CNAME %domain%.

Notice the two lines

ns1.yournameserver.com 14400 IN A 69.57.130.108
ns2.yournameserver.com 14400 IN A 69.57.130.109

**Change the DETAILS to YOUR NAME SERVER'S ADDRESSES.

Then SAVE the template.

Now, what you have to do is this (I suggest doing it on the least most important account first and testing it by trying to access it and also at www.dnsstuff.com)

So in WHM, go to DNS Functions->Delete a DNS Zone (remember choose the least most important account for testing)

and the Delete it

Now go to DNS Functions->Add a DNS Zone and choose the account you just deleted, and also type the domain name and the ipaddress of your server (the one you are connected to now. If you don't know it, just go to command line and type: ping yourdomain.com (replacing yourdomain.com with your actual domain )and it will list the ip address)

Repeat the Delete and Create procedure for all your accounts (testing each along the way)

If it doesn't work and you break the thing, don't blame me but if it works.. all praise welcome

[resellerscpanel]

Hello,

I am happy that I have a better network to host my server. This was a problem with one of my client.

We have resolved the error now but thanks for a nice explanation.

You are welcome to post this in the knowledgebase at

http://www.resellerscpanel.com/community/index.php


Thanks,

Resellerscpanel
Get 45 days free reseller plan.
Beta testers invited.