Sub domain under ispconfig

Discussion in 'General' started by Oitsuki, Jul 6, 2018.

Tags:
  1. Oitsuki

    Oitsuki Member

    Code:
    nano /etc/hostname
    ns304677
    
    myhostname server is :
    Code:
    Ubuntu 18.04 LTS
    
      Linux ubuntu 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
    
    
      Server   : 33xxxx
      IPv4       : 94.23.xx.34
      IPv6       : 2001:41d0:2:5922::1
      Hostname   : ns304677.ip-94-23-xxx.eu
    
    
    Maybe I must change ns304677 by ns304677.ip-94-23-xxx.eu ???
    What do you think ?
     
  2. Jesse Norell

    Jesse Norell Well-Known Member

    So ns304677.ip-94-23-xxx.eu is your ispconfig server? That one is answering DNS for your domain; try adding demo2 back and see if it works. If so, then all you have to do is track down why ns.kimsufi.com can't be queried, and make sure it's getting updates from your ispconfig dns changes, and you should be good ?

    No, I don't expect that would help anything. What were you thinking it might accomplish?
     
  3. ahrasis

    ahrasis Well-Known Member

    I might be wrong when I wrote my earlier replies and this as well, so correct me if I am wrong.

    I think you might want to check the manual and the tutorial in here before we all keep guessing on how to fix your domain / subdomain dns issues.

    Basically if you build a server based on a perfect server or the manual, you will have only a dns server, which I think may not be enough since a domain basically would require two dns servers to be resolved to.

    A note from the tutorial is that you need two servers with two different public IP addresses and with ISPConfig 3 installed and dns A records for both servers must already existed before you proceed.

    So, if you don't have the required basic dns servers for your domain / subdomain dns to work properly, I would rather suggest the use of free dns services like freedns.afraid.org or zoneedit.com or cloudflare.com to help you.
     
  4. Oitsuki

    Oitsuki Member

    I installed the server based on Kimsufi (OVH) ubuntu 18.4 server. This is an automatic install.
    Accross the kimsufi pane when you create an new website, you must declare the new website and the server
    Also you must create the website and the dns across ispconfig (of course !)
    At the end I follow this tutorial step by step without error : https://www.howtoforge.com/tutorial...l-pureftpd-bind-postfix-doveot-and-ispconfig/
     
  5. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    So this is a new install, first Ubuntu 18.04 from Kimsufi and then ISPConfig 3.1 installed on top of that, is this correct?
    The Perfect Server tutorial assumes ISPConfig is installed on an empty server, so if that Kimsufi Ubuntu already installed and set up something it is possible the ISPConfig installation is broken.
    You started this thread with
    ,
    But so far it looks like the DNS name service is not working at all. Is the bind9 now running on your name service host? Check with ISPConfig Panel Monitor tab. Then check with command
    Code:
    systemctl status bind9
    on that name server host.
    If bind9 is running and name service still does not work, it is getting pointless to guess further what might be wrong. If you can reveal what is the real full host and domain name you are creating, then it is easier to check what is wrong. Or find someone you trust and knows name service to set it up for you.
     
  6. Oitsuki

    Oitsuki Member

    bind9.service - BIND Domain Name Server
    Loaded: loaded (/lib/systemd/system/bind9.service; enabled; vendor preset: enabled)
    Active: active (running) since Tue 2018-07-10 19:00:35 UTC; 1 day 22h ago
    Docs: man:named(8)
    Process: 25465 ExecReload=/usr/sbin/rndc reload (code=exited, status=0/SUCCESS)
    Main PID: 21358 (named)
    Tasks: 7 (limit: 4915)
    CGroup: /system.slice/bind9.service
    └─21358 /usr/sbin/named -f -u bind

    juil. 12 15:37:06 ns304xxxx named[21358]: client @0x7fb170029ed0 54.37.80.36#51455 (xxxxx.com): zone transfer 'xxxxx.com/AXFR/I
    juil. 12 15:42:53 ns304xxxx named[21358]: SERVFAIL unexpected RCODE resolving '81.5.158.185.dnsbl.sorbs.net/A/IN': 174.36.xxxx.232#53
    juil. 12 16:28:06 ns304xxxx named[21358]: client @0x7fb1703e3d90 213.186.33.199#43749 (yyyyyyy.fr): zone transfer 'yyyyyyy.fr/AXF
    juil. 12 16:33:05 ns304xxxx named[21358]: client @0x7fb170001f70 54.37.80.36#37247 (yyyyyyy.fr): zone transfer 'yyyyyyy.fr/AXFR/I
    juil. 12 17:13:14 ns304xxxx named[21358]: REFUSED unexpected RCODE resolving 'trainhr.com/TXT/IN': 2607:f208:206::6#53
    juil. 12 17:13:14 ns304xxxx named[21358]: REFUSED unexpected RCODE resolving 'trainhr.com/TXT/IN': 216.69.185.6#53
    juil. 12 17:13:14 ns304677 named[21358]: REFUSED unexpected RCODE resolving 'trainhr.com/TXT/IN': 2603:5:2290::6#53
    juil. 12 17:13:14 ns304xxxx named[21358]: REFUSED unexpected RCODE resolving 'trainhr.com/TXT/IN': 173.201.73.6#53
    juil. 12 17:38:56 ns304xxxx named[21358]: client @0x7fb168712330 213.186.33.199#55165 (zzzzzzzzz.net): zone transfer 'zzzzzzzzz.net/AXF
    juil. 12 17:38:56 ns304xxxx named[21358]: client @0x7fb17818a590 54.37.80.36#46029 (zzzzzzzzz.net): zone transfer 'zzzzzzzzz.net/AXFR/I
    ~
     
  7. ahrasis

    ahrasis Well-Known Member

    This is not entirely true. You do not have to enable dns service or install its apt or manage your own dns while creating a website in ISPConfig. You can use external dns services that I mentioned earlier. There a lot more out there too.
     

Share This Page