DNS setup

Home Page Forums Network Management Networking DNS setup

This topic contains 4 replies, has 0 voices, and was last updated by  kphung 9 years, 6 months ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #41865

    kphung
    Member

    I set up the DNS run on zeroshell Release 1.0.beta12, found the reverse DNS not working.

    log message show
    connection refused resolving ‘xxx.xxx.xxx.203.in-addr.arpa/PTR/IN’: 203.xxx.xxx.xxx#53

    the following soa record was work fine on Release 1.0.beta9

    ***********
    99 PTR cc.bbb.com.

    xxx.xxx.xxx.203.in-addr-arpa. NS ns1.bbb.com.
    MX 10 email.bbb.com.
    MX 20 mail.bbb.com.
    A 203.xxx.xxx.123
    SOA bbb.com. root.bbb.com. 2009081411 28800 3600 604800 38400

    Any one can help!

    Thanks

    #48643

    ppalias
    Member

    try changing this

    SOA bbb.com. root.bbb.com. 2009081411 28800 3600 604800 38400 

    to this

    SOA ns1.bbb.com. root.bbb.com. 2009081411 28800 3600 604800 38400 

    Also you don’t have A records in reverse table, but this should not be a problem.

    #48644

    kphung
    Member

    Thanks ppalias

    Sorry, don’t work. 🙁

    Logging show connection refused while reverse DNS resolving.

    #48645

    ppalias
    Member

    Take a look at my example and try to be as close as possible to it.

    8		PTR	marida.trendy.awmn.
    9 PTR atherina.trendy.awmn.
    149.14.10.in-addr.arpa. NS ns0.trendy.awmn.
    NS ns1.trendy.awmn.
    NS ns2.trendy.awmn.
    SOA ns0.trendy.awmn. admin.trendy.awmn. 2009082100 10800 3600 604800 86400

    Also post any options you might have, as well as the log file during the start of the service. Last but not least post the firewall rules.

    #48646

    kphung
    Member

    Thanks I try to rebuild the file, still not work.

    Just use as router and DNS only No firewall rules had been seted
    DNS start logging as :

    10:00:27 starting BIND 9.5.1-P2
    10:00:27 adjusted limit on open files from 1024 to 1048576
    10:00:27 found 1 CPU, using 1 worker thread
    10:00:27 using up to 4096 sockets
    10:00:27 loading configuration from ‘/etc/named.conf’
    10:00:27 using default UDP/IPv4 port range: [1024, 65535]
    10:00:27 using default UDP/IPv6 port range: [1024, 65535]
    10:00:27 no IPv6 interfaces found
    10:00:27 listening on IPv4 interface lo, 127.0.0.1#53
    10:00:27 listening on IPv4 interface ETH00:00, 203.xxx.xxx.xxx#53
    10:00:27 listening on IPv4 interface ETH00:01, 192.168.0.75#53
    10:00:27 listening on IPv4 interface dummy0, 192.168.141.142#53
    10:00:27 listening on IPv4 interface VPN99:00, 192.168.250.254#53
    10:00:27 listening on IPv4 interface dummy1, 192.168.142.142#53
    10:00:27 automatic empty zone: 0.IN-ADDR.ARPA
    10:00:27 automatic empty zone: 127.IN-ADDR.ARPA
    10:00:27 automatic empty zone: 254.169.IN-ADDR.ARPA
    10:00:27 automatic empty zone: 2.0.192.IN-ADDR.ARPA
    10:00:27 automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
    10:00:27 automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
    10:00:27 automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
    10:00:27 automatic empty zone: D.F.IP6.ARPA
    10:00:27 automatic empty zone: 8.E.F.IP6.ARPA
    10:00:27 automatic empty zone: 9.E.F.IP6.ARPA
    10:00:27 automatic empty zone: A.E.F.IP6.ARPA
    10:00:27 automatic empty zone: B.E.F.IP6.ARPA
    10:00:27 command channel listening on 127.0.0.1#953
    10:00:27 zone salonmedia.com/IN: sending notifies (serial 2009081601)
    10:00:27 zone 127-64.xxx.xxx.203.in-addr-arpa/IN: sending notifies (serial 2009082502)
    10:00:34 lame server resolving ‘122.127-64.xxx.xxx.203.in-addr.arpa’ (in ‘127-64.xxx.xxx.203.in-addr.arpa’?): 203.xxx.xxx.71#53
    10:00:34 connection refused resolving ‘122.127-64.xxx.xxx.203.in-addr.arpa/PTR/IN’: 203.xxx.xxx.126#53
    10:00:40 connection refused resolving ‘122.127-64.xxx.xxx.203.in-addr.arpa/PTR/IN’: 203.xxx.xxx.126#53
    10:00:40 lame server ‘126.127-64.xxx.xxx.203.in-addr.arpa’ (in ‘127-64.xxx.xxx.203.in-addr.arpa’?): 203.xxx.xxx.71#53
    10:00:40 connection refused resolving ‘126.127-64.xxx.xxx.203.in-addr.arpa/PTR/IN’: 203.xxx.xxx.126#53
    10:00:49 connection refused resolving ‘126.127-64.xxx.xxx.203.in-addr.arpa/PTR/IN’: 203.xxx.xxx.126#53
    10:01:02 connection refused resolving ‘126.127-64.xxx.xxx.203.in-addr.arpa/PTR/IN’: 203.xxx.xxx.126#53
    10:01:15 message repeated 2 times
    10:01:28 no IPv6 interfaces found

    #48647

    kphung
    Member

    Thank All.

    the configure file was nothing wrong.

    Just because of the ISP typo they point to the wrong subnet file.

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.