It will not create any problem right if i remove default name servers from there.
No, and it’s the only way to make this work.
api.adpar.us should point our server.(A record)
No, you don’t need to manually create that A record. It will be handled by the registration server.
ns1.adpar.us should point our server.(NS name server for that domain)
Yes, the IP address of your registration server instance.
https://www.name.com/support/articles/205934547-Changing-nameservers-for-DNS-management
https://www.name.com/support/articles/205934457-Registering-custom-nameservers
https://www.name.com/support/articles/205934447-Changing-the-IP-of-your-custom-nameservers
This is what ours looks like (not using name.com, but the same thing applies):
We run two separate registration server instances, hence the 2 records.
i got the details shown in that image
.But not able to access the registration server by url api.adpar.usIt is giving like 502 bad gateway in nginx
This nginx error log while accessing that url
122.178.224.177 - - [22/Jun/2020:11:52:14 +0000] “GET / HTTP/2.0” 502 150 “-” “Mozilla/5.0 (X11; Linux x86_64; rv:77.0) Gecko/20100101 Firefox/77.0”
2020/06/22 11:52:14 [error] 30#30: *7 connect() failed (111: Connection refused) while connecting to upstream, client: 122.178.224.177, server: api.adpar.us, request: “GET / HTTP/2.0”, upstream: “http://127.0.0.1:81/”, host: “api.adpar.us:8443”
You still have one invalid NS record, the ns2dqx.name.com one. You’ll need remove that. If you’re forced to add a second record, you should be able to use ns2.adpar.us with the same IP address as ns1.adpar.us.
If you’re still having issues after you get that updated, please post your latest config files.
if i remove there default name server then nothing is working ,
Previous A records are also not working.
Forget about the A records. You do NOT need them. All that you need are the NS records, which MUST point to your server.
Ok, DNS looks good now. The next issue I see is that TCP ports 80 and 8443 are not open on your server.
now check its open. try accessing it
nginx is also running in docker,
Any problem with docker
This is the nginx config.
Note-
i commented the server block just above the registration server as other website is not accessible.
here nginx is config to deliver two websites.
One thing more i try removing all that other stuff and ran the nginx for only registration server still it is giving 502 bad gateway.
when i tried to register my sub-domain in iot gateway it is showing some error .
IOT gateway error log -> https://pastebin.com/gUfqA7Jg
this issue is solved now . the problem is created by the docker network.
Now registration server is running fine
