Results 1 to 7 of 7
  1. #1
    Join Date
    Mar 2004
    Location
    Tokyo / Japan
    Posts
    489

    DNS Setup troubleshooting

    Hello everybody,

    I am trying to setup the DNS server for the test domain http://www.wois.net .

    I set the nameservers to

    ns1.wois.net (221.186.130.211)
    ns2.wois.net (221.186.130.212)
    ns3.wois.net (221.186.130.213)

    When I do a whois than all 3 nameservers show up. Also all 3 domain servers are runing. Only Server 1 and 3 are actually accessable from the web by the global IP.

    Do cut the story shorter it seems to me that the DNS does not resolv correctly. For now please ignore the time settings (unless they are totally wrong of course. I set them short in order to be able to change the settings once it resolves correctly.
    All settings were done 4 days ago, so the resolving around the globe should have gone through by now ;-)

    How can I check that the announcements are actually reaching the 13 root servers ?
    Perhaps Do I need to open any other port than 25 and 80 on the router side in order to make it work ?

    Any reply and pointing into the right direction is much appreciated.
    I post my setup files below.

    (Note that the system is running on Debian Sarge. You may find that the config files are different from another distro)

    Best regards

    Nils Valentin


    -------- named.conf--------

    // This is the primary configuration file for the BIND DNS server named.
    //
    // Please read /usr/share/doc/bind/README.Debian for information on the
    // structure of BIND configuration files in Debian for BIND versions 8.2.1
    // and later, *BEFORE* you customize this configuration file.
    //

    include "/etc/bind/named.conf.options";

    // reduce log verbosity on issues outside our control
    logging {
    category lame-servers { null; };
    category cname { null; };
    };

    // prime the server with knowledge of the root servers
    zone "." {
    type hint;
    file "/etc/bind/db.root";
    };

    // be authoritative for the localhost forward and reverse zones, and for
    // broadcast zones as per RFC 1912

    zone "localhost" {
    type master;
    file "/etc/bind/db.local";
    };

    zone "127.in-addr.arpa" {
    type master;
    file "/etc/bind/db.127";
    };

    zone "0.in-addr.arpa" {
    type master;
    file "/etc/bind/db.0";
    };

    zone "255.in-addr.arpa" {
    type master;
    file "/etc/bind/db.255";
    };

    // add local zone definitions here
    include "/etc/bind/named.conf.local";

    -------named.conf.local---------
    //
    // Add local zone definitions here.

    zone "wois.net" {
    type master;
    file "/etc/bind/wois.net";
    };

    zone "130.186.221.in-addr.arpa" {
    type master;
    file "/etc/bind/wois.net.rev";
    };

    -------wois.net--------------

    $TTL 900
    wois.net. IN SOA ns3.wois.net. root.ns3.wois.net. (
    200405251 ; Serial
    900 ; Refresh 1 hour
    900 ; Retray 1 hour
    1200 ; Expire 100 hours
    900 ; Minimum 24 hours
    );

    IN NS ns1.wois.net.
    IN NS ns2.wois.net.
    IN NS ns3.wois.net.
    IN MX 10 ns1.
    ;
    ;hosts
    ;

    ns1 IN A 221.186.130.211
    ns2 IN A 221.186.130.212
    ns3 IN A 221.186.130.213
    ;
    ;alias
    ;
    ;dns IN CNAME ns1
    www IN CNAME ns1
    ftp IN CNAME ns1


    -------- wois.net.rev----------

    $TTL 900
    130.186.221.in-addr.arpa. IN SOA ns3.wois.net. root.ns3.wois.net. (
    200405251 ; Serial
    900 ; Refresh hour
    900 ; Retray 1 hour
    1200 ; Expire 100 hours
    900 ; Minimum 24 hours
    );

    IN NS ns1.wois.net.
    IN NS ns2.wois.net.
    IN NS ns3.wois.net.
    ;pointer to hosts
    ;
    211 IN PTR ns1.wois.net.
    212 IN PTR ns2.wois.net.
    213 IN PTR ns3.wois.net.
    __--- Nils Valentin ---
    ☆★☆ Speedtest One: Tokyo / Japan ☆★☆ / Feedback
    ☆★☆ Speedtest Two: Tokyo / Japan ☆★☆ / Feedback

  2. #2
    Join Date
    Jan 2004
    Posts
    445
    Port 53?

  3. #3
    Join Date
    Mar 2004
    Location
    Tokyo / Japan
    Posts
    489
    Hi sawbuck,

    That is / was exactly one of my concerns. Will it be really necessary to open the port 53 ? If I understand that correctly, then the nameservers are going to "broadcast" that they are there. So when an internet client requests information shouldnt that information be coming from the root servers (meaning, that we dont need to open the port 53 at the router) ?

    Am I mistaken ?
    __--- Nils Valentin ---
    ☆★☆ Speedtest One: Tokyo / Japan ☆★☆ / Feedback
    ☆★☆ Speedtest Two: Tokyo / Japan ☆★☆ / Feedback

  4. #4
    Recursive resolving DNS servers (the DNS server for the user) request host information directly from your NSes. You need to open at least UDP port 53 to the world.
    ::. www.diginode.net : Dedicated Servers : Virtual Machine Servers .::
    ::. Industry-Leading Remote Server Management .::
    ::. Automatic OS Re-image : Instant Server Reboot : Remote Serial Console .::
    ::. Over 20 OSes to choose from : Install a new OS every day .::

  5. #5
    Join Date
    Mar 2004
    Location
    Tokyo / Japan
    Posts
    489
    Hi diginode,

    Thank you for the reply. What you say makes since. I appreciate your reply.

    Assuming the port 53 is open and the issue remains. What would be other
    failure factors to be considered ?
    __--- Nils Valentin ---
    ☆★☆ Speedtest One: Tokyo / Japan ☆★☆ / Feedback
    ☆★☆ Speedtest Two: Tokyo / Japan ☆★☆ / Feedback

  6. #6
    Join Date
    Jul 2002
    Location
    Alberta, Canada
    Posts
    348
    Are the nameserver IP's registered?

    http://www.dnsreport.com/tools/dnsre...omain=wois.net cannot even connect, so it appears that port 53 isnt open still.
    AC Host Canada Affordable Canadian Web Hosting Solutions
    Shared Hosting | Email Hosting | DNS Hosting | Custom Plans Available
    Website: www.achost.ca email: [email protected]

  7. #7
    Join Date
    Mar 2004
    Location
    Tokyo / Japan
    Posts
    489
    Hi achost_ca,

    Thanks for the reply. I found the issue. UDP AND TCP must be enabled in order to work proberly.

    There are still some other issues, but that was the show stopper ;-)

    Thanks a lot
    __--- Nils Valentin ---
    ☆★☆ Speedtest One: Tokyo / Japan ☆★☆ / Feedback
    ☆★☆ Speedtest Two: Tokyo / Japan ☆★☆ / Feedback

Posting Permissions

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