Since you have used my Tutorial in setting up name service, do you have proposals to improve it in ways that would have helped you to get a working name service using the Tutorial?
But I don't want use this DNS setting because I don't want share the Ip of the VPS, 89.10.112.113 should be use to manage the Vps ONLY. Maybe that's my fault and I have been unclear 89.10.112.113 is the IP of my VPS https://vps730322.ovh.net 12.34.54.67 is the dedicated IP of this domaine name domain-name.com, then ns1.domain-name.com and ns2.domain-name.com must have the PTR Reverse on 12.34.54.67 exactly as My DNS managed by my registrar (OVH). My VPS doesn't manage the Dns of this domaine name, just need to reverse on ns1.domain-name.com = 12.34.54.67 and Code: # host domain-name.com 12.34.54.67 ;; connection timed out; no servers could be reached is wrong because we should get this at the end Code: # host domain-name.com 12.34.54.67 Using domain server: Name: 12.34.54.67 Address: 12.34.54.67#32 Aliases: domain-name.com has address 12.34.54.67 but we get Code: # host domain-name.com 12.34.54.67 ;; connection timed out; no servers could be reached
Yes sure it would be a pleasure to collaborate with you, and I am the perfect exemple because I am a beginner with IspConfig and Linux Let's keep in touch by private message to go a head for the tutorial... First, the tutorial need to be separate in 2 parts : 1- Dns fully managed by the server and Isp Config (for advanced admin) 2- Dns managed by one registrar (in the most of case..), just add your domain name to reverse with your DNS already managed by your registrar Theses 2 parts are completely different and make the beginner in trouble
1. Private message is not a good way to resolve things in a forum. 2. Newbie or not, you should know what you were doing before people can properly help you.
Please try to ready carrefully and think twice Private message was not to get help but to improve one tutorial as requested by @Taleman. That's a great welcome from you in this forum to explain : Newvbie should know what you were doing. If the Newbies knows what are they doing, they doesn't need help Maybe you have something more positive to say ? and would like to contribute to help in this thread ? Regards
There is no host answering to ping at IP number 87.98.149.60. Code: $ ping -c 3 87.98.149.60 PING 87.98.149.60 (87.98.149.60) 56(84) bytes of data. --- 87.98.149.60 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2039ms But this IP answers: Code: $ ping -c 3 51.77.159.133 PING 51.77.159.133 (51.77.159.133) 56(84) bytes of data. 64 bytes from 51.77.159.133: icmp_seq=1 ttl=47 time=70.2 ms 64 bytes from 51.77.159.133: icmp_seq=2 ttl=47 time=75.3 ms 64 bytes from 51.77.159.133: icmp_seq=3 ttl=47 time=78.6 ms --- 51.77.159.133 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 70.222/74.729/78.634/3.474 ms There is some confusion here somewhere, but I do not know what it is. Do you have a hosts that has IP-number 87.98.149.60? Where did you get the IP 87.98.149.60 from? You may well not want to use it, but if that is the only IP you got then there is not much choise. As to the reverse IP PTR record, if you plan to use this host as mail server the current reverse IP is not OK. Code: $ host 87.98.149.60 60.149.98.87.in-addr.arpa domain name pointer clear-optical.com. For an e-mail server, it must be a hostname, that is someting.clear-optical.com. And the mail host must have that as hostname and advertice that as the mail server name.
I'm starting to think the problem come from Ovh who manage the Dns and the IP... We did so many tests and we did not solved the problem. On the other side normally this is should work even if the Ping failed ? What do you think ? Code: # host domain-name.com 12.34.54.67 ;; connection timed out; no servers could be reached Maybe it's normal if the ping failed because this Ip do not Reverse PTR on my Vps ? What do you think ? Code: # host domain-name.com 12.34.54.67 ;; connection timed out; no servers could be reached but this is workiing ! Code: # host 12.34.54.67 60.149.98.87.in-addr.arpa domain name pointer domain-name.com. I get this dedicated Ip from my RIPE block with OVH, that's why I'm always using only one Ip per domain it's more convenient for the SNI and my Ip are Failover, mean I can switch it from server 1 to server 2 wihout thouching the Dns of the domain name Maybe we can still looking to discover why this is not working ? Code: # host domain-name.com 12.34.54.67 ;; connection timed out; no servers could be reached because we should get Code: # host domain-name.com 12.34.54.67 Using domain server: Name: 12.34.54.67 Address: 12.34.54.67#32 Aliases: domain-name.com has address 12.34.54.67 What do you think ?
I ask again: This command Code: # host 87.98.149.60 60.149.98.87.in-addr.arpa domain name pointer clear-optical.com. works because it queries OVH name server. It is OVH that is responsible for the IP address zone. Why do you say that? This whole thread is about you setting up DNS for your clear-optical.com zone. I am pretty sure that if you now register your clear-optical.com zone and change the name server to be 51.77.159.133, name service works after waiting for the 4 - 48 hours for DNS information to propagate around the world.
Funny responses but they are fine to me, though I will stick to retrace my steps based on howtoforge manual and tutorials that I followed. Anyway, you are in the good hand of @Taleman, so, hopefully you can resolve whatever problems you are facing, eventually.
I asnwered you already with this This answer was not clear ? Maybe I didn't undesrtood your question ? Because this IP failover is managed by OVH, able to be used as server 1 to server 2 to server 3. It happened already, when I changed the server for one IP, this Ip was sticked on the Old server and do not respond for this reason. And I agree with you, if the Ping doesn't work maybe the problem to not come from the VPS but from Ovh No I'm sorry, shared IP with multi domain name is not the right way to do, exemple if one domain name send spam, the Ip of the VPS will be burned...and for many other reason... Before I was using Plesk with One dedicated Ip for each domain and I would like to keep this.
OK, can not argue with that. I'm just pointing out that if you want to get your DNS name service working, then:
I suggest to restart again the full DNS check to discover why it's not working Do you agree ? Could you please let me know the command line that you want check ? and I will give you the result Just to remind : vps123456.ovh.net = IP 89.10.112.113 this is for my Vps domain-name.com = IP 12.34.54.67 Dns and Ip managed by Ovh Do you agree ? Thanks
You can use as many IP addresses as you want in ISPConfig. If an IP does not point to your server and this seems to be the case as you can not reach any service and you can not even ping it, then you can not reach DNS on your server by using that IP. As @Taleman pointed out, DNS is working when you can reach it on your other IP, so there is no DNS or ISPConfig issue here. Now you'll have to figure out with OVH support to get your additional IP working so that it can be used to reach services on your server as well. ISPConfig is not involved in that in any way as you configure the IP in the network config files of your server according to the instructions that you receive from OVH and if you did that, all services on your server will be reachable trough that IP as well.
Yes I agree and wrote : I opened one ticket already and waiting an answer from Ovh Many thanks to you and @Taleman for your great support I will keep you informed as soon as I get something new from OVH
Hello, I'm back again because I've got a more information from Ovh about the Ip's, apparently that's coming from the Firewal (I installed UFW as in the tutorial for install Debian 10) OVH said : Code: - nmap -sU -sS -T2 -Pn 12.34.54.67 -p 53 PORT STATE SERVICE 53/tcp filtered domain 53/udp openfiltered domain Please check port 53 / TCP and allow this IP. When IFPO will be valid, you will be able to use your IP How I can do this ? I tried Code: # sudo ufw disable sudo: unable to resolve host domain-name.com: Temporary failure in name resolution Firewall stopped and disabled on system startup but still Code: # host domain-name.com 12.34.54.67 ;; connection timed out; no servers could be reached You have mail in /var/mail/root Mail from /var/mail/root Code: From [email protected] Wed Sep 25 14:45:50 2019 Return-Path: <[email protected]> X-Original-To: [email protected] Delivered-To: [email protected] Received: from localhost (localhost.localdomain [127.0.0.1]) by vps123456.ovh.net (Postfix) with ESMTP id 005F521C67 for <[email protected]>; Wed, 25 Sep 2019 14:45:50 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at vps123456.ovh.net Received: from vps123456.ovh.net ([127.0.0.1]) by localhost (vps123456.ovh.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V6LDQD75D0Mm for <[email protected]>; Wed, 25 Sep 2019 14:45:43 +0200 (CEST) Received: by vps123456.ovh.net (Postfix, from userid 0) id BC22A21C65; Wed, 25 Sep 2019 14:45:43 +0200 (CEST) To: [email protected] From: [email protected] Auto-Submitted: auto-generated Subject: *** SECURITY information for domain-name.com *** Message-Id: <[email protected]> Date: Wed, 25 Sep 2019 14:45:43 +0200 (CEST) domain-name.com : Sep 25 14:45:43 : root : problem with defaults entries ; TTY=pts/0 ; PWD=/root ; USER=root ; From [email protected] Wed Sep 25 14:45:50 2019 Return-Path: <[email protected]> X-Original-To: [email protected] Delivered-To: [email protected] Received: from localhost (localhost.localdomain [127.0.0.1]) by vps123456.ovh.net (Postfix) with ESMTP id CDA5A21C65 for <[email protected]>; Wed, 25 Sep 2019 14:45:50 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at vps123456.ovh.net Received: from vps123456.ovh.net ([127.0.0.1]) by localhost (vps123456.ovh.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O9c_19tEMd7W for <[email protected]>; Wed, 25 Sep 2019 14:45:43 +0200 (CEST) Received: by vps123456.ovh.net (Postfix, from userid 0) id C5C0221C62; Wed, 25 Sep 2019 14:45:43 +0200 (CEST) To: [email protected] From: [email protected] Auto-Submitted: auto-generated Subject: *** SECURITY information for domain-name.com *** Message-Id: <[email protected]> Date: Wed, 25 Sep 2019 14:45:43 +0200 (CEST) domain-name.com : Sep 25 14:45:43 : root : unable to resolve host domain-name.com But Code: # dig @localhost domain-name.com 12.34.54.67 ; <<>> DiG 9.11.5-P4-5.1-Debian <<>> @localhost domain-name.com 12.34.54.67 ; (2 servers found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47015 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: 131ea911351303dedbc177a45d8b6307749ebb9b33a8ed28 (good) ;; QUESTION SECTION: ;domain-name.com. IN A ;; ANSWER SECTION: domain-name.com. 3600 IN A 12.34.54.67 ;; AUTHORITY SECTION: domain-name.com. 3600 IN NS ns2.domain-name.com. domain-name.com. 3600 IN NS ns1.domain-name.com. ;; ADDITIONAL SECTION: ns1.domain-name.com. 3600 IN A 12.34.54.67 ns2.domain-name.com. 3600 IN A 12.34.54.67 ;; Query time: 0 msec ;; SERVER: ::1#53(::1) ;; WHEN: Wed Sep 25 14:52:23 CEST 2019 ;; MSG SIZE rcvd: 158 ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 35360 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: 131ea911351303de53a128a85d8b63079becab84fb0e2272 (good) ;; QUESTION SECTION: ;12.34.54.67. IN A ;; AUTHORITY SECTION: . 7914 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019092500 1800 900 604800 86400 ;; Query time: 0 msec ;; SERVER: ::1#53(::1) ;; WHEN: Wed Sep 25 14:52:23 CEST 2019 ;; MSG SIZE rcvd: 144 What's wrong ? Thanks
I do not know. But I do know, that your name server works so it not much use to test that anymore. Please describe the setup that you have now. What kind of host is this? Which IP is the Failover IP? How have you set up this failover? I notice OVH has documentation on IP Failover, have you read them all and done the setup? What is in file /etc/network/interface on that host? What else is there to know of your setup? Then describe what is your goal, i.e. what are you trying to accomplish with this host and IP-numbers. Describe what you want the system to do.
I found it ! it was not the OVH fault To resume : vps123456.ovh.net is the name of my Vps with this IP= 89.10.112.113 this IP is used ONLY to manage the VPS. If I want use vps123456.ovh.net = 89.10.112.113 and share this IP to setup the domain name it's going to work, just need to add this IP 89.10.112.113 at OVH for my DNS ns1.domain.com But for many good reason that's not the best pratice and it's much better to get one dedicated IP for each domain name, let's call it IP FAILOVER Then I just need to buy a block Ripe and to get IP address, after I need to allocated one Ip per domain name, like this each domaine name have their own dedicated IP After I need to setup the reverse PTR on the domain name, if my dedicated IP is not added correctly in the server, my dedicated IP cannot reverse with the DNS at OVH. I was thinking the option in ISPconf system -> Server IP addresses" was doing the job, but apparently it's just show the Ip in ISPconfig but the server do not answer on eth0 with this IP (that's why # ping -c 3 87.98.149.60 was not working) IspConfig (system -> Server IP addresses") do not add in KeepAlived something like that : Code: vrrp_instance VI_1 { state MASTER interface eth0 virtual_router_id 101 priority 100 advert_int 1 authentication { auth_type PASS auth_pass 1111 } virtual_ipaddress { 87.98.149.60 } } For this reason Code: # host domain-name.com 12.34.54.67 Wasn't working The solution and the tutorial is on this link Now Code: # host domain-name.com 12.34.54.67 give me : Code: # host domain-name.com 12.34.54.67 Using domain server: Name: 12.34.54.67 Address: 12.34.54.67#53 Aliases: domain-name.com has address 12.34.54.67 domain-name.com mail is handled by 10 mail.domain-name.com. And everything is working... I don't now if my explainations are clear, I am just beginner with Linux and IspConfig, it was clear ? But maybe there is one more easy solution with IspConfig than use manually KeepAlived ?
Can you please answer me ? Should I use KeepAlived manually or there is one option with IspConfig that I don't know ? There is an other way to add an Ip on eth0 ? And ckeck here if the Ip have been add Code: # ip addr show eth0
