Hello,
We have two nameservers,
ns5.cloudwebdns.com
ns6.cloudwebdns.com
the primary types of domains, like com/net/org/info can be setup to be
resolved by them.
But some other domsins, like .me one, can't be setup in registrar's
admin panel, saying nameserver not authorized.
Can you help wit
Hi,
ns5.cloudwebdns.com
ns6.cloudwebdns.com
For these two nameservers (they are the native BIND 9), we can use them
to resolve the other domains like .com/.net/.org/.info etc.
But when we try to setup a .me domain to be resolved by them, from the
registrar's control panel, it gets failed, s
Hello,
we are using Global Server Loadbalancing (GSLB) for site redundancy.
GSLB is based on DNS technology and works as follows
---
standard implementation case
---
www.example.com.NS loadbalancer-1.example.com.
#
Hi brothers
I have a question about dns Address record, I´m running Bind9 over d
ebian, and I wonder if is posible to add address record for a remote
host? this remote host i reach it by a site to site vpn,
this is my scenario
-dns server 192.168.10.100
-remote host 172.28.15.34
I already a
l 10 11:41:05 2013
;; MSG SIZE rcvd: 113
nslookup pc12.mydomain.com
Server: 127.0.0.1
Address:127.0.0.1#53
** server can't findpc12.mydomain.com: NXDOMAIN
Thanks for the advice, I got both commands for testing dns
On 10/07/2013 11:39 AM, Steven Carr wrote:
On 10 July 2013
Hi brothers
I have running bind9 on debian, with master zone for mydomain.com i
created internal view for resolve names on my lan, and external zone for
resolve my host on Internet, this is the working scenario
Internal view
LAN IP 192.168.0.67
Hostname sales.mydomain.com
External view
WAN I
ted responses are expected and trusted.
// root-delegation-only exclude { "DE"; "MUSEUM"; };
include "/etc/bind/named.conf.local";
logging {
category lame-servers { null; };
category edns-disabled { null; };
};
key dhcpupdate {
algorit
that described
how the views were configured.
Mark
In message <51f9a4dc.6040...@gmail.com>, IT Support writes:
Dear Carl
Thanks for your answer here the output:
acl allowed-users {
localhost;
200.57.66.77/28;
192.168.0.0/23;
189.0.0.0/8;
1
Hi Steven
Can you tell me what files do I have to post here?
On 31/07/2013 7:04 PM, Steven Carr wrote:
On 1 August 2013 00:59, IT Support wrote:
Thanks in advance.
Where is your view/zone configuration? (possibly in one of the
included files) you will need to post that configuration as well
record created for a host in external view from dns server
by a ping and i got a ping: unknown host, but if a ping to other host
with external record i got a answer.
Is there a way to fix this issue?
Thanks a lot for your support.
___
Please visit
wrote:
On Sep 25, 2013, at 10:58 AM, IT Support wrote:
Hi brothers and sisters.
Hi, anonymous IT Support person-- :-)
I´m getting some weird perfomance on BIND version 9.6 I´m running on debian,
I have internal and external view created. there are records on internal and
external views,
Hi Chuck, sorry for the mistake.
so i did the dig host2.mydomain.com and this is the result:
host2.mydomain.com @xxx.xxx.xxx.xxx
; <<>> DiG 9.6-ESV-R4 <<>>host2.mydomain.com @xxx.xxx.xxx.xxx
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33734
;; flag
w? if this is the case I already added
those records. ¿Is there another thing that I´m forgetting to do?..."
Thanks in advance.8-)
On 26/09/2013 10:13 AM, Matus UHLAR - fantomas wrote:
On 25.09.13 14:58, IT Support wrote:
too many times I´ve got advices about to dns testing using dig
comman
wrote:
On 26.09.13 10:52, IT Support wrote:
Hi Matus thanks for your answer, can you do me a favor? can you tell
me how to looking for that configuration?
only clients that are supposed to get internal private addresses
should be in internal view. "...You mean, that I should to cre
I'm sure I'm doing something wrong, but for the life of me I can't figure out
what. I'm running named 9.12 in a simple recursive setup (built from source on
CentOS 7).
In named.conf I've set:
dnssec-enable yes;
dnssec-validation auto;
When I try to run "dig txt rs.dns-oarc.net"
Good thought but no luck, it doesn’t matter how many times I run “dig txt
rs.dns-oarc.net” or how long I wait it continues to SERVFAIL until I run "dig
txt rs.dns-oarc.net +trace" Interestingly I've found that running "dig txt
dns-oarc.net +trace" isn't enough to fix it, I actually have to run "
[…]
If you want to understand why your resolver is failing, again I'd have a look
at the 'resolver' log channel. It should have some detail about what's
resulting in the SERVFAIL message.
[…]
I took a look at the ‘resolver’ log channel. I didn’t find any useful
information there, just:
fetch
Just wanted to follow up 9.12.1b1 fixes this issue for me.
Thanks,
-Nick
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/l
-Original Message-
From: NNEX Support
Sent: Thursday, February 22, 2018 8:21 AM
To: 'bind-users@lists.isc.org'
Subject: RE: Issue running "dig txt rs.dns-oarc.net" on 9.12
Just wanted to follow up 9.12.1b1 fixes this issue for
I'm sorry to keep replying to myself but I believe I've found the line of code
that is causing this issue. Looking at validator.c, in the check_deadlock
function, 9.12.0rc1 says:
...
if (parent->event != NULL &&
parent->event->type == type &&
k
-Original Message-
From: bind-users [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Cathy
Almond
Sent: Tuesday, February 27, 2018 4:29 AM
To: bind-users@lists.isc.org
Subject: Re: Issue running "dig txt rs.dns-oarc.net" on 9.12
On 22/02/2018 16:44, NNEX Support wrote:
&g
Hello,
Following the CVE cve-2024-11187 and cve-2024-12705 concerning Bind9 I have two
debian servers whose repository cannot find the update:
apt-cache policy bind9
bind9:
Installed: 1:9.18.28-1~deb12u2
Candidate: 1:9.18.28-1~deb12u2
To patch to 9.18.33 Extended Support (ES), what do you
version of BIND 9 by compiling without regular expression
support.
Compilation without regular expression support:
BIND 9.7 (all versions), BIND 9.8 (9.8.0 through 9.8.5b1),
and BIND 9.9 (9.9.0 through 9.9.3b1) can be rendered completely
safe from this bug by re-compiling
On 3/26/13 10:05 AM, Jack Tavares wrote:
I have a request for clarification:
The workaround states to rebuild BIND with regexp support disabled.
And I see new versions of BIND have been released.
Are those versions just a rebuild with regexp support disabled?
Or are they a more comprehensive
Thanks Carl,
with your fix it works:
--
Server\Bind\bin\dig.exe @81.174.15.142 swupdl.adobe.com
; <<>> DiG 9.10.1 <<>> @81.174.15.142 swupdl.adobe.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode:
Good morning,
I have those Bind versions installed:
BIND 9.10.1-x86 in a Windows Server 32 bit
BIND 9.10.1-x64 in a Windows Server 64 bit
Both versions have the SIT (Source Identity Token) EDNS option enabled by
default.
You have DiG 9.10-P1 (May 8 2014) and my problems start with 9
https://www.isc.org/blogs/hijacking-dns-error-ddos-what-happened-and-what-you-can-do/
>From ISC Support Engineering staff
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
b
27 matches
Mail list logo
