Quote:
Originally Posted by billymayday
I thought that may be the case.
Are you sure there isn't a rndc.conf somewhere? Try
find / -type f -name 'rndc.conf*'
|
Yes I tried already. Please refer to posting #4 above.
I wonder whether use it as mentioned on the said posting or just leaving "rndc.key file NOT found ...." pending unsolved. The DNS server is working and has been checked on;
http://www.intodns.com/
with following info/warning/error indicated;
Parent
(i) Domain NS records
Code:
Nameserver records returned by the parent servers are:
ns43.domaincontrol.com. ['216.69.185.22'] [TTL=172800]
ns44.domaincontrol.com. ['208.109.255.22'] [TTL=172800]
m.gtld-servers.net was kind enough to give us that information.
NS
1)
(i) - NS records from your nameservers
Code:
NS records got from your nameservers listed at the parent NS are:
ns43.domaincontrol.com ['216.69.185.22'] [TTL=3600]
ns44.domaincontrol.com ['208.109.255.22'] [TTL=3600]
2)
(i) - Glue for NS records
Code:
INFO: GLUE was not sent when I asked your nameservers for your NS records.This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS records. The nameservers without glue are:
208.109.255.22
216.69.185.22
You can fix this for example by adding A records to your nameservers for the zones listed above.
SOA
(i) - SOA record
Code:
The SOA record is:
Primary nameserver: ns43.domaincontrol.com
Hostmaster E-mail address: dns.jomax.net
Serial #: 2007111300
Refresh: 28800
Retry: 7200
Expire: 604800 1 weeks
Default TTL: 86400
MX
1)
(i) - MX Records
Code:
Your MX records that were reported by your nameservers are:
10 xen02.satimis.com 220.232.213.178
20 smtp.secureserver.net -> CNAME(s) -> 208.109.80.149 (no glue)
30 mailstore1.secureserver.net 64.202.166.11 (no glue)
[These are all the MX records that I found. If there are some non common MX records at your nameservers you should see them below. ]
2)
MX CNAME Check
Code:
WARNING: CNAME was returned for the following MX records:
smtp.secureserver.net
The CNAME(s) that were returned are listed above. This is not ok per the RFCs and can cause problems including mail being lost!
3)
MX A request returns CNAME
Code:
WARNING: MX records points to a CNAME. CNAMEs are not allowed in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3. The problem MX record(s) are:
mailstore1.secureserver.net points to ['smtp.where.secureserver.net']
smtp.secureserver.net points to ['smtp.where.secureserver.net']
This can cause problems
4)
Reverse MX A records (PTR)
Code:
ERROR: No reverse DNS (PTR) entries. The problem MX records are:
178.213.232.220.in-addr.arpa -> no reverse (PTR) detected
You should contact your ISP and ask him to add a PTR record for your ips
WWW
(i) - WWW A Record
Code:
Your www.satimis.com A record is:
www.satimis.com -> satimis.com -> [ 220.232.213.178 ]
[Looks like you have CNAME's]
Any advice about their fix? TIA
satimis
