Mailinglist Archive: opensuse (1477 mails)
| < Previous | Next > |
Re: [opensuse] what does 127.0.1.1 mean?
- From: lynn <lynn@xxxxxxxxxxxx>
- Date: Fri, 30 Mar 2012 21:28:27 +0200
- Message-id: <4F76095B.1080801@steve-ss.com>
On 30/03/12 19:16, Anton Aylward wrote:
I just added the reverse zone in Yast but there seems to be a conflict between it and the samba4 dlz stuff we're running.
dig -x $( ip addr show to 0.0.0.0/0 scope global | awk '/[[:space:]]inet / { print gensub("/.*","","g",$2) }' )
berized nfs
; <<>> DiG 9.8.1-P1 <<>> -x 192.168.1.3
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56925
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;3.1.168.192.in-addr.arpa. IN PTR
;; AUTHORITY SECTION:
168.192.in-addr.arpa. 86400 IN SOA 168.192.in-addr.arpa. . 0 28800 7200 604800 86400
;; Query time: 24 msec
;; SERVER: 192.168.1.3#53(192.168.1.3)
;; WHEN: Fri Mar 30 21:19:19 2012
;; MSG SIZE rcvd: 77
My workaround is to add the 127.0.1.1 as. I only need it for really fussy dns stuff like Kerberos with nfs where if you so much as breathe, bind just turns away.
I'm glad to see the Samba4 guys working on a modern replacement for bind.
L x
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx
Carlos E. R. said the following on 03/30/2012 11:15 AM:Nope. Not working.
On 2012-03-30 14:35, Anton Aylward wrote:Sorry, my finger slipped. s is next to x ...
cer@Telcontar:~> dig -s $( ip addr show to 0.0.0.0/0 scope global |Have you tried the reverse lookup? (Sorry this is complicated
but its finding the IP address in a site independent manner)
# dig -s $( ip addr show to 0.0.0.0/0 scope global | \ awk
'/[[:space:]]inet / { print gensub("/.*","","g",$2) }' )
That should give you the FQDN of your host.
\
Invalid option: -sawk '/[[:space:]]inet / { print gensub("/.*","","g",$2) }' )
As the man page makes clear, reverse lookup is "-x".
I'm sure everyone is smart enough ...
I just added the reverse zone in Yast but there seems to be a conflict between it and the samba4 dlz stuff we're running.
dig -x $( ip addr show to 0.0.0.0/0 scope global | awk '/[[:space:]]inet / { print gensub("/.*","","g",$2) }' )
berized nfs
; <<>> DiG 9.8.1-P1 <<>> -x 192.168.1.3
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56925
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;3.1.168.192.in-addr.arpa. IN PTR
;; AUTHORITY SECTION:
168.192.in-addr.arpa. 86400 IN SOA 168.192.in-addr.arpa. . 0 28800 7200 604800 86400
;; Query time: 24 msec
;; SERVER: 192.168.1.3#53(192.168.1.3)
;; WHEN: Fri Mar 30 21:19:19 2012
;; MSG SIZE rcvd: 77
My workaround is to add the 127.0.1.1 as. I only need it for really fussy dns stuff like Kerberos with nfs where if you so much as breathe, bind just turns away.
I'm glad to see the Samba4 guys working on a modern replacement for bind.
L x
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx
| < Previous | Next > |