erastus@connect
Verified User
- Joined
- Jun 1, 2013
- Messages
- 36
an any one please help me. I did an IP change on DA
When I do this:
http://intodns.com/mpinsure.co.za
I get this:
Looks like the A records (the GLUE) got from the parent zone check are different than the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do.I detected some problems as follows:
For ns1.connect-at.net the parent reported: ['197.85.136.118'] and your nameservers reported: ['41.168.130.194']
For ns2.connect-at.net the parent reported: ['197.85.136.118'] and your nameservers reported: ['41.168.130.200']
This is the old ip 41.168.130.194 and 197.85.136.118 the new IP. Some how DA is not propagating the ip's
Why does this not get updated by DA after the IP change.
If I do a dig this is what I get: 197.85.136.114 is my server IP the old ip was 41.168.130.194
dig @197.85.136.114 www.mpinsure.co.za
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-25.P1.el5_11.6 <<>> @197.85.136.114 www.mpinsure.co.za
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25771
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;www.mpinsure.co.za. IN A
;; ANSWER SECTION:
www.mpinsure.co.za. 14400 IN A 41.168.130.194
;; AUTHORITY SECTION:
mpinsure.co.za. 14400 IN NS ns1.connect-at.net.
mpinsure.co.za. 14400 IN NS ns2.connect-at.net.
;; ADDITIONAL SECTION:
ns1.connect-at.net. 14400 IN A 41.168.130.194
ns2.connect-at.net. 14400 IN A 41.168.130.200
;; Query time: 0 msec
;; SERVER: 197.85.136.114#53(197.85.136.114)
;; WHEN: Fri Mar 18 10:14:39 2016
;; MSG SIZE rcvd: 134
[root@ns1 scripts]#
Regards
When I do this:
http://intodns.com/mpinsure.co.za
I get this:
Looks like the A records (the GLUE) got from the parent zone check are different than the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do.I detected some problems as follows:
For ns1.connect-at.net the parent reported: ['197.85.136.118'] and your nameservers reported: ['41.168.130.194']
For ns2.connect-at.net the parent reported: ['197.85.136.118'] and your nameservers reported: ['41.168.130.200']
This is the old ip 41.168.130.194 and 197.85.136.118 the new IP. Some how DA is not propagating the ip's
Why does this not get updated by DA after the IP change.
If I do a dig this is what I get: 197.85.136.114 is my server IP the old ip was 41.168.130.194
dig @197.85.136.114 www.mpinsure.co.za
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-25.P1.el5_11.6 <<>> @197.85.136.114 www.mpinsure.co.za
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25771
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;www.mpinsure.co.za. IN A
;; ANSWER SECTION:
www.mpinsure.co.za. 14400 IN A 41.168.130.194
;; AUTHORITY SECTION:
mpinsure.co.za. 14400 IN NS ns1.connect-at.net.
mpinsure.co.za. 14400 IN NS ns2.connect-at.net.
;; ADDITIONAL SECTION:
ns1.connect-at.net. 14400 IN A 41.168.130.194
ns2.connect-at.net. 14400 IN A 41.168.130.200
;; Query time: 0 msec
;; SERVER: 197.85.136.114#53(197.85.136.114)
;; WHEN: Fri Mar 18 10:14:39 2016
;; MSG SIZE rcvd: 134
[root@ns1 scripts]#
Regards
Last edited: