I have recently moved many of my accounts from another datacenter and am having problems with a reseller that I assigned private nameservers and a dedicated IP. I assigned a dedicated IP to this reseller so as to keep his separate from the rest of the customers on the server.
It seems that some of the resellers accounts are having problems resolving to the server when he adds new accounts.
Am getting the following error messages when using dnsreport.
FAIL Lame nameservers 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:
69.93.40.151
69.93.40.152
WARN Nameservers on separate class C's WARNING: All of your nameservers (listed at the parent nameservers) are in the same Class C (technically, /24) address space, which means that they are probably at the same physical location. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. RFC2182 3.1 goes into more detail about secondary nameserver location.
FAIL NS agreement on SOA Serial # ERROR: Your nameservers disagree as to which version of your DNS is the latest! 4294967295 versus 0! This is OK if you have just made a change recently, and your secondary DNS servers haven't yet received the new information from the master. I will continue the report, assuming that 0 is the correct serial #.
FAIL SOA MNAME Check ERROR: Your SOA (Start of Authority) record states that your master (primary) name server is: . However, that is not a valid domain name!
FAIL SOA RNAME Check ERROR: Your SOA (Start of Authority) record states that your DNS contact E-mail address in hostname format is: . However, that is NOT valid (it must have at least 2 '.''s in it and no '@')!
WARN SOA Serial Number WARNING: Your SOA serial number is: 0. That is OK, but the recommended format (per RFC1912 2.2) is YYYYMMDDnn, where 'nn' is the revision. For example, if you are making the 3rd change on 02 May 2000, you would use 2000050203. This number must be incremented every time you make a DNS change.
FAIL SOA REFRESH value WARNING: Your SOA REFRESH interval is : 0 seconds. This seems very low. You should consider increasing this value to about 3600-7200 seconds. RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours). A value that is too low will unncessarily increase Internet traffic.
FAIL SOA RETRY value WARNING: Your SOA RETRY interval is : 0 seconds. This seems very low. You should consider increasing this value to about 120-7200 seconds. The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.
FAIL SOA EXPIRE value WARNING: Your SOA EXPIRE time is : 0 seconds. This seems very low. You should consider increasing this value to about 1209600 to 2419200 seconds (2 to 4 weeks). RFC1912 recommends 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.
FAIL SOA MINIMUM TTL value WARNING: Your SOA MINIMUM TTL is : 0 seconds. This seems very low (unless you are just about to update your DNS). You should consider increasing this value to somewhere between 3600 and 10800. RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.
MX FAIL MX Category ERROR: I couldn't find any MX records for rxemployment.com. If you want to receive E-mail on this domain, you should have MX record(s). Without any MX records, mailservers should attempt to deliver mail to the A record for rxemployment.com. I can't continue in a case like this, so I'm assuming you don't receive mail on this domain.
Mail FAIL Connect to mail servers ERROR: I could not find any mailservers for rxemployment.com.
WWW FAIL WWW Category ERROR: I couldn't find any A records for
I did not forward a PTR request to servermatrix for the new nameservers as I never had to do that at my old datacenter.
I checked his accounts DNS records and they all seem fine.
I am using WHM on a cPanel box.
Is there anything special that needs to be done when assigning a dedicated IP to a reseller with private nameservers??