The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

DNS Problem..

Discussion in 'Bind / DNS / Nameserver Issues' started by jpan, Dec 6, 2001.

  1. jpan

    jpan Member

    Joined:
    Aug 12, 2001
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    1
    around every 6-8 hours, my client can\'t access their website with domain name, but IP is fine...
    than after i restart bind and everything back fine....
    Is anyone have this problem?


    [Edited on 12/6/01 by jpan]
     
  2. feanor

    feanor Well-Known Member

    Joined:
    Aug 13, 2001
    Messages:
    836
    Likes Received:
    0
    Trophy Points:
    16
    First off, perhaps you should monitor your nameserver a bit more often? It is a pretty vital service, like set up something to poll it remotely every 2/3 minutes or something like that.

    Hopefully you have extended logging setup for your nameserver? You can check why it is failing/crashing at /var/log/bind, (default)... or wherever you have that log building.

    Good luck.
     
  3. moronhead

    moronhead Well-Known Member

    Joined:
    Aug 12, 2001
    Messages:
    706
    Likes Received:
    0
    Trophy Points:
    16
    Feanor,[quote:25356fb3b2]First off, perhaps you should monitor your nameserver a bit more often? It is a pretty vital service, like set up something to poll it remotely every 2/3 minutes or something like that.

    Hopefully you have extended logging setup for your nameserver? You can check why it is failing/crashing at /var/log/bind, (default)... or wherever you have that log building.

    Good luck.[/quote:25356fb3b2]Can\'t see /var/log/bind on our server. How do you create this file?

    And how do you poll the DNS remotely?
     
  4. ewindisch

    ewindisch Member

    Joined:
    Sep 9, 2001
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    1
    To poll dns remotely, you can either open a socket to that server\'s DNS port (if the port is not open, it is not running).. or you can use some pre-existing software such as DiG to test.

    Of course, you cannot restart bind remotely.. it would be a good idea to just have a cronjob that checks for a running named process, if one does not exist.. create one :)
     
  5. feanor

    feanor Well-Known Member

    Joined:
    Aug 13, 2001
    Messages:
    836
    Likes Received:
    0
    Trophy Points:
    16
    Put this at the top of your named.conf....
    *be careful*

    ---------------------------
    // Advanced logging configuration ...
    options {
    directory \"/var/named\";
    };
    logging {
    channel default_log {
    file \"/var/log/bind\" versions 4 size 25m;
    print-category yes;
    print-severity yes;
    print-time yes;
    };
    category default { default_log; };
    category panic { default_log; };
    category packet { default_log; };
    category eventlib { default_log; };
    };

    --------------------------
    Then your named.conf continues with your hint zone, or what have you....

    Remotely polling/monitoring a nameserver? There are tons of products out there that do this as well as a variety of other services. http://www.deepmetrix.com/ has my favorite monitoring software. (IPMonitor)

    There are free ones out there, naturally, it\'s up to you to find the ones that are actually worth utilizing.


    Peace.

    :P
     
  6. moronhead

    moronhead Well-Known Member

    Joined:
    Aug 12, 2001
    Messages:
    706
    Likes Received:
    0
    Trophy Points:
    16
    [quote:5d01b36222]Put this at the top of your named.conf....
    *be careful*
    [/quote:5d01b36222]Thanks. We put those lines in and restarted named. But /var/log/bind hasn\'t been created as yet.

    We got these errors when reloading ndc:

    unknown logging category \'eventlib\' ignored
    unknown logging category \'packet\' ignored
    unknown logging category \'panic\' ignored

    Any ideas?
     
  7. feanor

    feanor Well-Known Member

    Joined:
    Aug 13, 2001
    Messages:
    836
    Likes Received:
    0
    Trophy Points:
    16
    Ancient version of bind perhaps?
    What version do you have?
    I would recommend 8.2.3 or H-I-G-H-E-R



    :P
     
  8. moronhead

    moronhead Well-Known Member

    Joined:
    Aug 12, 2001
    Messages:
    706
    Likes Received:
    0
    Trophy Points:
    16
    [quote:f33a17973b]Ancient version of bind perhaps?
    What version do you have?
    I would recommend 8.2.3 or H-I-G-H-E-R
    [/quote:f33a17973b] Vers. 9.1.0
     
  9. feanor

    feanor Well-Known Member

    Joined:
    Aug 13, 2001
    Messages:
    836
    Likes Received:
    0
    Trophy Points:
    16
    That doesn\'t count as higher necessarily.
    It\'s a long story, and I am running out of steam for the day- I have no idea why that version doesn\'t have these options, I have always stuck with the \"8\" breed of bind.

    Look at the docs for that version with how to enable advanced logging and then specify a logfile and all will be revealed to you.
     
  10. jpan

    jpan Member

    Joined:
    Aug 12, 2001
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    1
    I just flowing the step and setup the bind log, this is what error log is..
    Please Help...

    07-Dec-2001 19:19:08.697 default: info: sysquery: findns error (NXDOMAIN) on ns3.mydomain.org?
    07-Dec-2001 19:19:08.697 default: info: sysquery: findns error (NXDOMAIN) on ns4.mydomain.org?
    07-Dec-2001 19:19:09.955 default: info: sysquery: findns error (NXDOMAIN) on ns3.mydomain.org?
    07-Dec-2001 19:19:09.955 default: info: sysquery: findns error (NXDOMAIN) on ns4.mydomain.org?
    07-Dec-2001 19:19:37.897 default: info: sysquery: findns error (NXDOMAIN) on ns3.mydomain.org?
    07-Dec-2001 19:19:37.897 default: info: sysquery: findns error (NXDOMAIN) on ns4.mydomain.org?
    07-Dec-2001 19:19:41.372 default: info: sysquery: findns error (NXDOMAIN) on ns3.mydomain.org?
    07-Dec-2001 19:19:41.372 default: info: sysquery: findns error (NXDOMAIN) on ns4.mydomain.org?
    07-Dec-2001 19:20:10.056 default: info: sysquery: findns error (NXDOMAIN) on ns3.mydomain.org?
     
  11. feanor

    feanor Well-Known Member

    Joined:
    Aug 13, 2001
    Messages:
    836
    Likes Received:
    0
    Trophy Points:
    16
    Your hint zone is screwed up.
    You need this file, from InterNIC... You probably have it somewhere on your machine or you can FTP up to the internic\'s site and grab the current master nameserver zone file.

    Did you accidentally wipe out this chunk of configuration?
    (or similar)

    Check /var/log/bind, for errors with the \"hint\" zone.

    ................

    zone \".\" {
    type hint;
    file \"named.root\";
    };

    .................
     
  12. jpan

    jpan Member

    Joined:
    Aug 12, 2001
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    1
    Thanks for your replay,this is what i have in my named.conf
    zone \".\" IN {
    type hint;
    file \"named.ca\";
    };

    zone \"localhost\" IN {
    type master;
    file \"localhost.zone\";
    allow-update { none; };
    };

    zone \"0.0.127.in-addr.arpa\" IN {
    type master;
    file \"named.local\";
    allow-update { none; };
    };
    zone \"domain.org\" {
    type master;
    file \"/var/named/domain.org.db\";
    ____________________________________________
    and those is my bind log for today..
    ____________________________________________
    Thanks for your help....

    08-Dec-2001 09:15:56.962 load: info: hint zone \"\" (IN) loaded (serial 0)
    08-Dec-2001 09:15:56.985 load: info: master zone \"localhost\" (IN) loaded (serial 42)
    08-Dec-2001 09:15:56.986 load: info: master zone \"0.0.127.in-addr.arpa\" (IN) loaded (serial 1997022700)
    08-Dec-2001 09:15:56.986 load: info: master zone \"domain.org\" (IN) loaded (serial 1006564489)
    08-Dec-2001 09:15:56.987 load: info: master zone \"vcd100.com\" (IN) loaded (serial 1006874668)
    08-Dec-2001 09:15:56.996 load: info: master zone \"myjphost.com\" (IN) loaded (serial 1007556340)
    08-Dec-2001 09:15:56.997 load: info: master zone \"enew90.com\" (IN) loaded (serial 1007673687)
    08-Dec-2001 09:15:56.998 default: info: listening on [127.0.0.1].53 (lo)
    08-Dec-2001 09:15:56.998 default: info: listening on [209.223.116.225].53 (eth0)
    08-Dec-2001 09:15:56.998 default: info: listening on [209.223.116.226].53 (eth0:1)
    08-Dec-2001 09:15:56.998 default: info: listening on [209.223.116.227].53 (eth0:2)
    08-Dec-2001 09:15:56.998 default: info: listening on [209.223.116.228].53 (eth0:3)
    08-Dec-2001 09:15:56.998 default: info: listening on [209.223.116.229].53 (eth0:4)
    08-Dec-2001 09:15:56.998 default: info: listening on [209.223.116.230].53 (eth0:5)
    08-Dec-2001 09:15:56.998 default: info: listening on [209.223.116.231].53 (eth0:6)
    08-Dec-2001 09:15:56.998 default: info: listening on [209.223.116.232].53 (eth0:7)
    08-Dec-2001 09:15:56.998 default: info: listening on [209.223.116.233].53 (eth0:8)
    08-Dec-2001 09:15:56.998 default: info: listening on [209.223.116.234].53 (eth0:9)
    08-Dec-2001 09:15:56.998 default: info: listening on [209.223.116.235].53 (eth0:10)
    08-Dec-2001 09:15:56.998 default: info: listening on [209.223.116.236].53 (eth0:11)
    08-Dec-2001 09:15:56.998 default: info: listening on [209.223.116.237].53 (eth0:12)
    08-Dec-2001 09:15:56.999 default: info: listening on [209.223.116.238].53 (eth0:13)
    08-Dec-2001 09:15:56.999 default: info: listening on [209.223.116.239].53 (eth0:14)
    08-Dec-2001 09:15:56.999 default: info: Forwarding source address is [0.0.0.0].1054
    08-Dec-2001 09:15:57.004 security: info: group = 25
    08-Dec-2001 09:15:57.005 security: info: user = named
    08-Dec-2001 09:15:57.005 default: notice: Ready to answer queries.
    08-Dec-2001 09:15:58.506 default: info: sysquery: findns error (NXDOMAIN) on ns3.domain.org?
    08-Dec-2001 09:15:58.506 default: info: sysquery: findns error (NXDOMAIN) on ns4.domain.org?
    08-Dec-2001 09:15:59.338 default: info: sysquery: findns error (NXDOMAIN) on ns3.domain.org?
    08-Dec-2001 09:15:59.338 default: info: sysquery: findns error (NXDOMAIN) on ns4.domain.org?
    08-Dec-2001 09:15:59.446 default: info: sysquery: findns error (NXDOMAIN) on ns3.domain.org?
    08-Dec-2001 09:15:59.446 default: info: sysquery: findns error (NXDOMAIN) on ns4.domain.org?
    08-Dec-2001 09:16:01.449 default: info: sysquery: findns error (NXDOMAIN) on ns3.domain.org?
    08-Dec-2001 09:16:01.450 default: info: sysquery: findns error (NXDOMAIN) on ns4.domain.org?
    08-Dec-2001 09:16:02.105 default: info: sysquery: findns error (NXDOMAIN) on ns3.domain.org?
    08-Dec-2001 09:16:02.105 default: info: sysquery: findns error (NXDOMAIN) on ns4.domain.org?
    08-Dec-2001 09:16:03.524 default: info: sysquery: findns error (NXDOMAIN) on ns3.domain.org?
    08-Dec-2001 09:16:03.524 default: info: sysquery: findns error (NXDOMAIN) on ns4.domain.org?
    08-Dec-2001 09:16:32.197 default: info: sysquery: findns error (NXDOMAIN) on ns3.domain.org?
    08-Dec-2001 09:16:32.197 default: info: sysquery: findns error (NXDOMAIN) on ns4.domain.org?
    08-Dec-2001 09:16:50.717 default: info: sysquery: findns error (NXDOMAIN) on ns3.domain.org?
    08-Dec-2001 09:16:50.717 default: info: sysquery: findns error (NXDOMAIN) on ns4.domain.org?
    08-Dec-2001 09:17:04.315 default: info: sysquery: findns error (NXDOMAIN) on ns3.domain.org?
    08-Dec-2001 09:17:04.315 default: info: sysquery: findns error (NXDOMAIN) on ns4.domain.org?
    08-Dec-2001 09:17:38.792 default: info: sysquery: findns error (NXDOMAIN) on ns3.domain.org?
    keep repeat about 100 times...
     
  13. jpan

    jpan Member

    Joined:
    Aug 12, 2001
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    1
    another information for named.ca file..
    This is what i have in my named.ca
    thanks for your help....
    ___________________________________________

    ; This file holds the information on root name servers needed to
    ; initialize cache of Internet domain name servers
    ; (e.g. reference this file in the \"cache . <file>\"
    ; configuration file of BIND domain name servers).
    ;
    ; This file is made available by InterNIC registration services
    ; under anonymous FTP as
    ; file /domain/named.root
    ; on server FTP.RS.INTERNIC.NET
    ; -OR- under Gopher at RS.INTERNIC.NET
    ; under menu InterNIC Registration Services (NSI)
    ; submenu InterNIC Registration Archives
    ; file named.root
    ;
    ; last update: Aug 22, 1997
    ; related version of root zone: 1997082200
    ;
    ;
    ; formerly NS.INTERNIC.NET
    ;
    . 3600000 IN NS A.ROOT-SERVERS.NET.
    A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4
    ;
    ; formerly NS1.ISI.EDU
    ;
    . 3600000 NS B.ROOT-SERVERS.NET.
    B.ROOT-SERVERS.NET. 3600000 A 128.9.0.107
    ;
    ; formerly C.PSI.NET
    ;
    . 3600000 NS C.ROOT-SERVERS.NET.
    C.ROOT-SERVERS.NET. 3600000 A 192.33.4.12
    ;
    ; formerly TERP.UMD.EDU
    ;
    . 3600000 NS D.ROOT-SERVERS.NET.
    D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90
    ;
    ; formerly NS.NASA.GOV
    ;
    . 3600000 NS E.ROOT-SERVERS.NET.
    E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10
    ;
    ; formerly NS.ISC.ORG

    . 3600000 NS F.ROOT-SERVERS.NET.
    F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241
    ;
    ; formerly NS.NIC.DDN.MIL
    ;
    . 3600000 NS G.ROOT-SERVERS.NET.
    G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4
    ;
    ; formerly AOS.ARL.ARMY.MIL
    ;
    . 3600000 NS H.ROOT-SERVERS.NET.
    H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53
    ;
    ; formerly NIC.NORDU.NET
    ;
    . 3600000 NS I.ROOT-SERVERS.NET.
    I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17
    ;
    ; temporarily housed at NSI (InterNIC)
    ;
    . 3600000 NS J.ROOT-SERVERS.NET.
    J.ROOT-SERVERS.NET. 3600000 A 198.41.0.10
    ;
    ; housed in LINX, operated by RIPE NCC
    ;
    . 3600000 NS K.ROOT-SERVERS.NET.
    K.ROOT-SERVERS.NET. 3600000 A 193.0.14.129
    ;
    ; temporarily housed at ISI (IANA)
    ;
    . 3600000 NS L.ROOT-SERVERS.NET.
    L.ROOT-SERVERS.NET. 3600000 A 198.32.64.12
    ;
    ; housed in Japan, operated by WIDE
    ;
    . 3600000 NS M.ROOT-SERVERS.NET.
    M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33
    ; End of File
     
  14. WeinBar

    WeinBar Well-Known Member

    Joined:
    Aug 13, 2001
    Messages:
    79
    Likes Received:
    0
    Trophy Points:
    6
    are your trying to use ns3.domain.org, or just masking out your real name? If masking, is it such a secret. It would help to know this for debugging.
     
  15. jpan

    jpan Member

    Joined:
    Aug 12, 2001
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    1
    posted on 12/8/01 at 22:35
    are your trying to use ns3.domain.org, or just masking out your real name? If masking, is it such a secret. It would help to know this for debugging.
    _________________________________________
    I am just masking my real domain name...
     
  16. WeinBar

    WeinBar Well-Known Member

    Joined:
    Aug 13, 2001
    Messages:
    79
    Likes Received:
    0
    Trophy Points:
    6
    Can you post the real file so I can help you out? Masking the real domain name does nothing but add confusion and in doing so, we cannot help you.
     
  17. jpan

    jpan Member

    Joined:
    Aug 12, 2001
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    1
    Those is my file /var/log/bind
    http://www.jpadult.org/bind
    Thanks for your help....


    [quote:950e0ef235]Can you post the real file so I can help you out? Masking the real domain name does nothing but add confusion and in doing so, we cannot help you. [/quote:950e0ef235]
     
  18. WeinBar

    WeinBar Well-Known Member

    Joined:
    Aug 13, 2001
    Messages:
    79
    Likes Received:
    0
    Trophy Points:
    6
    Check the following:

    you have specified ns3 and ns4 as A records in your /var/named/jpadult.org.db file

    Also, the ns3 and ns4 records may need to be reversed. If they are not, you may want to add them.

    If it is entered correctly, stop and restart named.

    If it is not entered correctly, either add it through WHM, or add it manually (make sure you increment the serial number if you do this manually), and stop and restart named (can be done through WHM if you would like).
     
  19. jpan

    jpan Member

    Joined:
    Aug 12, 2001
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    1
    Hi:
    This is my /var/named/jpadult.org file, please tell me which one need to be change and edit, Thanks for your help...

    ; Modified by Web Host Manager
    ; Zone File for jpadult.org
    @ 14400 IN SOA ns3.jpadult.org. root.ns3.jpadult.org. (
    1006564490
    28800
    7200
    3600000
    86400
    )

    jpadult.org. 14400 IN NS ns3.jpadult.org.
    jpadult.org. 14400 IN NS ns4.jpadult.org.
    jpadult.org. 14400 IN A 209.223.116.226

    localhost.jpadult.org. 14400 IN A 127.0.0.1

    jpadult.org. 14400 IN MX 10 jpadult.org.

    mail 14400 IN CNAME jpadult.org.
    www 14400 IN CNAME jpadult.org.
    ftp 14400 IN CNAME jpadult.org.



    [quote:2bf728f5dd]Check the following:

    you have specified ns3 and ns4 as A records in your /var/named/jpadult.org.db file

    Also, the ns3 and ns4 records may need to be reversed. If they are not, you may want to add them.

    If it is entered correctly, stop and restart named.

    If it is not entered correctly, either add it through WHM, or add it manually (make sure you increment the serial number if you do this manually), and stop and restart named (can be done through WHM if you would like).

    [/quote:2bf728f5dd]
     
  20. WeinBar

    WeinBar Well-Known Member

    Joined:
    Aug 13, 2001
    Messages:
    79
    Likes Received:
    0
    Trophy Points:
    6
    Add the following:
    ns3 14400 IN A 209.223.116.225
    ns4 14400 IN A 209.223.116.226

    Also, increment your serial number ( if you are editting this manually):

    1006564490 to something HIGHER, i.e. 1006564495

    Then stop and restart named.
     
Loading...

Share This Page