>I'm not sure how what you are asking for is different from the default.
Indeed, that’s what I get for reading an outdated version of the documentation!
(which didn’t mention the second field) Looks like it does everything I want…
Thanks again,
-Mathew Eis
-Original Message-
From:
On Jul 15, 2016, at 8:48 AM, Matus UHLAR - fantomas wrote:
>
> On 15.07.16 14:05, Daniel Dawalibi wrote:
>> Dig domainname -> Server failed
>
> please show us output of it.
> when 127.0.0.1 is first in /etc/resolv.conf, dig should contact localhost
> first, and the result should be the same as d
On 15.07.16 14:05, Daniel Dawalibi wrote:
Dig domainname -> Server failed
please show us output of it.
when 127.0.0.1 is first in /etc/resolv.conf, dig should contact localhost
first, and the result should be the same as dig @localhost domainname.
Dig domainname ServerIP -> Server failed
Dig
Hi,
I am curently testing a dnssec setup with the new dnssec-keymgr tool. I
created a test zone with very fast key rollover setings and very short
TTLs. (Configs below)
The automated creation of keys seems to work fine but bind behaves other
than I would have expected.
- Initial deployment looks
Yes
Dig domainname -> Server failed
Dig domainname ServerIP -> Server failed
Dig domainame localhost -> Resolving properly
-Original Message-
From: bind-users [mailto:bind-users-boun...@lists.isc.org] On Behalf Of
Matus UHLAR - fantomas
Sent: 15 July, 2016 1:02 PM
To: bind-users@lists.isc
On 15.07.16 12:05, Daniel Dawalibi wrote:
To: 'Matus UHLAR - fantomas' , bind-users@lists.isc.org
please avoid personal replies. use list-reply whenever possible.
I already did it as per below output of resolv.conf but problem persists.
do you want to say, even if you run "dig domainname" w
On 14.07.16 11:19, Sachin Patil wrote:
I am just looking into bind and want to send extra information while
querying dns bind server.
This information will be used at the bind server side to return the
resolved ip.
Do you mean something like proposed "edns client subnet" that may return
differe
Hello
I already did it as per below output of resolv.conf but problem persists.
/etc/resolv.conf
# Generated by NetworkManager
nameserver 127.0.0.1
nameserver 194.126.10.18
Regards
Daniel
-Original Message-
From: bind-users [mailto:bind-users-boun...@lists.isc.org] On Behalf Of
Matus
On 12.07.16 17:13, Daniel Dawalibi wrote:
We are facing a weird issue while resolving a specific domain name from our
authoritative DNS server running on BIND 9.10.4-P1
Server has only one public IP address.
If you try to resolve the domain using either dig or nslookup you will not
get any resu
9 matches
Mail list logo