DHCP Scope and DNS Reverse Lookup
-
I am so lost.
-
@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.
-
@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.xzone. Going back to DHCP, the single scope is168.1.1 - 168.3.254.- force NextCloud to a
168.2.xaddress.
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.xaddress. Force as in push it to a192.168.2.xaddressWhoa, 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?
- force NextCloud to a
-
@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.xzone. Going back to DHCP, the single scope is168.1.1 - 168.3.254.- force NextCloud to a
168.2.xaddress.
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.xaddress. Force as in push it to a192.168.2.xaddressWhoa, 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.
- force NextCloud to a
-
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.
-
Never Mind.
Found the issue, and added the A Record accordingly - points like it should.
-
@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?
-
@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. -
@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.
-
@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.
