Bob Bishop wrote:
Hi,
On 7 Apr 2009, at 19:35, Aryeh M. Friedman wrote:
I have registered and pointed to my name server the following domains:
istudentunion.com (.net and .org) [etc]
Actually, the registrar only seems to have delegated istudentunion.net
I'm not sure that using a CNAME for
Hi,
On 7 Apr 2009, at 19:35, Aryeh M. Friedman wrote:
I have registered and pointed to my name server the following domains:
istudentunion.com (.net and .org) [etc]
Actually, the registrar only seems to have delegated istudentunion.net
I'm not sure that using a CNAME for the server(s) is a
I have registered and pointed to my name server the following domains:
istudentunion.com (.net and .org)
They resolve locally but do not resolve remotely it has been 24 hrs
so some propagation should of occured... I tested resolving remotely
with hardcoding the nameserver to be me and that
> I have registered and pointed to my name server the following domains:
>
> istudentunion.com (.net and .org)
>
> They resolve locally but do not resolve remotely it has been 24 hrs
> so some propagation should of occured... I tested resolving remotely
> with hardcoding the nameserver to be
Aryeh M. Friedman wrote:
Already did (went a step farther had my machine at home -CURRENT use
the one at work [the one with the probldem] as it's /etc/resolv.conf
and as a forwarder in my named.conf and both worked fine)
Forgot to mention that different ISP's so it is not a port blocking prob
Already did (went a step farther had my machine at home -CURRENT use the
one at work [the one with the probldem] as it's /etc/resolv.conf and as
a forwarder in my named.conf and both worked fine)
Xin LI wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aryeh M. Friedman wrote:
I have r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aryeh M. Friedman wrote:
> I have registered and pointed to my name server the following domains:
>
> istudentunion.com (.net and .org)
>
> They resolve locally but do not resolve remotely it has been 24 hrs
> so some propagation should of occure
Stupid configuration error on my part. I still had my old ISP's name
servers configured in my named.conf forwarders statement, and they
have apparently been responding to me for eighteen months -- until
two days ago. Sorry for the noise! -- George Mitchell
_
> From: Matthew Seaman <[EMAIL PROTECTED]>
> [EMAIL PROTECTED] wrote:
> > I'm having severe DNS problems. I'm running 6.2-RELEASE, and I upgrade=
> d
> > to the bind9 port (after cvsup) on July 14. Starting yesterday morning=
> ,
> > DNS became v
[EMAIL PROTECTED] wrote:
I'm having severe DNS problems. I'm running 6.2-RELEASE, and I upgraded
to the bind9 port (after cvsup) on July 14. Starting yesterday morning,
DNS became very, very slow. If I repeated a "dig" command three or four
times, I could get an answer
I'm having severe DNS problems. I'm running 6.2-RELEASE, and I upgraded
to the bind9 port (after cvsup) on July 14. Starting yesterday morning,
DNS became very, very slow. If I repeated a "dig" command three or four
times, I could get an answer after 20-30 seconds. Thi
11 matches
Mail list logo
