Hi.
Please, please, please upgrade your OS and BIND.
CentOS 6 went EoS 3 years ago, from what I can tell.
BIND 9.8 is 12 years old and there have been far too many changes and
security fixes in that time to list in a mail. If you want to see for
yourself, explore https://downloads.isc.org/isc/bind
***
このメールの添付ファイルはSPC Mailエスティーにアップロードされました。
該当ファイルは以下のダウンロードページから取得してください。
ダウンロードするためのパスワード情報は、別メールで通知されます。
The attach file to this email has been uploaded to SPC Mail Estee for mail
saf
Ok, let me state that clearly again. There is no guarantee that dlv.isc.org
will be operational in the next second, next minute, next day, next month or
next year. Stop using it right now, we are not going to send any notices
because you failed to act.
Ondrej
--
Ondřej Surý — ISC (He/Him)
My w
UE:: I am using a DNS server in Japan. The DNS server failed to resolve
> the domain name on August 2, 2024. It automatically recovered after a
> while. The following message was recorded in the logs
>
> I want to know why I suddenly can't resolve names.
>
> logs::
>
>
first email. Sorry for any rough edges.ISSUE:: I am using a DNS server in Japan. The DNS server failed to resolve the domain name on August 2, 2024. It automatically recovered after a while. The following message was recorded in the logsI want to know why I suddenly can't resolve names.logs:
name on August 2, 2024. It automatically recovered after a while. The following message was recorded in the logsI want to know why I suddenly can't resolve names.logs::log1: validating @0x: dlv.isc.org DNSKEY: verify failed due to bad signature (keyid=xxx): RRSIG has expire
my first email. Sorry for any rough edges.
> ISSUE:: I am using a DNS server in Japan. The DNS server failed to resolve
> the domain name on August 2, 2024. It automatically recovered after a while.
> The following message was recorded in the logs
> I want to know why I suddenly can&#x
This will be my first email. Sorry for any rough edges.
ISSUE:: I am using a DNS server in Japan. The DNS server failed to resolve
the domain name on August 2, 2024. It automatically recovered after a
while. The following message was recorded in the logs
I want to know why I suddenly can&#
yes, true the problem is from the firewall.
Thanks everyone for the tremendous support.
Ejaz
From: Warren Kumari [mailto:war...@kumari.net]
Sent: Sunday, January 4, 2015 5:09 PM
To: Mohammed Ejaz
Cc: Barry Margolin; comp-protocols-dns-b...@isc.org
Subject: Re: can't-resolve
On 04.01.15 08:43, Mohammed Ejaz wrote:
now everything is fine once the port > 1024 opened from the network
firewall. so it means not only 53 port requires to be open.
BIND (and other DNS servers) uses random port for outgoing requests.
som you really had firewall on the path...
--
Matus UHLAR
you'd been mistaken...
W
>
>
>
> -Original Message-
> From: bind-users-boun...@lists.isc.org
> [mailto:bind-users-boun...@lists.isc.org ] On Behalf Of Ejaz
> Sent: Sunday, December 28, 2014 11:10 AM
> To: 'Warren Kumari'; 'Barry Margolin'
> Cc: co
ber 28, 2014 11:10 AM
To: 'Warren Kumari'; 'Barry Margolin'
Cc: comp-protocols-dns-b...@isc.org
Subject: RE: can't-resolve
Thanks for the suggestion
I am sure No firewall at all. Also See I now I have reassigned the my
previous IP which is 212.119.64.12, after that eve
140
> Fax: +966 11 465 4735
>
> -Original Message-
> From: bind-users-boun...@lists.isc.org
> [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Warren Kumari
> Sent: Saturday, December 27, 2014 2:27 AM
> To: Barry Margolin
> Cc: comp-protocols-dns-b...@isc.or
ocols-dns-b...@isc.org
Subject: Re: can't-resolve
Also, from querying from the outside (with TCP):
~# dig +tcp www.auth-servers.net @212.119.64.228
; <<>> DiG 9.10.1-P1 <<>> +tcp www.auth-servers.net @212.119.64.228 ;;
global options: +cmd ;; Got answer:
;; ->>H
plies (which go
>> to an ephemeral port).
>>
>>>
>>>
>>> Regards,
>>> Mohammed Ejaz
>>> CYBERIAR SAUDI ARABIA
>>> P.O.Box 301079, Riyadh 11372, Saudi Arabia
>>> Tel: +966 11 464 7114 Ext. 140
>>> Fax: +966 11 465 4
35
>>
>> -Original Message-
>> From: bind-users-boun...@lists.isc.org
>> [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Matus UHLAR -
>> fantomas
>> Sent: Friday, December 26, 2014 7:35 PM
>> To: bind-users@lists.isc.org
>> Subject: Re: can't-re
..@lists.isc.org
> [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Matus UHLAR -
> fantomas
> Sent: Friday, December 26, 2014 7:35 PM
> To: bind-users@lists.isc.org
> Subject: Re: can't-resolve
>
> On 26.12.14 19:21, Ejaz wrote:
> >When run "
: bind-users-boun...@lists.isc.org
[mailto:bind-users-boun...@lists.isc.org] On Behalf Of Matus UHLAR -
fantomas
Sent: Friday, December 26, 2014 7:35 PM
To: bind-users@lists.isc.org
Subject: Re: can't-resolve
On 26.12.14 19:21, Ejaz wrote:
>When run "dig a yahoo.com @212.119.64.228
On 26.12.14 19:21, Ejaz wrote:
When run "dig a yahoo.com @212.119.64.228 below is the ouput.
yahoo.com. (38)
17:39:41.363532 IP 212.119.64.228.37891 > 212.119.64.228.domain: 34168+
[1au] A? yahoo.com. (38)
17:39:42.246993 IP 212.119.64.228.53702 > 192.5.5.241.domain: 5
isc.org] On Behalf Of Matus UHLAR -
fantomas
Sent: Friday, December 26, 2014 6:46 PM
To: bind-users@lists.isc.org
Subject: Re: can't-resolve
>On 25.12.14 17:50, Mohammed Ejaz wrote:
>>as you said I modified the logging sections. but still external
>>domains are unable to re
On 25.12.14 17:50, Mohammed Ejaz wrote:
as you said I modified the logging sections. but still external domains
are unable to resolve. I wanted tell you one more thing when I reassign
my old IP which is 212.119.64.12 then everything works fine (I mean
interal autherative domain and external yah
UHLAR - fantomas'; bind-users@lists.isc.org
Subject: RE: can't-resolve
Query log says "Connection timed out error."
> yahoo.com
Server: [212.119.64.228]
Address: 212.119.64.228
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was
day, December 25, 2014 9:47 PM
To: bind-users@lists.isc.org
Subject: Re: can't-resolve
On 25.12.14 17:50, Mohammed Ejaz wrote:
>as you said I modified the logging sections. but still external domains
are
>unable to resolve. I wanted tell you one more thing when I reassign my
old
>
On 25.12.14 17:50, Mohammed Ejaz wrote:
as you said I modified the logging sections. but still external domains are
unable to resolve. I wanted tell you one more thing when I reassign my old
IP which is 212.119.64.12 then everything works fine (I mean interal
autherative domain and external ya
ind-users-boun...@lists.isc.org] On Behalf Of Steven Carr
Sent: Thursday, December 25, 2014 5:54 PM
To: Bind users
Subject: Re: can't-resolve
On 25 December 2014 at 14:50, Mohammed Ejaz wrote:
> I wanted tell you one more thing when I reassign my old IP which is
> 212.119.64.12 then everything w
On 25 December 2014 at 14:50, Mohammed Ejaz wrote:
> I wanted tell you one more thing when I reassign my old
> IP which is 212.119.64.12 then everything works fine (I mean interal
> autherative domain and external yahoo etc )without any problem
Check your firewall? is the new IP allowed to ta
ecember 25, 2014 12:29 PM
To: Bind users
Subject: Re: can't-resolve
On 25 December 2014 at 08:05, Mohammed Ejaz wrote:
> logging {
>
> channel querylog{
>
> file "/var/log/querylog";
> severity debug 10;
>
On 25 December 2014 at 08:05, Mohammed Ejaz wrote:
> logging {
>
> channel querylog{
>
> file "/var/log/querylog";
> severity debug 10;
> print-category yes;
> print-time yes;
> print-severi
.119.64.226
ns2 IN A 212.119.64.228
=======
-Original Message-
From: bind-users-boun...@lists.isc.org
[mailto:bind-users-boun...@lists.isc.org] On Behalf Of
Ah so this is to do with recursion.
Check the settings on the 212.119.64.228 server to ensure that
recursion is turned on and allowed for the clients that need to be
able to resolve domains that the server is not authoritative for.
You'll also have to make sure that 212.119.64.228 has unrestricted
ER: 212.119.64.228#53(212.119.64.228)
;; WHEN: Thu Dec 25 08:26:29 2014
;; MSG SIZE rcvd: 165
===
See when I tried to resolve for outside domain
On 24 December 2014 at 13:42, Mohammed Ejaz wrote:
> Any clue would be highly appreciated. thanks in advance.
What's the name of the zone so we can test from here?
Did you update the parent zone to tell it the nameserver IP for your
zone has changed?
If you explicitely try to query to the new
hello,
I cannot resolve the external domain when I change my name server IP.I
am sure for the new IP (which I am replacing with existing IP) the port 53
udp and TCP is enabled for publically.
also modifying in the named.conf in the listening section such as "
listen-on port 53
On 06/21/2011 12:59 AM, Kevin Darcy wrote:
On 6/17/2011 8:01 AM, Phil Mayers wrote:
On 17/06/11 12:10, Andrew Benton wrote:
And it works well for every domain on the internet. Except for
www.nhs.uk - I can't resolve nhs.uk
www.nhs.uk is, currently, a CNAME to www.prod.nhs.uk.akadns.net
On 6/17/2011 8:01 AM, Phil Mayers wrote:
On 17/06/11 12:10, Andrew Benton wrote:
And it works well for every domain on the internet. Except for
www.nhs.uk - I can't resolve nhs.uk
www.nhs.uk is, currently, a CNAME to
www.prod.nhs.uk.akadns.net
You might be suffering from the bind 9.8
On Friday 17 June 2011 19:53, the following was written:
> So bind-9.8.0-P2 can resolve a uk domain in Missouri but I can't get it
> to work in the UK. Could someone help me to understand why it won't
> resolve this one domain for me when it will work for other people? What
> can I do to track
Yay! I fixed it! It was a problem with my router. I went to the Netgear
website, downloaded the latest firmware and BING! It's working now:
andy:~$ dig nhs.uk
; <<>> DiG 9.8.0-P2 <<>> nhs.uk
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39092
;; flag
On Fri, 17 Jun 2011 09:22:02 -0500 (CDT)
David Forrest wrote:
> Resolves from here:
>
> [drf@maplepark ~]$ dig nhs.uk
>
> ; <<>> DiG 9.8.0-P2 <<>> nhs.uk
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 65421
> ;; flags: qr rd ra; QUERY: 1, ANSWE
> > Jun 17 12:02:38 eccles named[4689]: client 127.0.0.1#36651: query failed
> > (SERVFAIL) for nhs.uk/IN/A at query.c:6199
> >
> > As I say, for any other domain/website on the internet it works great;
> > instant response, rapid page loadingbut this one domain I ju
Hello,
On 17.06.11 17:49, Matthew Seaman wrote:
> Spam detection software, running on the system
> "lucid-nonsense.infracaninophile.co.uk", has
> identified this incoming email as possible spam. The original message
> has been attached to this so you can view it (if it isn't spam) or label
> sim
omain on the internet. Except for >>> www.nhs.uk - I can't resolve nhs.uk
>> >> www.nhs.uk is, currently, a CNAME to >> www.prod.nhs.uk.akadns.net
>> >> You might be suffering from the bind 9.8 CNAME issue. See the recent,
>> repeated discuss
:02:18 eccles named[4689]: createfetch: nhs.uk A
Jun 17 12:02:38 eccles named[4689]: client 127.0.0.1#36651: query failed
(SERVFAIL) for nhs.uk/IN/A at query.c:6199
As I say, for any other domain/website on the internet it works great;
instant response, rapid page loadingbut this one domain I just can'
On Jun 17 2011, G.W. Haywood wrote:
laptop:~$ >>> whois nhs.uk
Error for "nhs.uk".
This domain cannot be registered because it contravenes the Nominet UK
naming rules. The reason is:
the domain name contains too few parts.
WHOIS lookup made at 14:37:29 17-Jun-2011
That's j
On 17/06/11 14:40, G.W. Haywood wrote:
Hi there,
On Fri, 17 Jun 2011 Andrew Benton wrote:
I can't resolve one domain: nhs.uk
laptop:~$>>> whois nhs.uk
Error for "nhs.uk".
This domain cannot be registered because it contravenes the Nominet UK
nami
On 17/06/11 14:33, Andrew Benton wrote:
Do you mean this patch?
Yep.
http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/dns/bind98/files/patch-bin__named__query.c?rev=1.1
I've just tried it and it made no difference. I'm not convinced of this
CNAME hypothesis. Could you point me toward
Resolves from here:
[drf@maplepark ~]$ dig nhs.uk
; <<>> DiG 9.8.0-P2 <<>> nhs.uk
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 65421
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;nhs.uk.
On Fri, 17 Jun 2011 13:01:00 +0100
Phil Mayers wrote:
> On 17/06/11 12:10, Andrew Benton wrote:
> >
> > And it works well for every domain on the internet. Except for
> > www.nhs.uk - I can't resolve nhs.uk
>
> www.nhs.uk is, currently, a CNAME to
> www.prod.
Hi there,
On Fri, 17 Jun 2011 Andrew Benton wrote:
> I can't resolve one domain: nhs.uk
laptop:~$ >>> whois nhs.uk
Error for "nhs.uk".
This domain cannot be registered because it contravenes the Nominet UK
naming rules. The reason is:
the domain
On 17/06/11 12:10, Andrew Benton wrote:
And it works well for every domain on the internet. Except for
www.nhs.uk - I can't resolve nhs.uk
www.nhs.uk is, currently, a CNAME to
www.prod.nhs.uk.akadns.net
You might be suffering from the bind 9.8 CNAME issue. See the recent,
rep
net. Except for
www.nhs.uk - I can't resolve nhs.uk
named.conf looks like this:
key "rndc-key" {
algorithm hmac-md5;
secret "nothing to see here, move along";
};
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "rndc-key"; };
};
zo
50 matches
Mail list logo
