This is an answer given to a dns question, useful:
Hi,
maybe the most detailed info about dns settins is at: https://www.ehcp.net/helper/yardim/cat.php?cid=4&qid=16
there, you may find howto redirect domains and setup dns. (Currently, I didnt check every word there, some info may be outdated, not sure)
1-Since you host your server on your local, the most important part is port redirections. tcp+udp port 53,80 must be redirected at least to your server.
2- Additional thing to consider about dns:
- dns propogation (activation) takes some time, sometime 1-2 hours, sometime more than 1 day. (this is due to caching of dns queries in dns servers)
- if you do NOT make any dns query for any domain/subdomain, and define it properly in your dns/ehcp, after it is active, you can Query it, then, it may activate suddenly. The reason: Since nobody asked, dns is applied to whole world directly and suddenly. But in this case, you cannot change it immadiately, the change propogation takes time..
- if, you or somebody else, queries a domain, after that, changing that domain dns entries would take some time, since it is cached in other dns servers.
3- The very first record of a "server/ehcp/dns server" must be done in "Registrar" (place where you bought your domain), for ns1.anydomain.. or for ns2... if you want to use your own dns.
This must be done for at least one of your domains, in this case, for example, ns1.yyyyyyyyyy.com.zz.
Because, at start, domain registrar needs to know where to ask dns queries. This is called nameserver registering in Registrar.. You may find info in above website about this also.
to check/verify this, use whois command:
whois yourdomain.com
in output, you need to see your own nameservers. (if you are going to use your own)
if not, that means, you could not complete this step. if there is ip info, that should also point to your server or primary dns.
4- your dns domain should be setup in your Ehcp/Server. Just add your domain to Ehcp. No special setting required.
To test this, issue:
host yourdomain.com yourip
(this works even if step 2 or 3 problematic, but, does not work if step 1 is not fullfilled. Because, this works independent of registrar, bc, we query diretcly our server)
5- Not for only dns, for whole operation of Ehcp:
a- make sure ehcp daemon is running: ps aux | grep ehcp
you need to see a daemon line. if not, start it using:
/etc/init.d/ehcp restart
b- make sure ip info in ehcp web gui->options is correct. That should be your external real ip. your local ip would not function there..
These are all steps necessary for your "own dns server/nameserver".
Tests:
root@xxx:~/# nmap 103.148.xx.yy -p 53 -P0 -sU
Starting Nmap 7.80 ( https://nmap.org ) at 2021-11-21 14:42 CET
Nmap scan report for 103.148.xx.yy
Host is up.
PORT STATE SERVICE
53/udp open|filtered domain
Nmap done: 1 IP address (1 host up) scanned in 2.21 seconds
root@xxx:~/# nmap 103.148.xx.yy -p 53 -P0
Starting Nmap 7.80 ( https://nmap.org ) at 2021-11-21 14:42 CET
Nmap scan report for 103.148.xx.yy
Host is up.
PORT STATE SERVICE
53/tcp filtered domain
Nmap done: 1 IP address (1 host up) scanned in 2.20 seconds
root@xxx:~/# host ns1.yyyyyyyyyy.com.zz 103.148.xx.yy
;; connection timed out; no servers could be reached
These tests shows that, step 1 and/or 4 are not fullfilled. Both can also problematic, I cannot understand this now, without knowing step 1 is fullfilled. step 3 can be verified after others.
Hi,
maybe the most detailed info about dns settins is at: https://www.ehcp.net/helper/yardim/cat.php?cid=4&qid=16
there, you may find howto redirect domains and setup dns. (Currently, I didnt check every word there, some info may be outdated, not sure)
1-Since you host your server on your local, the most important part is port redirections. tcp+udp port 53,80 must be redirected at least to your server.
2- Additional thing to consider about dns:
- dns propogation (activation) takes some time, sometime 1-2 hours, sometime more than 1 day. (this is due to caching of dns queries in dns servers)
- if you do NOT make any dns query for any domain/subdomain, and define it properly in your dns/ehcp, after it is active, you can Query it, then, it may activate suddenly. The reason: Since nobody asked, dns is applied to whole world directly and suddenly. But in this case, you cannot change it immadiately, the change propogation takes time..
- if, you or somebody else, queries a domain, after that, changing that domain dns entries would take some time, since it is cached in other dns servers.
3- The very first record of a "server/ehcp/dns server" must be done in "Registrar" (place where you bought your domain), for ns1.anydomain.. or for ns2... if you want to use your own dns.
This must be done for at least one of your domains, in this case, for example, ns1.yyyyyyyyyy.com.zz.
Because, at start, domain registrar needs to know where to ask dns queries. This is called nameserver registering in Registrar.. You may find info in above website about this also.
to check/verify this, use whois command:
whois yourdomain.com
in output, you need to see your own nameservers. (if you are going to use your own)
if not, that means, you could not complete this step. if there is ip info, that should also point to your server or primary dns.
4- your dns domain should be setup in your Ehcp/Server. Just add your domain to Ehcp. No special setting required.
To test this, issue:
host yourdomain.com yourip
(this works even if step 2 or 3 problematic, but, does not work if step 1 is not fullfilled. Because, this works independent of registrar, bc, we query diretcly our server)
5- Not for only dns, for whole operation of Ehcp:
a- make sure ehcp daemon is running: ps aux | grep ehcp
you need to see a daemon line. if not, start it using:
/etc/init.d/ehcp restart
b- make sure ip info in ehcp web gui->options is correct. That should be your external real ip. your local ip would not function there..
These are all steps necessary for your "own dns server/nameserver".
Tests:
root@xxx:~/# nmap 103.148.xx.yy -p 53 -P0 -sU
Starting Nmap 7.80 ( https://nmap.org ) at 2021-11-21 14:42 CET
Nmap scan report for 103.148.xx.yy
Host is up.
PORT STATE SERVICE
53/udp open|filtered domain
Nmap done: 1 IP address (1 host up) scanned in 2.21 seconds
root@xxx:~/# nmap 103.148.xx.yy -p 53 -P0
Starting Nmap 7.80 ( https://nmap.org ) at 2021-11-21 14:42 CET
Nmap scan report for 103.148.xx.yy
Host is up.
PORT STATE SERVICE
53/tcp filtered domain
Nmap done: 1 IP address (1 host up) scanned in 2.20 seconds
root@xxx:~/# host ns1.yyyyyyyyyy.com.zz 103.148.xx.yy
;; connection timed out; no servers could be reached
These tests shows that, step 1 and/or 4 are not fullfilled. Both can also problematic, I cannot understand this now, without knowing step 1 is fullfilled. step 3 can be verified after others.