from the GLTD to comcast’s DNS I even got, dig:
couldn't get address for 'dns101.comcast.net': no more at one point. Although
now it seems to be back to normal, not sure what to make of it.
Thanks for your reply Bob.
Paul
a
;; Query time: 26 msec
b
;; Query
CzbySVmj5mj5J9vscR4mYf+f X
zNGKen73GecLw+HiwwSzUG8jYkGtvNOMrj9ZbC4v+XWuq0EFcxDEhbJ
yTAq2wPMGD6evSUSDLfqYu8h
oJH9svqS06KlBjWkKQqx8X+ZIIqmUMVk ivk=
dig: couldn't get address for 'dns101.comcast.net': no more
-Original Message-
From: Mark Andrews [mailto:ma...@isc.org]
Sent: Fri
This is not really a Bind issue, but can anyone else confirm latency when
querying Comcast from the root down? I ask because this morning some of our
customers
Could not email @comcast addresses, looked at the mail server and domain not
found. I suspect my cache for Comcast timeout and when my DN
ng to your NS servers? I have a lot of stale DNS zones I want to
remove.
Thanks, Paul
-Original Message-
From: Tony Finch [mailto:d...@dotat.at]
Sent: Thursday, July 28, 2016 10:45 AM
To: Casey Deccio
Cc: Paul A ; bind-us...@isc.org
Subject: Re: getting not authoritative with som
Yes there is.
p
From: Casey Deccio [mailto:ca...@deccio.net]
Sent: Thursday, July 28, 2016 10:39 AM
To: Paul A
Cc: Tony Finch ; bind-us...@isc.org
Subject: Re: getting not authoritative with some notifies
On Thu, Jul 28, 2016 at 10:34 AM, Paul A mailto:ra...@meganet.net> >
Yes on both server and the slave and primary are listed on the NS RR. I'm
really at a loss here, the zone updates on the slave but I keep getting that
message.
Paul
-Original Message-
From: Tony Finch [mailto:d...@dotat.at]
Sent: Thursday, July 28, 2016 6:20 AM
To: Paul A
Cc: bi
I have an issue I can't seem to figure out, when I make a zone change on the
master server it sends out notifies to the slave, the slave updates the zone
once it sees the notify but I get this in the logs.
named[7062]: client xx.xx.64.2#51056: received notify for zone 'xxx: not
authoritative
reverse delegation
On 14.10.15 10:11, Paul A wrote:
>Niall my problem is the name server that delegated the reserve does look up
the record correctly.
>
>I have this in the zone,
>
>DNAME 0/24
>;;
> delegate to server
>;;
>0/24NS ns.som
.orei...@ucd.ie]
Sent: Tuesday, October 13, 2015 6:29 PM
To: Paul A
Cc: bind-users@lists.isc.org
Subject: Re: dname reverse delegation
On Tue, 13 Oct 2015 21:40:30 +0100,
Paul A wrote:
>
> I have a few /24 that I want to delegate using DNAME.
Are you expecting to save yourself trouble
I have a few /24 that I want to delegate using DNAME.
Lets says I have 192.168.13.0/24 how would I go about doing reserve on the
forwarding server using DNAME.
Currently on the forwarding server I have
NS ns.isp.com
;;
DNAME 0/24
;;
Thank you Mark for all your help in the mail list. I will try this instead,
so is this happening when an link local client is trying to query my server?
paul
-Original Message-
From: Mark Andrews [mailto:ma...@isc.org]
Sent: Tuesday, April 01, 2014 5:03 PM
To: Paul A
Cc: ca35763+b
, April 01, 2014 4:35 PM
To: bind-users@lists.isc.org
Subject: RE: socket error on ipv6 link local
I'm getting the same errors with bind-9.10.0b2.
Just a guess but I think it's related to using a HE IPv6 Tunnel and the
updated root servers.
On Tue, 1 Apr 2014, Paul A wrote:
> Date: Tu
to such
an abomination.
- Kevin
On 4/1/2014 2:31 PM, Paul A wrote:
Hi, I have been using bind 9.9.4 for awhile suddenly looking at the looks I
see lots of socket.c errors. Looking at this it seems that bind is
complaining about the link local ipv6 address , I enabled ipv6 awhile back
and I just no
Hi, I have been using bind 9.9.4 for awhile suddenly looking at the looks I
see lots of socket.c errors. Looking at this it seems that bind is
complaining about the link local ipv6 address , I enabled ipv6 awhile back
and I just noticed this.
Apr 1 13:05:32 ns1 named[18769]: connect(fe80::#53)
Thank you Cathy already informed me of that. it works with the patch.
-Original Message-
From: Jeremy C. Reed [mailto:jr...@isc.org]
Sent: Tuesday, November 26, 2013 12:20 PM
To: Paul A
Cc: bind-us...@isc.org
Subject: Re: caps compiling error
Please see
https://kb.isc.org/article/AA
@lists.isc.org
Subject: Re: caps compiling error
On 26/11/2013 16:56, Paul A wrote:
> Yeah I have compline Bind on that machine many times currently I'm on
> BIND 9.8.4-P2.
>
> Not sure what header file is missing.
>
> -Original Message-
> From: bind-u
Sent: Tuesday, November 26, 2013 11:34 AM
To: bind-users@lists.isc.org
Subject: Re: caps compiling error
On Tue, Nov 26, 2013 at 10:17:11AM -0500, Paul A wrote:
> I was trying to upgrade BIND and suddenly ran into this error with
> both version of bind I was upgrading to.
>
> I tried
I was trying to upgrade BIND and suddenly ran into this error with both
version of bind I was upgrading to.
I tried to compile, bind-9.9.4 and bind-9.8.6-P1 and I get a caps error, I
search the mailing archives and the web but didn't find much on this. As
anyone run into this and know what I'm
n't update.
paul
From: bind-users-bounces+pamaral=meganet@lists.isc.org
[mailto:bind-users-bounces+pamaral=meganet@lists.isc.org] On Behalf Of
Chris Buxton
Sent: Wednesday, February 13, 2013 12:58 PM
To: Paul A
Cc: bind-us...@isc.org
Subject: Re: SOA issue
On Feb 13, 2
Can anyone tell help me figure out why this SOA is not changing no matter
what I do. The zone was edited and has a new SOA but no matter what I do
bind doesn't reload the zone with the new SOA. I tried rndc freeze/unfreeze
and still nothing. Short of reloading bind what else can I do.
TIA, Paul
Aside from the NS issue the problem was def related to having an 6to4 ipv6
address on the eth0 interface of my name server. Once I removed that ipv6 ip
all is working well.
Which leaves me with some questions,
Does bind try on an ipv6 addr 1st? I suspect it does.
The name servers for the doma
ssage-
From: bind-users-bounces+pamaral=meganet@lists.isc.org
[mailto:bind-users-bounces+pamaral=meganet@lists.isc.org] On Behalf Of
Anand Buddhdev
Sent: Thursday, March 29, 2012 11:46 AM
To: Paul A
Cc: bind-us...@isc.org
Subject: Re: query issue
On 29/03/2012 17:35, Paul A wrote:
Hi P
Hi hoping someone with more DNS experience then me can help me figure out
this strange issue.
I have a domain kingstonmass.org that I'm having problems resolving anything
for from one NS server but it work from the other. The issue seems to be
when I query for kingstonmass.org I get stuck on th
23 matches
Mail list logo
