Public DNS

Discussion in 'ISPConfig 3 Priority Support' started by budgierless, Nov 25, 2015.

  1. budgierless

    budgierless Member

    Hi,

    I would like to set up FQDN that is resolvable externally, as when i use the ispconfig monitor app, the fqdn of my server dose not work and i ended up using my IP address for access. Also I think this is the main reason I have been having DNS issues,
    can i setup my FQDN so that it will forward to the sub-domain itself? for example, http://server1.domain.com
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    First you have to check if your own server is the authoritative DNS server for this domain or if the dns server of the ISP where you ordered the domain name is responsible for the DNS records. If your own server is the authoritative server, then you can add the dns zone for this domain in ispconfig and add an additional a-record for the server hostname in that zone.
     
  3. budgierless

    budgierless Member

    I just contacted godaddy and they told me I have authoritative DNS control from my end, can you give me an example of what the A record should look like that I need to add to my DNS template, please keep in mind that this is for a subdomain, not the domain itself, such as: server1.domain.com not dmain.com if that makes any difference, as I intend to to make my FQDN the same as the subdoamin.
     
  4. budgierless

    budgierless Member

    ok so, I was trying to do this by also adding revserse dns to my config, but I think I have made a mistake, I cant find any errors in the logs, but its not working, please check my config;
    Code:
    $TTL        3600
    @       IN      SOA     ns1.mydomain. admin.mydomain. (
                            2015112704       ; serial, todays date + todays serial #
                            14400              ; refresh, seconds
                            3600              ; retry, seconds
                            604800              ; expire, seconds
                            86400 )            ; minimum, seconds
    ;
    
    mail 3600 A        81.000.000.209
    mmg1 3600 A        81.000.000.209
    mydomain. 3600 A        81.000.000.209
    mx 3600 A        81.000.000.209
    ns1 3600 A        81.000.000.209
    ns2 3600 A        81.000.000.209
    www 3600 A        81.000.000.209
    billing 3600      CNAME        mydomain.
    clients 3600      CNAME        mydomain.
    hosting 3600      CNAME        mydomain.
    red5 3600      CNAME        mydomain.
    support 3600      CNAME        mydomain.
    mydomain. 3600      MX    1   mail.mydomain.
    mydomain. 3600      MX    100   mx.mydomain.
    mydomain. 3600      MX    10   mmg1.mydomain.
    mydomain. 3600      NS        ns1.mydomain.
    mydomain. 3600      NS        ns2.mydomain.
    1 3600      PTR        mmg1.mydomain.
    2 3600      PTR        mail.mydomain.
    3 3600      PTR        mx.mydomain.
    mydomain. 3600      TXT        "v=spf1 a mx ptr ip4:81.000.000.209 a:mydomain -all"
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    Remove the PTR records. PTR records are only in reverse zones (the zones of IP addresses) and not in the zone of your domain. The errors of the BIND daemon are in the syslog of the Linux system.
     
  6. budgierless

    budgierless Member

    Yes, Im trying to add reverse zones for the IP, how to I do this?
     
  7. till

    till Super Moderator Staff Member ISPConfig Developer

    The PTR records have to be added into the reverse zone and not the domain. There is an example on how to create a reverse zone in the ISPConfig manual.
     
  8. budgierless

    budgierless Member

    ok this is the PTR I made for the IP:
    Code:
    $TTL        3600
    @       IN      SOA     ns1.mydomain. webmaster.mydomain. (
                            2015112707       ; serial, todays date + todays serial #
                            28800              ; refresh, seconds
                            7200              ; retry, seconds
                            604800              ; expire, seconds
                            86400 )            ; minimum, seconds
    ;
    
    2XX.XXX.81.in-addr.arpa. 3600      NS        ns1.mydomain.
    2XX.XXX.81.in-addr.arpa. 3600      NS        ns2.mydomain.
    209 3600      PTR        mydomain.
    is the right? it loaded with no errors, but my FQDN is like server1.mydomain.com so should server1 so not beused somewhere in this DNS zone???
     
  9. till

    till Super Moderator Staff Member ISPConfig Developer

    Replace mydomain. with server1.mydomain.com. in that zone.
     
  10. budgierless

    budgierless Member

    Done that now thanks, what about ns1, is that ok for this kind of zone, or should that be server1 aswell?

    Also should this also include a SPF record?
     
    Last edited: Nov 28, 2015
  11. till

    till Super Moderator Staff Member ISPConfig Developer

    Thats ok, as long as ns1 and ns2 exits as A-Records in the mydomain.tld zone.

    No. SPF records are for email and email addresses never use an IP.
     
    budgierless likes this.
  12. budgierless

    budgierless Member

    think it working now, just testing.
     

Share This Page