Re: DNS not resolving for a particular domain only

2017-08-11 Thread U Zee via bind-users
Thanks for the suggestion Grant. Here's what I get for the recursive server's capture: ( I queried from the recursive server itself from another ssh session so it is the client as well) # tcpdump -v -v -nt -i eth0 udp port 53|grep lenovotcpdump: listening on eth0, link-type EN10MB (Ethernet),

Re: need to look up short names

2017-08-11 Thread ToddAndMargo
On 08/11/2017 02:40 PM, ToddAndMargo wrote: On 08/10/2017 07:07 PM, Grant Taylor via bind-users wrote: On 08/10/2017 06:21 PM, toddandmargo wrote: Fedora 26 Fedora = Linux (vs Windows vs other) I am stumped. I need to be able to look up short names on my local network. ... What am I

Re: need to look up short names

2017-08-11 Thread ToddAndMargo
On 08/10/2017 07:07 PM, Grant Taylor via bind-users wrote: On 08/10/2017 06:21 PM, toddandmargo wrote: Fedora 26 Fedora = Linux (vs Windows vs other) I am stumped. I need to be able to look up short names on my local network. ... What am I missing? domain and / or search configuration

Confused about SELinux error

2017-08-11 Thread ToddAndMargo
Hi All, What does this SELinux error mean when I start bin-chroot? # semanage fcontext -a -t FILE_TYPE 'session.key' where FILE_TYPE is one of the following: dnssec_trigger_var_run_t, ipa_var_lib_t, krb5_host_rcache_t, krb5_keytab_t, named_cache_t, named_log_t, named_tmp_t,

Re: need to look up short names

2017-08-11 Thread Grant Taylor via bind-users
On 08/10/2017 10:18 PM, /dev/rob0 wrote: Note that this still work for dig(1) and host(1) as per the OP's examples. But things like ping(1) and browsers will work with a search domain. Do you mean to say that the search / domain entry in /etc/resolv.conf do /not/ work for dig / host? (Or am

RE: command line ID vs Wireshark transaction ID (dns.id)

2017-08-11 Thread John W. Blue
> What nameserver addresses are listed in /etc/resolv.conf? So. resolv.conf has the non-RFC1918 ip addresses commented out *and* loopback is the only one enabled. Lovely. I decided to leave it as is and retested with: # tcpdump -n -i lo0 -s0 port domain tcpdump: verbose output

Re: bind-chroot, runs, works, dies

2017-08-11 Thread Reindl Harald
Am 11.08.2017 um 15:57 schrieb Petr Mensik: Hi Todd. I think much better than Ask Fedora would be filling a bug in bugzilla.redhat.com. I would see it straight away. I am Fedora bind maintainer. If there is bug preventing correct start of named-chroot, I would like to fix it. You would see

Re: bind-chroot, runs, works, dies

2017-08-11 Thread Petr Mensik
Hi Todd. I think much better than Ask Fedora would be filling a bug in bugzilla.redhat.com. I would see it straight away. I am Fedora bind maintainer. If there is bug preventing correct start of named-chroot, I would like to fix it. You would see SElinux errors in command "ausearch -i -ts

DNS not resolving for a particular domain only

2017-08-11 Thread U Zee via bind-users
Hi All, We are experiencing a weird issue for the past week or two.  We run bind9 on RHEL/CentOS and one of our international offices that has their own auth and caching servers cannot resolve lenovo.com for some odd reason. If that office clients use google DNS it works but using their own DNS

RE: command line ID vs Wireshark transaction ID (dns.id)

2017-08-11 Thread Philippe.Simonet
strange : by me it looks like ... : 43350 = 0xa956 >/usr/bin/dig www.google.ch ; <<>> DiG 9.10.3-P4-Debian <<>> www.google.ch ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43350 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1