proteus-IV
asked on
Change IPs for NS records
I ported NS, MX and A records to new IPs from a range given by new ISP.
Then I disabled the old ISP link.
Now, I am unable to resolve hostnames which had their IP ported.
Should I leave the old WAN link from the old ISP enabled until DNS replicates across the world?
How does this work?
Will my DNS inform our new ISPs DNS of the IP adresses change and forward the new IPs
for NS and MX?
How long will it take to propagate the new NS IPs to the DNSs?
How do root DNSs update this info?
Then I disabled the old ISP link.
Now, I am unable to resolve hostnames which had their IP ported.
Should I leave the old WAN link from the old ISP enabled until DNS replicates across the world?
How does this work?
Will my DNS inform our new ISPs DNS of the IP adresses change and forward the new IPs
for NS and MX?
How long will it take to propagate the new NS IPs to the DNSs?
How do root DNSs update this info?
ASKER
I noticed that DNS only works when I enable the old WAN link and old NAT rules for old NS WAN IPs.
I did a check with intoDNS, it reported 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.
Also, dns2.mydomain.com reports (NO GLUE).
I also get a warning about recursive queries:
I could use the nameservers listed below to performe recursive queries. It may be that I am wrong but the chances of that are low. You should not have nameservers that allow recursive queries as this will allow almost anyone to use your nameservers and can cause problems.
I did a check with intoDNS, it reported 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.
Also, dns2.mydomain.com reports (NO GLUE).
I also get a warning about recursive queries:
I could use the nameservers listed below to performe recursive queries. It may be that I am wrong but the chances of that are low. You should not have nameservers that allow recursive queries as this will allow almost anyone to use your nameservers and can cause problems.
ASKER
@kenboonejr
How do I find out which authoritative DNS servers are handling my domain?
So, you are saying I have to contact the new ISP and tell them to update their DNS records
for my domain and from there they will propagate to the rest of the Internet?
How do I find out which authoritative DNS servers are handling my domain?
So, you are saying I have to contact the new ISP and tell them to update their DNS records
for my domain and from there they will propagate to the rest of the Internet?
what is your domain name?
ASKER
admiral.hr
ASKER
I tried checking for the NS record for my domain with an authoritative server for the .hr TLD.
dig +norec @hr-ns-1.carnet.hr. admiral.hr. NS
It is still pointing to the old ISP IP for dns1:
dns1.admiral.hr. 14440 IN A 195.29.163.228
dig +norec @hr-ns-1.carnet.hr. admiral.hr. NS
It is still pointing to the old ISP IP for dns1:
dns1.admiral.hr. 14440 IN A 195.29.163.228
Go to network-tools.com
On the left side click on DNS and down below in the space put in admiral.hr
Then hit go.
You will get these results:
Retrieving DNS records for admiral.hr...
DNS servers
dns2.admiral.hr
dns1.admiral.hr [195.29.163.228]
Answer records
admiral.hr A 31.45.244.77 3600s
admiral.hr NS dns3.admiral.hr 3600s
admiral.hr NS dns2.admiral.hr 3600s
admiral.hr NS dns1.admiral.hr 3600s
admiral.hr SOA
server: dns1.admiral.hr
email: hostmaster@admiral.hr
serial: 86
refresh: 900
retry: 600
expire: 86400
minimum ttl: 3600
3600s
admiral.hr MX
preference: 10
exchange: mail.admiral.hr
3600s
Authority records
Additional records
dns3.admiral.hr A 83.139.114.100 3600s
dns2.admiral.hr A 31.45.244.76 3600s
dns1.admiral.hr A 31.45.244.75 3600s
mail.admiral.hr A 31.45.244.77 3600s
So do you maintain these servers?
On the left side click on DNS and down below in the space put in admiral.hr
Then hit go.
You will get these results:
Retrieving DNS records for admiral.hr...
DNS servers
dns2.admiral.hr
dns1.admiral.hr [195.29.163.228]
Answer records
admiral.hr A 31.45.244.77 3600s
admiral.hr NS dns3.admiral.hr 3600s
admiral.hr NS dns2.admiral.hr 3600s
admiral.hr NS dns1.admiral.hr 3600s
admiral.hr SOA
server: dns1.admiral.hr
email: hostmaster@admiral.hr
serial: 86
refresh: 900
retry: 600
expire: 86400
minimum ttl: 3600
3600s
admiral.hr MX
preference: 10
exchange: mail.admiral.hr
3600s
Authority records
Additional records
dns3.admiral.hr A 83.139.114.100 3600s
dns2.admiral.hr A 31.45.244.76 3600s
dns1.admiral.hr A 31.45.244.75 3600s
mail.admiral.hr A 31.45.244.77 3600s
So do you maintain these servers?
ASKER
Yes, I maintain these:
dns3.admiral.hr A 83.139.114.100 3600s
dns2.admiral.hr A 31.45.244.76 3600s
dns1.admiral.hr A 31.45.244.75 3600s
mail.admiral.hr A 31.45.244.77 3600s
network-tools.com also reports old IP for dns1.admiral.hr:
dns1.admiral.hr [195.29.163.228]
dns3.admiral.hr A 83.139.114.100 3600s
dns2.admiral.hr A 31.45.244.76 3600s
dns1.admiral.hr A 31.45.244.75 3600s
mail.admiral.hr A 31.45.244.77 3600s
network-tools.com also reports old IP for dns1.admiral.hr:
dns1.admiral.hr [195.29.163.228]
So these are the authoritative domain servers for your domain. So now what needs to happen is the registrar for the admiral.hr domain needs to be notified of the new authoritative name server IP addresses.
ASKER
How do I notify the registrar about the change?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
If you did not change who is handling your authorative DNS servers then you simply need to submit your DNS changes for the A records so they point to the new IP addresses. This process is different for every provider out there. Some you can call the changes in, some you have to send an email, some let you do it through a web portal.
They always claim it takes 24 hours. This is due to the nature of how DNS propagates. However, most of it is ready within the first 30 minutes to 3 hours.
So what you do depends on if you are changing your authoritative name servers and whether you are changing your dns provider.
Your old ISP is not going to notify the new ISP of anything.