When accesing the Registration server from url in docker logs i am getting Error was : NoRoute

WebThings
#36

Assuming your domain is still uk.ms…

config.toml:

  1. domain should be:
    domain = "uk.ms"
  2. ns_records should be:
    ns_records = [
  [ "ns1.uk.ms", "<IP address of your server>" ],
]
  3. soa_record should be:
    soa_record = "ns1.uk.ms hostmaster.uk.ms 1592378223  7200 3600 604800 300"
  4. 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:

  1. authdomain should be:
    --authdomain=uk.ms

docker-compose.yml:

  1. 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:

  1. Externally, you need to open ports 53 (TCP), 53 (UDP), 443 (TCP), and 8443 (TCP) to the world.
#37

still getting same error.

help me i have to deploy it for company

#38

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.
#39

Where to create these records??. As you told i made changes in config.otml.

I am using adpar.us domain

#40 
$ 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.

#41

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)

#42

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.

#43

20200619_021624
20200619_0216244096×1188 3.62 MB

Showing this error when remove all the default nameserver.

#44

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

#45

This is what ours looks like (not using name.com, but the same thing applies):

image
image860×462 14.9 KB

We run two separate registration server instances, hence the 2 records.

#47

i got the details shown in that image

Screenshot_20200622_095122
Screenshot_20200622_0951221163×594 63.2 KB
.But not able to access the registration server by url api.adpar.us

#48

It is giving like 502 bad gateway in nginx

#49

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”

#50

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.

#51

if i remove there default name server then nothing is working ,
Previous A records are also not working.

#52

Forget about the A records. You do NOT need them. All that you need are the NS records, which MUST point to your server.

#53

Can you check that on adpar.us

#54

now i added two name server ns1.adpar.us and ns3.adpar.us pointing to same server

#55

Screenshot_20200624_232957
Screenshot_20200624_2329571176×615 67.9 KB

Still getting nginx 502 bad gateway

#56

Ok, DNS looks good now. The next issue I see is that TCP ports 80 and 8443 are not open on your server.