Skip to main content

Issue with Bind

Comments

8 comments

  • ae9803
    Also, I would like to add that I did update the server. I currently run Centos 6.7
    0
  • Infopro
    That output is from your firewall of course. It shows us no errors, only blocks. What is the actual issue you're having? If it's DNS related, you might check the domain for issues using a site like intodns.com
    0
  • ae9803
    Hello, Thankyou so much for the reply. I have checked here, - Removed - I am not sure with those errors what seems to be the issue. BIND is up, but I cannot troubleshoot because every log that I have looked at isnt displaying issue. But, like I said, every domain that is pointed to the name servers ns1.example.com and ns2.example.com arent resolving after I updated centos. Also here is the output of DIG if this helps at all.... LOL
    ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.37.rc1.el6_7.5 <<>> example.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43564 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;example.com. IN A ;; ANSWER SECTION: example.com. 14400 IN A 158.69.xxx.xxx ;; AUTHORITY SECTION: example.com. 86400 IN NS ns2.example.com. example.com. 86400 IN NS ns1.example.com. ;; ADDITIONAL SECTION: ns1.example.com. 14400 IN A 192.95.xx.xx ns2.example.com. 14400 IN A 198.27.xx.xxx ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Dec 30 15:48:52 2015 ;; MSG SIZE rcvd: 123
    0
  • Infopro
    Check your firewall's blocked IPs list for your own IP addresses to make sure they're not blocked. You don't appear to have your DNS setup properly for the nameservers.
    0
  • ae9803
    Check your firewall's blocked IPs list for your own IP addresses to make sure they're not blocked. You don't appear to have your DNS setup properly for the nameservers.

    Everything had been set up fine before the update and I actually have been running smoothly for months before this issue... For anyone with this issue, under option fixed the issue right away. listen-on port 53 { any; }; allow-query { any; }; allow-recursion { any; };
    0
  • Infopro
    For anyone with this issue, under option fixed the issue right away.

    Under what option exactly?
    0
  • ae9803

    options { query-source port 53; listen-on port 53 { any; }; listen-on-v6 port 53 { ::1; }; directory "/var/named"; dump-file "/var/named/data/cache_dump.db"; statistics-file "/var/named/data/named_stats.txt"; memstatistics-file "/var/named/data/named_mem_stats.txt"; allow-query { any; }; allow-recursion { any; }; dnssec-enable yes; dnssec-validation yes; dnssec-lookaside auto; /* Path to ISC DLV key */ bindkeys-file "/etc/named.iscdlv.key"; managed-keys-directory "/var/named/dynamic"; };
    I guess the code wasnt picking up on the forum? Hopefully that works
    0
  • ae9803
    Though setting allow-query any is very unsafe, I cannot find away around it.... I get alot of these errors Dec 30 18:01:11 server named[30337]: client 130.207.54.136#4438: query 'ns1.example.com/AAAA/IN' denied
    0

Please sign in to leave a comment.