I have followed multiple online tutorials on setting this up, it is BIND9 on a debian server.

It is the only server I have, so it is acting as both ns1, ns1, and the server they domain name should point to itself.

It all appears to be working and when I dig the domain name from the server itself I get (what seems to me) the correct output:

; <<>> DiG 9.7.3 <<>> theonetekkit.com.au ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18593 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION: ;theonetekkit.com.au. IN A

;; ANSWER SECTION: theonetekkit.com.au. 3000 IN A 103.4.17.189

;; AUTHORITY SECTION: theonetekkit.com.au. 3000 IN NS ns1.theonetekkit.com.au. theonetekkit.com.au. 3000 IN NS ns2.theonetekkit.com.au.

;; ADDITIONAL SECTION: ns1.theonetekkit.com.au. 3000 IN A 103.4.17.189 ns2.theonetekkit.com.au. 3000 IN A 103.4.17.189

;; Query time: 15 msec ;; SERVER: 103.4.17.189#53(103.4.17.189) ;; WHEN: Wed Nov 7 02:12:58 2012 ;; MSG SIZE rcvd: 121

When I dig it from another server / computer, however, I am getting a problem:

; <<>> DiG 9.7.3 <<>> theonetekkit.com.au ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 56637 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION: ;theonetekkit.com.au. IN A

;; Query time: 22 msec ;; SERVER: 103.4.16.166#53(103.4.16.166) ;; WHEN: Wed Nov 7 02:12:40 2012 ;; MSG SIZE rcvd: 37

I have given it more than enough time for the records to be refreshed since setting up the DNS server, so I don't know what would be causing this.

Any ideas?

Thanks