About the single IP. There are not enough IP addresses for the world in IPv4 so no, that's not an issue today as routers share the internet to the PCs on the other side. How this works is on the web so moving on.
As to the verification, Facebook has their system so just verify and move forward.
I tried the forwarders and that didn't work. I put in all the public DNS that were recommended, 220.127.116.11, 18.104.22.168 and 22.214.171.124. I think the DNS component of the server might be corrupted. I was thinking of removing the DNS entirely and re-add it again on the server. This server was added to an existing forest, so I think some of the DNS properties from the old server is still playing a role somehow. The old server has been taken down.
If I deleted the current DNS settings and configured a new one, would that make a difference? Somehow I think it will. However, Im not sure what the consequences of deleting the current settings will be.
Also, I noticed when I connected my laptop to the Wi-Fi and statically assigned the DNS server (192.168.0.3), it was then able to go out the internet. The connection was kind of slow, but it still went out to the internet. That made me think that the DNS settings might be corrupted.
Regarding the nslookup, I was working with Ubiquity support exclusively for a while, as I thought the issue was with them. They ran a couple of NSLOOKUP commands and saw that the AP was working fine with DNS. They concluded the issue is with the DNS server.
I will try that NSLOOKUP command from the server and see what I get. I'll let you know the results.
From server at 192.168.0.3. It is the DNS for the network. Thus it should also have Forwarders setup in it's DNS config so that anything it can't resolve gets sent out to another 3rd party dns server (i.e. 126.96.36.199 or 188.8.131.52).
From the client, if you can ping something internally, but dns fails when going to an external site, then the Forwarders are probably incorrect.
On a client or even on the server, check dns by opening a command prompt:
<here you should see a response showing google's ip>
<here, if you get a timeout, the server is not forwarding dns requests outbound or is blocked going out a tcp/udp 53>
OK, now run NSLOOKUP on the client that doesn't work and see if NSLOOKUP works.
This is starting to sound as if the Ubiquity is the issue. I'm not using their product so you may have to call them if this is the cause of the issue. We've done the rest of the checking so what remains is the Ubiquity.
The machine with the ip 192.168.0.3 is the DNS server. Its also the local server/domain controller. 192.168.0.1 is the gateway, which is a netgear firewall. So every machine that has joined this domain is assigned an ip that's on the subnet of 192.168.0.x.
The first set of ip addresses that I showed you was from the server/domain controller. Its ip address is 192.168.0.3. And because its also the DNS server, that's why its DNS is 127.0.0.1. Every other machine on the network is assigned 192.168.0.3 for the DNS.
I thought I posted that in the previous post I copied. The IP settings from the client's server is:
DNS: 127.0.0.1 (if this is a failure point, maybe chaning to 192.168.0.3 might help, let me know if this is what you would suggest)
The AP's IP settings (Set to DHCP) are:
The network is on a 192.168.0.x subnet. So all the other machines connected are all on the same subnet, including the AP. Hope that helps.
Thanks again for the help!
I asked for the client IP settings. 127.0.0.1 would be a failure point. You are close to solving this as it is indeed a DNS issue. But here I only have what you share and maybe you posted it but I don't see it. What are the client IP settings?
The AP is set to DHCP, and is assigned 192.168.0.13 when I was there last. I'm not able to log into the configuration of the AP unless I'm on site. Everything seems to be connected just fine, but DNS is just not doing what it's supposed to be doing on the server. Also, the server has the role of DHCP. Its turned off on the Firewall/router. Not sure if that could be part of the problem. Like I said, I can ping 184.108.40.206 when I'm connected via wireless, but not to Google's website or any other website, which means its a DNS issue.
These are all the devices connected to the network:
Interface: 192.168.0.3 --- 0xd