Mailinglist Archive: opensuse (818 mails)

< Previous Next >
Re: [opensuse] bind DNS: forwarders not working unless named is restarted
On 04/07/12 11:44, Per Jessen wrote:
lynn wrote:

On 04/07/12 07:57, Per Jessen wrote:
lynn wrote:

plus default "forward first". Looks fine. So, once you restart bind, forwarding to dragonet.es works? How does that look with "dig +trace google.es" ?

Right after boot:
dig google.es

; <<>> DiG 9.8.1-P1 <<>> google.es
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 49629
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;google.es. IN A

;; Query time: 9 msec
;; SERVER: 192.168.1.2#53(192.168.1.2)
;; WHEN: Wed Jul 4 19:26:46 2012
;; MSG SIZE rcvd: 27

Next, we restart named:
dig google.es

; <<>> DiG 9.8.1-P1 <<>> google.es
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58555
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;google.es. IN A

;; ANSWER SECTION:
google.es. 300 IN A 74.125.230.248
google.es. 300 IN A 74.125.230.247

;; AUTHORITY SECTION:
google.es. 338357 IN NS ns3.google.com.
google.es. 338357 IN NS ns1.google.com.
google.es. 338357 IN NS ns2.google.com.
google.es. 338357 IN NS ns4.google.com.

;; ADDITIONAL SECTION:
ns1.google.com. 334208 IN A 216.239.32.10
ns2.google.com. 334208 IN A 216.239.34.10
ns3.google.com. 334208 IN A 216.239.36.10
ns4.google.com. 334208 IN A 216.239.38.10

;; Query time: 1143 msec
;; SERVER: 192.168.1.2#53(192.168.1.2)
;; WHEN: Wed Jul 4 19:27:52 2012
;; MSG SIZE rcvd: 205

No forwarding is being done.

Now we stop named and put the forwarder in resolv.conf:
dig google.es

; <<>> DiG 9.8.1-P1 <<>> google.es
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56773
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;google.es. IN A

;; ANSWER SECTION:
google.es. 300 IN A 74.125.230.247
google.es. 300 IN A 74.125.230.248

;; AUTHORITY SECTION:
google.es. 338025 IN NS ns4.google.com.
google.es. 338025 IN NS ns1.google.com.
google.es. 338025 IN NS ns2.google.com.
google.es. 338025 IN NS ns3.google.com.

;; ADDITIONAL SECTION:
ns1.google.com. 333876 IN A 216.239.32.10
ns2.google.com. 333876 IN A 216.239.34.10
ns3.google.com. 333876 IN A 216.239.36.10
ns4.google.com. 333876 IN A 216.239.38.10

;; Query time: 291 msec
;; SERVER: 217.70.240.135#53(217.70.240.135)
;; WHEN: Wed Jul 4 19:33:25 2012
;; MSG SIZE rcvd: 205

Now we get to the DNS of our ISP.

Our Internal DNS is not starting up at boot correctly although it shows a clean startup log and it resolves our own internal suff fine.

Maybe this is the time to give up. It is not serious enough for a bugzilla. The only way I can get named to start during boot is to comment out the forwarders line. forward first doesn't work either. It always uses our internal named. I just need a way of restarting named right after boot:-(
L x

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups