ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Quick question: because I think I messed up.

    IT Discussion
    8
    12
    658
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • popesterP
      popester
      last edited by

      Do the Name Server records over ride other records like the SOA records? I have changed the name server records for my godaddy domain which makes DNS unmanageable through their interface. I have the records present in on the hosted name server but I am getting no indication that traffic is being redirected. ???!!!

      ObsolesceO 1 Reply Last reply Reply Quote 1
      • ObsolesceO
        Obsolesce @popester
        last edited by

        @popester said in Quick question: because I think I messed up.:

        Do the Name Server records over ride other records like the SOA records? I have changed the name server records for my godaddy domain which makes DNS unmanageable through their interface. I have the records present in on the hosted name server but I am getting no indication that traffic is being redirected. ???!!!

        If you changed the name server, you manage the dns records through the nameserver you changed it to. Not godaddy anymore. You will need to change the name servers back to godaddy if you weren't ready for that change.

        1 Reply Last reply Reply Quote 1
        • popesterP
          popester
          last edited by

          Thank you. I am ready, I believe. It is just taking longer than I was expecting. Is there a better way to do this sort of thing? It seems like this is my only choice. I have all the records in place at the new name server. I appreciate your help.

          ObsolesceO travisdh1T jmooreJ Emad RE 4 Replies Last reply Reply Quote 0
          • ObsolesceO
            Obsolesce @popester
            last edited by

            @popester said in Quick question: because I think I messed up.:

            Thank you. I am ready, I believe. It is just taking longer than I was expecting. Is there a better way to do this sort of thing? It seems like this is my only choice. I have all the records in place at the new name server. I appreciate your help.

            It just depends on where everything is. It could take 48 hours to 100% take effect world wide. Sometimes it starts working in minutes depending on where the everything is geographically. But not usually.

            1 Reply Last reply Reply Quote 0
            • travisdh1T
              travisdh1 @popester
              last edited by

              @popester said in Quick question: because I think I messed up.:

              Thank you. I am ready, I believe. It is just taking longer than I was expecting. Is there a better way to do this sort of thing? It seems like this is my only choice. I have all the records in place at the new name server. I appreciate your help.

              Could be the timeout setting is quite long. 2 weeks used to be a common setting, so it could take some time if you didn't change that setting beforehand.

              J 1 Reply Last reply Reply Quote 2
              • jmooreJ
                jmoore @popester
                last edited by

                @popester said in Quick question: because I think I messed up.:

                Thank you. I am ready, I believe. It is just taking longer than I was expecting. Is there a better way to do this sort of thing? It seems like this is my only choice. I have all the records in place at the new name server. I appreciate your help.

                I will take a little time for things to sync, so don't panic yet. Sometimes a few hours in my experiences.

                1 Reply Last reply Reply Quote 1
                • Emad RE
                  Emad R @popester
                  last edited by

                  @popester

                  Yeah change it to CF which acts as reverseproxy and then any future changes will be instant.

                  1 Reply Last reply Reply Quote 1
                  • DashrenderD
                    Dashrender
                    last edited by

                    The new DNS servers should be seen as the SOA almost immediately, but as mentioned, any DNS server that pulled records (cached them) will wait out their TTL before looking back to get updated information and discovering the new SOA.

                    1 Reply Last reply Reply Quote 2
                    • JaredBuschJ
                      JaredBusch
                      last edited by

                      dig is your friend.

                      Show the SOA
                      6f1aa1ed-d398-4fa4-be98-cb5ed4fbf71f-image.png

                      Show results from your default DNS (typically assigned by your DHCP server to your machine)
                      307f0f28-b5e2-4a64-8681-389def5dd864-image.png

                      Show results from a specifc DNS server. In this example, cloudflare
                      ef2a1aec-7169-436e-9bd8-facac8b72615-image.png

                      1 Reply Last reply Reply Quote 1
                      • J
                        JasGot @travisdh1
                        last edited by JasGot

                        @travisdh1 said in Quick question: because I think I messed up.:

                        Could be the timeout setting is quite long. 2 weeks used to be a common setting, so it could take some time if you didn't change that setting beforehand.

                        Excellent point. For years we have been making it a point to set the timeout to 900 seconds as soon as we new there was going to be a change in the future. Not all name servers honor it, but is sure has had a positive impact to the overall propagation time.

                        1 Reply Last reply Reply Quote 0
                        • popesterP
                          popester
                          last edited by

                          Thanks for all the help. The Dig command is now in my tool bag. Thank you Jared.

                          Confession time: 7.5 hrs into the 48 hr wait and hope, I discovered an issue.

                          The domain was wardmechanical.com.

                          Our isp, which we have a great relationship with (they are awesome) put in the initial DNS entry for me because we were working on the website (we have a guy for website stuff). I was sitting reading about DNS going over in my head what I could have done wrong. While starring at the DNS entry page it suddenly jumped out at me.

                          The zone was set up with wardmechancial.com

                          The I and C were transposed........ Wow........ :astonished_face:

                          So I did a FTFY and within seconds things started talking.

                          Ya live, ya learn, ya die......

                          J 1 Reply Last reply Reply Quote 3
                          • J
                            JasGot @popester
                            last edited by

                            @popester said in Quick question: because I think I messed up.:

                            The I and C were transposed........ Wow........

                            Typos drive me insane! Glad you found it before you suffered a catastrophe.

                            1 Reply Last reply Reply Quote 1
                            • 1 / 1
                            • First post
                              Last post