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

    DHCP Scope and DNS Reverse Lookup

    Scheduled Pinned Locked Moved IT Discussion
    26 Posts 5 Posters 1.7k 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.
    • gjacobseG
      gjacobse @scottalanmiller
      last edited by

      @scottalanmiller said in DHCP Scope and DNS Reverse Lookup:

      @gjacobse said in DHCP Scope and DNS Reverse Lookup:

      It is available externally just fine. it is internal that I am having the issue.

      Then why are we looking at the public DNS records? You either need to assign an overloaded one internally or a different one internally. The internal users cannot be using the public DNS records.

      DNS Manager
      Forward Lookup Zone - domain.com A Record(s)

      demo ( points to external IP)
      RDS (points to internal IP)
      RDS3 (points to Internal IP)
      nextcloud (points to Internal IP)

      scottalanmillerS stacksofplatesS 2 Replies Last reply Reply Quote 0
      • scottalanmillerS
        scottalanmiller @gjacobse
        last edited by

        @gjacobse said in DHCP Scope and DNS Reverse Lookup:

        @scottalanmiller said in DHCP Scope and DNS Reverse Lookup:

        @gjacobse said in DHCP Scope and DNS Reverse Lookup:

        It is available externally just fine. it is internal that I am having the issue.

        Then why are we looking at the public DNS records? You either need to assign an overloaded one internally or a different one internally. The internal users cannot be using the public DNS records.

        DNS Manager
        Forward Lookup Zone - domain.com A Record(s)

        demo ( points to external IP)
        RDS (points to internal IP)
        RDS3 (points to Internal IP)
        nextcloud (points to Internal IP)

        If the external DNS points to an internal IP, it can't work.

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

          @scottalanmiller said in DHCP Scope and DNS Reverse Lookup:

          @gjacobse said in DHCP Scope and DNS Reverse Lookup:

          It is available externally just fine. it is internal that I am having the issue.

          Then why are we looking at the public DNS records? You either need to assign an overloaded one internally or a different one internally. The internal users cannot be using the public DNS records.

          Unless your firewall supports hairpinning, assuming that's a Scott approved term.

          scottalanmillerS 1 Reply Last reply Reply Quote 0
          • stacksofplatesS
            stacksofplates @gjacobse
            last edited by

            @gjacobse said in DHCP Scope and DNS Reverse Lookup:

            @scottalanmiller said in DHCP Scope and DNS Reverse Lookup:

            @gjacobse said in DHCP Scope and DNS Reverse Lookup:

            It is available externally just fine. it is internal that I am having the issue.

            Then why are we looking at the public DNS records? You either need to assign an overloaded one internally or a different one internally. The internal users cannot be using the public DNS records.

            DNS Manager
            Forward Lookup Zone - domain.com A Record(s)

            demo ( points to external IP)
            RDS (points to internal IP)
            RDS3 (points to Internal IP)
            nextcloud (points to Internal IP)

            What DNS manager? Internal or external?

            Instead of looking at reverse, what do you get from an nslookup on nextcloud.domain.com?

            gjacobseG 1 Reply Last reply Reply Quote 0
            • scottalanmillerS
              scottalanmiller @Dashrender
              last edited by

              @dashrender said in DHCP Scope and DNS Reverse Lookup:

              @scottalanmiller said in DHCP Scope and DNS Reverse Lookup:

              @gjacobse said in DHCP Scope and DNS Reverse Lookup:

              It is available externally just fine. it is internal that I am having the issue.

              Then why are we looking at the public DNS records? You either need to assign an overloaded one internally or a different one internally. The internal users cannot be using the public DNS records.

              Unless your firewall supports hairpinning, assuming that's a Scott approved term.

              Even hairpinning doesn't work in this direction.

              1 Reply Last reply Reply Quote 0
              • gjacobseG
                gjacobse @stacksofplates
                last edited by

                @stacksofplates said in DHCP Scope and DNS Reverse Lookup:

                @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                @scottalanmiller said in DHCP Scope and DNS Reverse Lookup:

                @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                It is available externally just fine. it is internal that I am having the issue.

                Then why are we looking at the public DNS records? You either need to assign an overloaded one internally or a different one internally. The internal users cannot be using the public DNS records.

                DNS Manager
                Forward Lookup Zone - domain.com A Record(s)

                demo ( points to external IP)
                RDS (points to internal IP)
                RDS3 (points to Internal IP)
                nextcloud (points to Internal IP)

                What DNS manager? Internal or external?

                Instead of looking at reverse, what do you get from an nslookup on nextcloud.domain.com?

                DNS Manager : Server 2012

                scottalanmillerS 1 Reply Last reply Reply Quote 0
                • scottalanmillerS
                  scottalanmiller @gjacobse
                  last edited by

                  @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                  @stacksofplates said in DHCP Scope and DNS Reverse Lookup:

                  @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                  @scottalanmiller said in DHCP Scope and DNS Reverse Lookup:

                  @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                  It is available externally just fine. it is internal that I am having the issue.

                  Then why are we looking at the public DNS records? You either need to assign an overloaded one internally or a different one internally. The internal users cannot be using the public DNS records.

                  DNS Manager
                  Forward Lookup Zone - domain.com A Record(s)

                  demo ( points to external IP)
                  RDS (points to internal IP)
                  RDS3 (points to Internal IP)
                  nextcloud (points to Internal IP)

                  What DNS manager? Internal or external?

                  Instead of looking at reverse, what do you get from an nslookup on nextcloud.domain.com?

                  DNS Manager : Server 2012

                  OH! You should have said that, we've been assuming the main DNS system. Argh.

                  So internal doesn't work even though it points to the right address?

                  gjacobseG 1 Reply Last reply Reply Quote 0
                  • scottalanmillerS
                    scottalanmiller @gjacobse
                    last edited by

                    @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                    However the NextCloud instance is on a 168.3.x zone. Going back to DHCP, the single scope is 168.1.1 - 168.3.254.

                    • force NextCloud to a 168.2.x address.

                    What do you mean force it to 168.2.x? That is a 168.3.x address here. See your subnet notes above.

                    gjacobseG 1 Reply Last reply Reply Quote 0
                    • gjacobseG
                      gjacobse @scottalanmiller
                      last edited by

                      @scottalanmiller said in DHCP Scope and DNS Reverse Lookup:

                      @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                      @stacksofplates said in DHCP Scope and DNS Reverse Lookup:

                      @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                      @scottalanmiller said in DHCP Scope and DNS Reverse Lookup:

                      @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                      It is available externally just fine. it is internal that I am having the issue.

                      Then why are we looking at the public DNS records? You either need to assign an overloaded one internally or a different one internally. The internal users cannot be using the public DNS records.

                      DNS Manager
                      Forward Lookup Zone - domain.com A Record(s)

                      demo ( points to external IP)
                      RDS (points to internal IP)
                      RDS3 (points to Internal IP)
                      nextcloud (points to Internal IP)

                      What DNS manager? Internal or external?

                      Instead of looking at reverse, what do you get from an nslookup on nextcloud.domain.com?

                      DNS Manager : Server 2012

                      OH! You should have said that, we've been assuming the main DNS system. Argh.

                      So internal doesn't work even though it points to the right address?

                      Guess I made some assumptions when I mentioned DHCP Scope and DNS, and refererenced IPs in the local 192.168.2 zone

                      1 Reply Last reply Reply Quote 0
                      • gjacobseG
                        gjacobse @scottalanmiller
                        last edited by

                        @scottalanmiller said in DHCP Scope and DNS Reverse Lookup:

                        @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                        However the NextCloud instance is on a 168.3.x zone. Going back to DHCP, the single scope is 168.1.1 - 168.3.254.

                        • force NextCloud to a 168.2.x address.

                        What do you mean force it to 168.2.x? That is a 168.3.x address here. See your subnet notes above.

                        NextCloud currently has a 192.168.3.x address. Force as in push it to a 192.168.2.x address

                        scottalanmillerS 1 Reply Last reply Reply Quote 0
                        • scottalanmillerS
                          scottalanmiller
                          last edited by

                          I am so lost.

                          stacksofplatesS 1 Reply Last reply Reply Quote 0
                          • stacksofplatesS
                            stacksofplates @scottalanmiller
                            last edited by

                            @scottalanmiller said in DHCP Scope and DNS Reverse Lookup:

                            I am so lost.

                            Ya idk what's going on. I'd do an nslookup first to figure out what the clients are tying to get to.

                            1 Reply Last reply Reply Quote 0
                            • scottalanmillerS
                              scottalanmiller @gjacobse
                              last edited by

                              @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                              @scottalanmiller said in DHCP Scope and DNS Reverse Lookup:

                              @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                              However the NextCloud instance is on a 168.3.x zone. Going back to DHCP, the single scope is 168.1.1 - 168.3.254.

                              • force NextCloud to a 168.2.x address.

                              What do you mean force it to 168.2.x? That is a 168.3.x address here. See your subnet notes above.

                              NextCloud currently has a 192.168.3.x address. Force as in push it to a 192.168.2.x address

                              Whoa, that's nothing like what you had before. 168.x is external public IPs. 192.168.x is internal, private IPs.

                              Why are there two subnets as options?

                              stacksofplatesS 1 Reply Last reply Reply Quote 2
                              • stacksofplatesS
                                stacksofplates @scottalanmiller
                                last edited by stacksofplates

                                @scottalanmiller said in DHCP Scope and DNS Reverse Lookup:

                                @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                                @scottalanmiller said in DHCP Scope and DNS Reverse Lookup:

                                @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                                However the NextCloud instance is on a 168.3.x zone. Going back to DHCP, the single scope is 168.1.1 - 168.3.254.

                                • force NextCloud to a 168.2.x address.

                                What do you mean force it to 168.2.x? That is a 168.3.x address here. See your subnet notes above.

                                NextCloud currently has a 192.168.3.x address. Force as in push it to a 192.168.2.x address

                                Whoa, that's nothing like what you had before. 168.x is external public IPs. 192.168.x is internal, private IPs.

                                Why are there two subnets as options?

                                This is why I was confused. Looks like he left off the 192 to shorten it? I thought it was public also.

                                Ah it's in the reverse ip. I just missed it.

                                1 Reply Last reply Reply Quote 1
                                • scottalanmillerS
                                  scottalanmiller
                                  last edited by

                                  This thread is a lost cause. @gjacobse start a new thread. Post your GOAL and your PROBLEM. This thread is all about DHCP Scope and Reverse DNS which are both completely unrelated to the issue you are trying to solve. Everyone is lost because you led off with a thread about red herrings and not about the problem you are attempting to resolve. Start over from the beginning, but don't inject potential solutions or presumptions. Just state the state of things and what you need to have working at the end. Don't use terms like "DNS Server" without telling us internal or external. Don't modify addresses. Keep it simple and focused on the goal.

                                  1 Reply Last reply Reply Quote 0
                                  • gjacobseG
                                    gjacobse
                                    last edited by

                                    Never Mind.

                                    Found the issue, and added the A Record accordingly - points like it should.

                                    scottalanmillerS 1 Reply Last reply Reply Quote 0
                                    • scottalanmillerS
                                      scottalanmiller @gjacobse
                                      last edited by

                                      @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                                      Never Mind.

                                      Found the issue, and added the A Record accordingly - points like it should.

                                      There was no record at all?

                                      gjacobseG JaredBuschJ 2 Replies Last reply Reply Quote 0
                                      • gjacobseG
                                        gjacobse @scottalanmiller
                                        last edited by

                                        @scottalanmiller said in DHCP Scope and DNS Reverse Lookup:

                                        @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                                        Never Mind.

                                        Found the issue, and added the A Record accordingly - points like it should.

                                        There was no record at all?

                                        I had added the record. But didn't work. searched for record, not there.
                                        Was in wrong zone.

                                        JaredBuschJ 1 Reply Last reply Reply Quote 0
                                        • JaredBuschJ
                                          JaredBusch @scottalanmiller
                                          last edited by

                                          @scottalanmiller said in DHCP Scope and DNS Reverse Lookup:

                                          @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                                          Never Mind.

                                          Found the issue, and added the A Record accordingly - points like it should.

                                          There was no record at all?

                                          Obviously. This was the entire problem the entire time.

                                          He did not even perform a basic DNS validation locally (nslookup) before jumping to random conclusions on the wrong things.

                                          1 Reply Last reply Reply Quote 1
                                          • JaredBuschJ
                                            JaredBusch @gjacobse
                                            last edited by

                                            @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                                            @scottalanmiller said in DHCP Scope and DNS Reverse Lookup:

                                            @gjacobse said in DHCP Scope and DNS Reverse Lookup:

                                            Never Mind.

                                            Found the issue, and added the A Record accordingly - points like it should.

                                            There was no record at all?

                                            I had added the record. But didn't work. searched for record, not there.
                                            Was in wrong zone.

                                            That is 100% no record at all.

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