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

    Certbot

    Scheduled Pinned Locked Moved IT Discussion
    138 Posts 8 Posters 29.6k Views
    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.
    • DashrenderD
      Dashrender
      last edited by

      The only DNS IPs that should be listed in any PC that lives on your network should be the IPs of these machines

      0_1464270779999_ns.JPG

      alex.olynykA 1 Reply Last reply Reply Quote 1
      • JaredBuschJ
        JaredBusch @wirestyle22
        last edited by

        @wirestyle22 said in Certbot:

        @Dashrender said in Certbot:

        yep, there are your problems!!

        Look at your DNS entries. You can only use Windows DNS servers for DNS to have this problem solved.

        It also appears that you are not using DHCP - why not?

        Also, why is 127.0.0.1 in that list? that is basically saying, use myself to find DNS information, but non of your PCs have a DNS sever installed on them, I hope.

        What is that ::1 in DNS servers?

        That is IPv6 loopback

        wirestyle22W 1 Reply Last reply Reply Quote 2
        • wirestyle22W
          wirestyle22 @JaredBusch
          last edited by

          @JaredBusch said in Certbot:

          @wirestyle22 said in Certbot:

          @Dashrender said in Certbot:

          yep, there are your problems!!

          Look at your DNS entries. You can only use Windows DNS servers for DNS to have this problem solved.

          It also appears that you are not using DHCP - why not?

          Also, why is 127.0.0.1 in that list? that is basically saying, use myself to find DNS information, but non of your PCs have a DNS sever installed on them, I hope.

          What is that ::1 in DNS servers?

          That is IPv6 loopback

          Oh I see. Thanks

          1 Reply Last reply Reply Quote 0
          • DashrenderD
            Dashrender @wirestyle22
            last edited by

            This post is deleted!
            1 Reply Last reply Reply Quote 1
            • DashrenderD
              Dashrender
              last edited by

              @alex-olynyk

              Do you have someone else in the company who is a senior IT person? Or are you the one currently in charge of the network?

              alex.olynykA 1 Reply Last reply Reply Quote 0
              • alex.olynykA
                alex.olynyk @Dashrender
                last edited by

                @Dashrender said in Certbot:

                @alex-olynyk

                Do you have someone else in the company who is a senior IT person? Or are you the one currently in charge of the network?

                there is a senior IT person. But he is at the same level as me when it comes to DNS

                DashrenderD 1 Reply Last reply Reply Quote 0
                • alex.olynykA
                  alex.olynyk @Dashrender
                  last edited by

                  @Dashrender said in Certbot:

                  The only DNS IPs that should be listed in any PC that lives on your network should be the IPs of these machines

                  0_1464270779999_ns.JPG

                  Im aware of that

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

                    Hold the phone here -

                    JB pointed out to me that the ipconfig you posted is from your DC.

                    THAT majorly changes things.

                    You can point to yourself for DNS on a DC - in your case you don't need to, because have 6 DNS servers.

                    You need to change the Domain Controller's DNS to all point to other DNS servers on your network. The primary one should point to another Local DNS server if there is one, the secondary can be local or remote. If there are no other local DNS, you have no choice but to have the primary point to another DNS that is remote.

                    wirestyle22W alex.olynykA 2 Replies Last reply Reply Quote 0
                    • wirestyle22W
                      wirestyle22 @Dashrender
                      last edited by

                      @Dashrender said in Certbot:

                      Hold the phone here -

                      JB pointed out to me that the ipconfig you posted is from your DC.

                      THAT majorly changes things.

                      You can point to yourself for DNS on a DC - in your case you don't need to, because have 6 DNS servers.

                      You need to change the Domain Controller's DNS to all point to other DNS servers on your network. The primary one should point to another Local DNS server if there is one, the secondary can be local or remote. If there are no other local DNS, you have no choice but to have the primary point to another DNS that is remote.

                      Yeah I was literally just typing that out in a post. Rose-DC1 so it would refer to itself for DNS

                      1 Reply Last reply Reply Quote 0
                      • DashrenderD
                        Dashrender @alex.olynyk
                        last edited by

                        @alex.olynyk said in Certbot:

                        @Dashrender said in Certbot:

                        @alex-olynyk

                        Do you have someone else in the company who is a senior IT person? Or are you the one currently in charge of the network?

                        there is a senior IT person. But he is at the same level as me when it comes to DNS

                        I'm really thinking JB is right, you need to hire someone to either remotely assist you or come onsite and give your network a good once over. it will be well worth the spend.

                        1 Reply Last reply Reply Quote 2
                        • alex.olynykA
                          alex.olynyk @Dashrender
                          last edited by

                          @Dashrender said in Certbot:

                          Hold the phone here -

                          JB pointed out to me that the ipconfig you posted is from your DC.

                          THAT majorly changes things.

                          You can point to yourself for DNS on a DC - in your case you don't need to, because have 6 DNS servers.

                          You need to change the Domain Controller's DNS to all point to other DNS servers on your network. The primary one should point to another Local DNS server if there is one, the secondary can be local or remote. If there are no other local DNS, you have no choice but to have the primary point to another DNS that is remote.

                          0_1464271528426_Capture.PNG
                          128.1 is the only DC/DNS on site so its pointing to 118.5 which is a DC/DNS server at a remote site.

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

                            what is the name of that server at that site?

                            alex.olynykA 1 Reply Last reply Reply Quote 0
                            • alex.olynykA
                              alex.olynyk @Dashrender
                              last edited by

                              @Dashrender said in Certbot:

                              what is the name of that server at that site?

                              TRI-DC1A

                              1 Reply Last reply Reply Quote 0
                              • JaredBuschJ
                                JaredBusch @alex.olynyk
                                last edited by

                                @alex.olynyk said in Certbot:

                                @Dashrender said in Certbot:

                                Hold the phone here -

                                JB pointed out to me that the ipconfig you posted is from your DC.

                                THAT majorly changes things.

                                You can point to yourself for DNS on a DC - in your case you don't need to, because have 6 DNS servers.

                                You need to change the Domain Controller's DNS to all point to other DNS servers on your network. The primary one should point to another Local DNS server if there is one, the secondary can be local or remote. If there are no other local DNS, you have no choice but to have the primary point to another DNS that is remote.

                                0_1464271528426_Capture.PNG
                                128.1 is the only DC/DNS on site so its pointing to 118.5 which is a DC/DNS server at a remote site.

                                Gods, what a train wreck, but I keep coming back...

                                The DNS setting in the NIC for a DC (assuming it is also a DNS server) should ALWAYS point to itself first.

                                It should never point to anything else first.

                                DNS 1: 127.0.0.1
                                DNS 2: Some other INTERNAL DNS server

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

                                  @JaredBusch said in Certbot:

                                  @alex.olynyk said in Certbot:

                                  @Dashrender said in Certbot:

                                  Hold the phone here -

                                  JB pointed out to me that the ipconfig you posted is from your DC.

                                  THAT majorly changes things.

                                  You can point to yourself for DNS on a DC - in your case you don't need to, because have 6 DNS servers.

                                  You need to change the Domain Controller's DNS to all point to other DNS servers on your network. The primary one should point to another Local DNS server if there is one, the secondary can be local or remote. If there are no other local DNS, you have no choice but to have the primary point to another DNS that is remote.

                                  128.1 is the only DC/DNS on site so its pointing to 118.5 which is a DC/DNS server at a remote site.

                                  Gods, what a train wreck, but I keep coming back...

                                  The DNS setting in the NIC for a DC (assuming it is also a DNS server) should ALWAYS point to itself first.

                                  It should never point to anything else first.

                                  DNS 1: 127.0.0.1
                                  DNS 2: Some other INTERNAL DNS server

                                  Once you have that setup right, everything in the local office will immediately start working right.

                                  Next, you need to look into your DNS configuration, because in theory, you should have still been working if your DNS was properly replicating between all of your servers.

                                  1 Reply Last reply Reply Quote 2
                                  • A
                                    Alex Sage
                                    last edited by

                                    What DNS addresses are your clients getting from DHCP?

                                    alex.olynykA 1 Reply Last reply Reply Quote 0
                                    • alex.olynykA
                                      alex.olynyk @Alex Sage
                                      last edited by

                                      @aaronstuder said in Certbot:

                                      What DNS addresses are your clients getting from DHCP?

                                      we dont use DHCP. Clients are statically assigned 118.5

                                      A DashrenderD 2 Replies Last reply Reply Quote 0
                                      • A
                                        Alex Sage @alex.olynyk
                                        last edited by

                                        @alex.olynyk said in Certbot:

                                        we dont use DHCP. Clients are statically assigned 118.5

                                        It just gets better, and better.....

                                        1 Reply Last reply Reply Quote 0
                                        • DashrenderD
                                          Dashrender @JaredBusch
                                          last edited by

                                          @JaredBusch said in Certbot:

                                          128.1 is the only DC/DNS on site so its pointing to 118.5 which is a DC/DNS server at a remote site.

                                          Gods, what a train wreck, but I keep coming back...

                                          The DNS setting in the NIC for a DC (assuming it is also a DNS server) should ALWAYS point to itself first.

                                          It should never point to anything else first.

                                          DNS 1: 127.0.0.1
                                          DNS 2: Some other INTERNAL DNS server

                                          OK I'll disagree here. A DC should always point to another DC first and itself second. The assumption is that the other DC will be up and running while this DC is down. This will allow this DC to boot up faster on the assumption that DNS isn't the first thing that comes up.

                                          I have seen faster reboots because I point to some other DNS server instead itself first.

                                          JaredBuschJ 1 Reply Last reply Reply Quote 0
                                          • DashrenderD
                                            Dashrender @alex.olynyk
                                            last edited by

                                            @alex.olynyk said in Certbot:

                                            @aaronstuder said in Certbot:

                                            What DNS addresses are your clients getting from DHCP?

                                            we dont use DHCP. Clients are statically assigned 118.5

                                            While I don't understand your lack of use of DHCP, that shouldn't really matter.

                                            The clients do need to have DNS entries of only DNS servers within your network, they should never have an DNS entry for something outside your network, like google's 8.8.8.8 or your ISPs DNS servers. That will cause all kinds of problems.

                                            1 Reply Last reply Reply Quote 1
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 6
                                            • 7
                                            • 6 / 7
                                            • First post
                                              Last post