You don’t need to do any of that. The registration server itself serves the DNS records for the whole domain.
I tried accessing it using http://127.0.0.1:81 getting below error:-
Error:- https://pastebin.com/T5kLLB9m
config.otml:- https://pastebin.com/ng6GtvwS
other-config :- https://pastebin.com/Mh1vidZb
Assuming your domain is still uk.ms
…
config.toml
:
-
domain
should be:domain = "uk.ms"
-
ns_records
should be:ns_records = [ [ "ns1.uk.ms", "<IP address of your server>" ], ]
-
soa_record
should be:soa_record = "ns1.uk.ms hostmaster.uk.ms 1592378223 7200 3600 604800 300"
- The
geoip
sections should look like this:[pdns.geoip] default = "<IP address of your server>" [pdns.geoip.continent] # nothing else in this section
pagekite.conf
:
-
authdomain
should be:--authdomain=uk.ms
docker-compose.yml
:
- Why are you binding the DNS ports to 543 locally? Those need to be on 53, and should be open to the world (so that DNS resolution actually works).
Additionally:
- Externally, you need to open ports 53 (TCP), 53 (UDP), 443 (TCP), and 8443 (TCP) to the world.
still getting same error.
help me i have to deploy it for company
Your NS records are still not correct:
$ dig +short NS mozilla-iot.org
ns1.mozilla-iot.org.
ns2.mozilla-iot.org.
$ dig +short NS uk.ms
ns1.afraid.org.
ns4.afraid.org.
ns2.afraid.org.
ns3.afraid.org.
Where to create these records??. As you told i made changes in config.otml.
I am using adpar.us domain
$ dig +short NS adpar.us
ns2dqx.name.com.
ns4bty.name.com.
ns3dgj.name.com.
ns1fkl.name.com.
As I’ve told you multiple times, you need to change your domain registrar’s settings to not use its own name servers, but to instead use yours.
It will not create any problem right if i remove default name servers from there.
api.adpar.us should point our server.(A record)
ns1.adpar.us should point our server.(NS name server for that domain)
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.