Secondary Dns issues

[OwenW]

Hi All,

I am using a kimsufi dedicated server with Centos + ISPConfig 3.

I have set up a domian name on the server which seems to be working, however after testing the dns with dnssy, I am receiving errors related to the secondry dns (ns.kimsufi.com).

My settings so far are:

Domain settings at registrar:
ns1.mydomain.co MY_SERVER_IP
ns.kimsufi.com IP_OF_NS_KIMSUFI_COM

Domain settings on server:
A ns1.mydomain.co. MY_SERVER_IP
A ns2.mydomain.co. IP_OF_NS_KIMSUFI_COM
NS mydomain.co. ns1.mydomain.co. 0
NS mydomain.co. ns2.mydomain.co. 0

Domain is added on Kimsufi/OVH manager:
mydomain.co DATE MY_SERVER_IP ns.kimsufi.com ACTIVE

When I do nslookup from my windows pc, using localhost dns (my home dns) I get the correct response (MY_IP)

When I do nslookup from my windows pc, using mydomain.co, i get the correct response (MY_IP)

When I do nslookup from my windows pc, using NS.KIMSUFI.COM, i get
*** ns.kimsufi.com can't find mydomain.co: Server failed




What am I doing wrong? How do I get ns.kimsufi.com to serve as my secondary DNS?

Any help would be much apeciated,
Thanks,

Owen

[Neil]

Hi

If you have added the domain name in the OVH Manager under the Secondary DNS then you need to leave it 24/48 hours for it to update. If you have left this long and you still get an error, then try using the Dig command to see if it is active.

If it is not then please contact us and we will look into it.

[OwenW]

I added it to the OVH manager a few days ago, here is the output of dg:

[root@ksxxxxxx ~]# dig @ns.kimsufi.com

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> @ns.kimsufi.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 28973
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;. IN NS

;; Query time: 4 msec
;; SERVER: 213.186.33.199#53(213.186.33.199)
;; WHEN: Thu Nov 4 15:01:13 2010
;; MSG SIZE rcvd: 17


[root@ksxxxxxx ~]# dig @ns.kimsufi.com mydomain.co

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> @ns.kimsufi.com mydomain.co
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 50678
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;mydomain.co. IN A

;; Query time: 4 msec
;; SERVER: 213.186.33.199#53(213.186.33.199)
;; WHEN: Thu Nov 4 15:01:17 2010
;; MSG SIZE rcvd: 31

No answers from DIG... :(

[Neil]

Hi

It should work fine, but can you confirm that you have set 'allow-transfer'? Because if you query with XFR it does not return your DNS. I think you have allow-transfer set off.

[OwenW]

That was it, setting allow transfer to the ns.kimsufi.com IP cleared up he issue.

I am left with one warning on dnssy.com:

ns.kimsufi.com reported:
ns.kimsufi.com [no glue] TTL 3600
ns1.mydomain.co [MY_IP] TTL 3600


ns1.mydomain.co reported:
ns.kimsufi.com [213.186.33.199] TTL 3600
ns1.mydomain.co [MY_IP] TTL 3600

Is this lack of glue anything to worry about? Or should I just leave it how it is?

Thanks for the help,

Owen

[Neil]

Hi

Excellent news.

Nothing to worry about, just how the DNS Servers works.

[OwenW]

Perfect, thanks alot for the help :).