Glue records?

T

turbo2ltr

Member
I am migrating a few sites from a KH VPS to a KH dedicated. The VPS had the private name servers ns1.example.com, ns2.example.com as well as hosted the web page at example.com

I moved everything over and it's runnig, but having some issues with dns propagation. I already had previously set TTLs for all domains to 5 minutes. in prep for the move. The issue is that the name servers IP's have changed. So I made sure that both the glue records (ns1, ns2 for the example.com record) on both the VPS and dedicated, both pointed to the new server. But running dns checks on it seems like the glue records haven't fully propagated despite the 5min TTL. IPs of both name servers (VPS and dedicated) are being queried. It has not been 24 hours yet, but I'm worried I did something wrong or didn't do something I needed to.

Both name servers have the correct records (records on the old VPS now point to the IP of the dedicated) so it's not really creating an access issue, but I want to be confident I can shut down the VPS name servers.. Is it just a matter of waiting?
 
Depending on your domain's registrar it usually takes around 15 minutes (can take longer) but the 24 hour window registrars give is really just so you don't contact them every 10 minutes. Did you change your NS ips on your registrars side (where your DNS hot records reside)? If you provide your name servers we can better help you. If you're concerned about security providing your NS it's nothing people could find out using your domain name anyways.
 
Nothing has changed at the registrar. The domain (registered at godaddy) points to my private name servers at the same domain. My understanding was the "glue" records in the domain's DNS record is what resolves the recursive nature of having name servers at the same domain. As far as godaddy knows, the domain's name servers haven't changed, they are still ns1 and ns2.

http://www.simpledns.com/lookup-dg.aspx

Code: 
Loading root server list (static data):
-> a.root-servers.net (198.41.0.4)
-> b.root-servers.net (192.228.79.201)
-> c.root-servers.net (192.33.4.12)
-> d.root-servers.net (128.8.10.90)
-> e.root-servers.net (192.203.230.10)
-> f.root-servers.net (192.5.5.241)
-> g.root-servers.net (192.112.36.4)
-> h.root-servers.net (128.63.2.53)
-> i.root-servers.net (192.36.148.17)
-> j.root-servers.net (192.58.128.30)
-> k.root-servers.net (193.0.14.129)
-> l.root-servers.net (199.7.83.42)
-> m.root-servers.net (202.12.27.33)
Sending request to "h.root-servers.net" (128.63.2.53)
Received referral response - DNS servers for "com":
-> a.gtld-servers.net (192.5.6.30)
-> b.gtld-servers.net (192.33.14.30)
-> c.gtld-servers.net (192.26.92.30)
-> d.gtld-servers.net (192.31.80.30)
-> e.gtld-servers.net (192.12.94.30)
-> f.gtld-servers.net (192.35.51.30)
-> g.gtld-servers.net (192.42.93.30)
-> h.gtld-servers.net (192.54.112.30)
-> i.gtld-servers.net (192.43.172.30)
-> j.gtld-servers.net (192.48.79.30)
-> k.gtld-servers.net (192.52.178.30)
-> l.gtld-servers.net (192.41.162.30)
-> m.gtld-servers.net (192.55.83.30)
Sending request to "f.gtld-servers.net" (192.35.51.30)
Received referral response - DNS servers for "christiansfitnessfactory.com":
-> ns2.christiansfitnessfactory.com (67.222.4.103)
-> ns1.christiansfitnessfactory.com (67.222.3.103)
Sending request to "ns1.christiansfitnessfactory.com" (67.222.3.103)
Received authoritative (AA) response:
-> Answer: A-record for christiansfitnessfactory.com = 209.236.126.155
-> Authority: NS-record for christiansfitnessfactory.com = ns1.christiansfitnessfactory.com
-> Authority: NS-record for christiansfitnessfactory.com = ns2.christiansfitnessfactory.com
-> Additional: A-record for ns1.christiansfitnessfactory.com = 209.236.126.155
-> Additional: A-record for ns2.christiansfitnessfactory.com = 209.236.126.156

67.222.x.103 are the old name servers. You can see the record it replies with has the correct NS records pointing to the new server at the 209 IP (retrieved from the OLD name server)

So it seems like the TLD server f.gtld-servers.net is not updating it's ns1/ns2 resolutions....?
 
Seems you've done more work than is necessary for creating NS records on GoDaddy. All that's necessary is go on GoDaddy, manage your domains, click on christiansfitnessfactory.com, under the settings tab there's "Host Names", click on the manage link beneath it, if you don't already have them created there click ADD HOSTNAME and add NS1 with IP address 209.236.126.155, then NS2 with IP address 209.236.126.156. Nothing else is needed. There's no need to edit any of the DNS records/ZONE FILE. Then when you migrate to a new server all that's needed is changing those IPs.
 
I already have the name server *domain names* defined for the domain at godaddy (I haven't touched it as the domain names of the name servers never changed). Godaddy does not allow you to define IP addresses with the domain names, just domain names as name servers.

"Edit Nameservers" only allows me to change the domain name of the name server.
 

Attachments

  • Capture.PNG
    Capture.PNG
    25.6 KB · Views: 749
You must log in or register to reply here.
Top