Re: Error in named configuration
Posted: 2018/02/21 14:21:23
We're getting away from your DNS, but there still seems to be an oddity in resolv.conf. I can ping both servers but they do not return any name information to me. Lets see if you get the same results:
We are asking Google to do a reverse translation of 207.68.222.222. See the line near the bottom: SERVER: 8.8.8.8#53(8.8.8.8), that shows we are talking to Google and being served by it. Look at the answer section and you can see 222.222.68.207.in-addr.arpa. 1799 IN PTR 207-68-222-222.nctc.net. which is good. Now:
No server responded and no answer was returned. You can try pinging 207.68.222.222 to prove the connection exists.
Try renaming resolv.conf to resolv.conf.orig, then creating a new resolv.conf with the following contents:
and then just try $ dig 8.8.4.4.
Code: Select all
$ dig @8.8.8.8 -x 207.68.222.222
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.62.rc1.el6_9.5 <<>> @8.8.8.8 -x 207.68.222.222
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16740
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;222.222.68.207.in-addr.arpa. IN PTR
;; ANSWER SECTION:
222.222.68.207.in-addr.arpa. 1799 IN PTR 207-68-222-222.nctc.net.
;; Query time: 167 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Feb 21 14:10:17 2018
;; MSG SIZE rcvd: 82
Code: Select all
$ dig @207.68.222.222 -x 8.8.8.8
; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.62.rc1.el6_9.5 <<>> @207.68.222.222 -x 8.8.8.8
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
Try renaming resolv.conf to resolv.conf.orig, then creating a new resolv.conf with the following contents:
Code: Select all
; generated by /sbin/dhclient-script
nameserver 8.8.8.8
nameserver 8.8.4.4