Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: [SOLVED] DNS ERROR resolving

  1. #1
    ruben.rodrigues Guest

    Default [SOLVED] DNS ERROR resolving

    Hi!

    I'm trying to install zimbra but no success so far.

    My router is my dns server and it does not recognize my server hostname. how bad is this?

    Operations logged to /tmp/zmsetup.10202009-164728.log
    Installing LDAP configuration database...done.
    Setting defaults...hostname: Unknown host
    No results returned for A lookup of
    Checked nameservers:
    192.168.1.1


    DNS ERROR resolving
    It is suggested that the hostname be resolveable via DNS
    Change hostname [Yes]

  2. #2
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Quote Originally Posted by ruben.rodrigues View Post
    Hi!

    I'm trying to install zimbra but no success so far.

    My router is my dns server and it does not recognize my server hostname. how bad is this?
    It's very bad, you need to install a Split DNS.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  3. #3
    Join Date
    Oct 2009
    Posts
    17
    Rep Power
    6

    Default

    i have the same problem, but my server isn't behind a router....... it have a public ip......

    how do i resolve this...........????

    error2.jpg
    Last edited by padial; 10-26-2009 at 10:54 AM.

  4. #4
    Join Date
    May 2009
    Location
    Jakarta
    Posts
    86
    Rep Power
    6

    Default

    U need fixed dns setup..
    Zimbra can't work without FQDN so u must have that qualify domain...

    example:
    I've domain "dipekso.net"
    and i want setup mail server using zimbra so i must have valid MX record that pointing to zimbra mail server, hm..., hostname also needed by zimbra so u must attend it..

    Example for my domain record

    $ dig -t mx dipekso.net

    ; <<>> DiG 9.5.1-P2 <<>> -t mx dipekso.net
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25567
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 6

    ;; QUESTION SECTION:
    ;dipekso.net. IN MX

    ;; ANSWER SECTION:
    dipekso.net. 10800 IN MX 20 mail2.dipekso.net.
    dipekso.net. 10800 IN MX 10 mail.dipekso.net.

    ;; AUTHORITY SECTION:
    dipekso.net. 112 IN NS ns1.dipekso.net.
    dipekso.net. 112 IN NS ns2.dipekso.net.
    dipekso.net. 112 IN NS mbahrip.dipekso.net.
    dipekso.net. 112 IN NS mbahnyet.dipekso.net.

    ;; ADDITIONAL SECTION:
    mail.dipekso.net. 112 IN A 10.0.100.3
    mail2.dipekso.net. 10800 IN A 10.0.100.4
    ns2.dipekso.net. 3476 IN A 10.0.100.14
    ns1.dipekso.net. 10800 IN A 10.0.100.13

    ;; Query time: 115 msec

    And /etc/hosts
    $ cat /etc/hosts
    # Do not remove the following line, or various programs
    # that require network functionality will fail.
    127.0.0.1 localhost.localdomain localhost
    ::1 localhost6.localdomain6 localhost6
    10.0.100.3 mail.dipekso.net mail

    If You have valid domain name and dns setup i think the problem was solved...

  5. #5
    Join Date
    Oct 2009
    Posts
    17
    Rep Power
    6

    Default

    i think that the problem its in my zone, look at the hosts and zone files.... my hostname is correo
    hosts.jpg
    zone.jpg

    thanks

  6. #6
    Join Date
    Feb 2007
    Location
    Portland, OR
    Posts
    1,147
    Rep Power
    10

    Default

    padial you have your MX records set to your name servers ns1 and sn2, and the only other A record for the domain you show is domain.cl

    However... your hosts file shows correo.domain.com as the name of the Zimbra server. You should remove the second MX record, and change the first to point to "correo.domain.com." as well as add correo to the list of A records for your domain.

  7. #7
    Join Date
    Oct 2009
    Posts
    17
    Rep Power
    6

    Default

    sorry, this is my configuration

    hostname: correo
    fqdn: correo.example.cl

    hostsexample.jpg

    examplezone.jpg

    i have another zimbra server with the same conf and it worked perfectly

    thanks for answer so fast

  8. #8
    Join Date
    Feb 2007
    Location
    Portland, OR
    Posts
    1,147
    Rep Power
    10

    Default

    I have no idea how it "worked perfectly" because your DNS is configured wrong. There is still no A record for correo.example.cl, until this exists (and a matching PTR record!) this test WILL fail.

  9. #9
    Join Date
    Oct 2009
    Posts
    17
    Rep Power
    6

    Default

    the line that says :

    example.cl IN A 200.42.X.Y

    doesn't create the A record for correo.example.cl ?
    if not, how should i make that record?

  10. #10
    Join Date
    Feb 2007
    Location
    Portland, OR
    Posts
    1,147
    Rep Power
    10

    Default

    Actually looking closer... I'm not sure how that is working at all. BIND must be seeing your configuration and transparently fixing this for you. Here is what your configuration should probably look like
    Code:
    $TTL 604800
    @               IN SOA          ns1.example.cl. hostmaster.example.cl. (
                                    1       ; serial
                                    86400           ; refresh
                                    7200            ; retry
                                    1209600         ; expiry
                                    10800 )         ; minimum
    
    example.cl.     IN NS   ns1.example.cl.
    example.cl.     IN MX   0 correo.example.cl.
    example.cl.     IN A    200.42.X.Y
    www             IN A    200.42.X.Y
    ns1             IN A    200.42.X.Y
    correo          IN A    200.42.X.Y
    Now there are still a few things that could be wrong with the above. In the example you are posting you keep on showing a ns1 and a ns2... but you have them as the same address. This is absolutely pointless. If there really is 2 name servers then add back in that entry.

    In your original file you have the master name server set as the domain name, this is wrong and is corrected above. You also have ns1 and ns2 setup as your MX records, again if these are separate servers, and actually are Mail servers (that forward to correo?) then this may be correct, but in the example above I assumed that you want mail delivered directly to correo.

    Your original file was also missing a "." at the end of all the "example.cl" which would make BIND expand it to "example.cl.example.cl."

    You also had a localhost.example.cl A record in there pointing to 127.0.0.1.... this is absolutely bogus data and will be rejected by any properly configured DNS client.

    To add the correo.example.cl record see above. Since you seem to be pointing everything to the same, singular, public IP address I put the same address for it as well.

    Remember that your PTR records will also need to be set to show the PTR record for 200.42.X.Y (or whatever the address for correo.example.cl is) pointing to correo.example.cl. This will probably need to be done by your ISP as they are most likely the ones who control the PTR record for your address space.

    Also in the future rather then posting a screenshot please use the [ code] [ /code] tags (without the spaces), or click the # symbol at the top after selecting a block of text.

Similar Threads

  1. Replies: 5
    Last Post: 08-28-2009, 09:35 AM
  2. DNS ERROR resolving MX for mail.domain.com
    By csoliss in forum Installation
    Replies: 11
    Last Post: 04-29-2008, 08:32 AM
  3. ZCS ROCKS! Need some DNS help!
    By SiteDiscovery in forum Administrators
    Replies: 9
    Last Post: 12-30-2006, 09:50 PM
  4. DNS in a nutshell part two (For dummies)
    By daimer77 in forum Installation
    Replies: 4
    Last Post: 12-18-2006, 05:28 PM
  5. DNS Strategies and Best Practices, and a SLES10 Request
    By LMStone in forum Administrators
    Replies: 4
    Last Post: 10-14-2006, 07:51 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •