Nameserver help.

All the errors are listed in the wall of text from UniForum:
FQDN: ns1.synapticweb.co.za ==> [WARN: No A records!]
FQDN: ns1.synapticweb.co.za ==> [WARN: No AAAA records!]

FQDN: ns2.synapticweb.co.za ==> [WARN: No A records!]
FQDN: ns2.synapticweb.co.za ==> [WARN: No AAAA records!]
Just a warning - so you ignore it for now.
The SOA record for synapticweb.co.za at 173.0.52.199 can not be retreived.

! The most common reasons for this is that the Nameserver is not currently
! reachable or the Nameserver has not been configured for this domain.
I think thats self explanatory. Your ns1 is not responding to requests. Have you tested it to check?
;; The Nameserver "ns2.synapticweb.co.za." at IP "173.0.52.207"
;; does not have a reverse FQDN entry and as such will be rejected.
;; A 'dig -x 173.0.52.207' gives:-

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 34856
The rDNS for ns2 is not working. Where did you set it up? Have you tested that you ISP has propagated the change to their servers?
 
I have set up the rDNS and at time of testing it was working.

Will have to see again.

I have re submitted the application without ip6 to simplify the problems.

I have tried a few dig requests and all seemed fine. Not sure why it can't "find" the nameserver
 
Are you sure that the bind daemons are running on those 2 servers?

Code:
root@ns3 [~]# dig SOA synapticweb.co.za @173.0.52.207

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5_7.1 <<>> SOA synapticweb.co.za @173.0.52.207
;; global options:  printcmd
;; connection timed out; no servers could be reached

root@ns3 [~]# dig SOA synapticweb.co.za @173.0.52.199

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5_7.1 <<>> SOA synapticweb.co.za @173.0.52.199
;; global options:  printcmd
;; connection timed out; no servers could be reached
 
Are you sure that the bind daemons are running on those 2 servers?

Code:
root@ns3 [~]# dig SOA synapticweb.co.za @173.0.52.207

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5_7.1 <<>> SOA synapticweb.co.za @173.0.52.207
;; global options:  printcmd
;; connection timed out; no servers could be reached

root@ns3 [~]# dig SOA synapticweb.co.za @173.0.52.199

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5_7.1 <<>> SOA synapticweb.co.za @173.0.52.199
;; global options:  printcmd
;; connection timed out; no servers could be reached

Sorry the BIND server was down after a reboot yesterday. But I have had this problem for over a week now.

My dig request

[root@ns1 ~]# dig SOA synapticweb.co.za @173.0.52.199

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5_7.1 <<>> SOA synapticweb.co.za @173.0.52.199
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6886
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4

;; QUESTION SECTION:
;synapticweb.co.za. IN SOA

;; ANSWER SECTION:
synapticweb.co.za. 38400 IN SOA ns1.synapticweb.co.za. kevin.synapticweb.co.za. 1329176665 10800 3600 604800 38400

;; AUTHORITY SECTION:
synapticweb.co.za. 38400 IN NS ns1.synapticweb.co.za.
synapticweb.co.za. 38400 IN NS ns2.synapticweb.co.za.

;; ADDITIONAL SECTION:
ns1.synapticweb.co.za. 38400 IN A 173.0.52.199
ns1.synapticweb.co.za. 38400 IN AAAA 2604:c00:a:1:0:1:5c6:c62b
ns2.synapticweb.co.za. 38400 IN A 173.0.52.207
ns2.synapticweb.co.za. 38400 IN AAAA 2604:c00:a:1:0:1:380c:3045

;; Query time: 0 msec
;; SERVER: 173.0.52.199#53(173.0.52.199)
;; WHEN: Sun Feb 26 22:25:33 2012
;; MSG SIZE rcvd: 201
 
Are both these IPs on one server?? :wtf:

If you've fixed all the errors that where listed above then resubmit the DNS update.

For now yes, haven't bothered with setting up another server for redundancy yet.

Will start on that when the DNS update is accepted. Have to wait 24 hours for their automated system. Hope it works! Thanks
 
Ok so the DNS updated and this is the error I get now. Any ideas?

The domain update request for synapticweb.co.za has been suspended until
the DNS errors are resolved.

The problem/s are as follows:-

Checking Nameservers for synapticweb.co.za...
2 Nameservers specified:-
ns1.synapticweb.co.za, ns2.synapticweb.co.za.

Syntax/Cross-Checking provided info for Nameserver at 6a: ns1.synapticweb.co.za @ 173.0.52.199
IPv4: 173.0.52.199 ==> ns1.synapticweb.co.za.
FQDN: ns1.synapticweb.co.za ==> [WARN: No A records!]

Syntax/Cross-Checking provided info for Nameserver at 6e: ns2.synapticweb.co.za @ 173.0.52.207
IPv4: 173.0.52.207 ==> [WARN: No PTR records!]
FQDN: ns2.synapticweb.co.za ==> [WARN: No A records!]

! The message "No PTR records?" indicates that the reverse domain
| information has not been configured correctly.


! The message "No A records?" means that name of the Nameserver specified can not be resolved.
! This can be ignored if the specified Nameserver is a child of the
| domain application.


NS1-1 FQDN: ns1.synapticweb.co.za.
NS1-1 IPV4: 173.0.52.199
NS1-1 ORIGIN: ns1.synapticweb.co.za.
NS1-1 E-MAIL: [email protected].
NS1-1 SER-NO: 1329176665
NS1-1 NS RECORD1: ns1.synapticweb.co.za.
NS1-1 NS RECORD2: ns2.synapticweb.co.za.


;; The Nameserver "ns2.synapticweb.co.za." at IP "173.0.52.207"
;; does not have a reverse FQDN entry and as such will be rejected.
;; A 'dig -x 173.0.52.207' gives:-

; <<>> DiG 9.7.0-P1 <<>> -x 173.0.52.207
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 657
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;207.52.0.173.in-addr.arpa. IN PTR

;; Query time: 341 msec
;; SERVER: 206.223.136.205#53(206.223.136.205)
;; WHEN: Tue Feb 28 04:20:08 2012
;; MSG SIZE rcvd: 43

NS2-1 FQDN: ns2.synapticweb.co.za.
NS2-1 IPV4: 173.0.52.207
NS2-1 ORIGIN: ns1.synapticweb.co.za.
NS2-1 E-MAIL: [email protected].
NS2-1 SER-NO: 1329176665
NS2-1 NS RECORD1: ns1.synapticweb.co.za.
NS2-1 NS RECORD2: ns2.synapticweb.co.za.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ERROR: Not all nameservers found (Found 1 of 2) - suspending request.
!
! The suspended request will be checked every 8 hours for 5 days.
! Please re-check your dns configuration. It is not necessary to re-submit this application.
--------------------------------------------------------------------

Coza Support
 
Last edited:
; <<>> DiG 9.7.0-P1 <<>> -x 173.0.52.207
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 657
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
Your reverse DNS is still broken. You cannot fix this yourself - only your service provider can.

Your service provider has 2 servers authoritative for the rDNS zone: NS101.VIRPUS.COM & NS202.VIRPUS.COM. These two servers are sending inconsistent replies to queries.
 
Your reverse DNS is still broken. You cannot fix this yourself - only your service provider can.

Your service provider has 2 servers authoritative for the rDNS zone: NS101.VIRPUS.COM & NS202.VIRPUS.COM. These two servers are sending inconsistent replies to queries.

I'm failing to understand how they managed to screw that up 2 times. Both times they told me they set it. Guess I'm off to query them again. Thanks for the input!
 
Top
Sign up to the MyBroadband newsletter
X