[HCoop-Discuss] DNS issues
docelic
docelic at mire.hcoop.net
Wed Dec 19 16:54:22 EST 2007
On Wed, Dec 19, 2007 at 11:03:42AM -0800, Jeff Basham wrote:
> I just checked my domain on GoDaddy (the hcoop's wiki recommends GoDaddy)
> and they require two unique name servers. The Hcoop needs to provide its
> members with two name servers. It seems like a major oversight that
> suddenly the 'documentation'was out of date', and now you only provide one
> name server for your customers.
> As far as I know, there is not a registrar that will accept just one name
> server.
>
> Some further explaination and a action plan from the BoD of HCoop should be
> posted immediately.
Hi,
We've always provided two DNS servers minimum.
I was not the main person behind it and so I couldn't give
the big picture, but the plan was to have ns1 and ns3 as
pointers to the new infrastructure. (ns1 = deleuze, ns3 = mire).
Then, later, when Fyodor (old server) is decomissioned, we would
also point ns2 to mire. Ns3 would be left pointing at Mire not
to break configs for people who used that as their name server.
Eventually if we got a third one, ns3 could be redirected there.
So if I'm still up to date with information, users on the new
infrastructure should use ns1 and ns3, and if ns3 isn't working,
it's a bug.
-doc
> Thanks.
> On Dec 19, 2007 10:52 AM, Jeff Basham <jeff at jeffbasham.com> wrote:
>
> > Most all registrars require two NS. If NS3 is not available for our use,
> > what will be put into place to allow us a 2nd NS?
> >
> > Jeff
> >
> > On Dec 19, 2007 9:49 AM, Adam Megacz <megacz at hcoop.net> wrote:
> >
> > >
> > > Hi, Steve. The ns3.hcoop.net server is not for member use; it only
> > > serves the HCOOP.NET <http://hcoop.net/> domain and a few domains from
> > > the old (fyodor)
> > > infrastructure. Please tell your registrar to use ns1.hcoop.net.
> > >
> > > Thanks,
> > >
> > > - a
> > >
> > >
> > > "Steve Johnson" <srj at adnd.com> writes:
> > > > I posted this in the chat room this evening, with out much luck, but I
> > > > think there is an issue with NS3 not updating dns records after you
> > > > run domtool in your ~.domtool directory.
> > > >
> > > > I made some DNS changes about 5 hours ago, and NS1 updated, but NS3
> > > > has not.. Also, mire does not reflect the changes unless I specify
> > > > ns1.hcoop.net as the server when using nslookup
> > > >
> > > > fratm at mire:~/.domtool$ nslookup www.fratm.com
> > > > Server: 216.187.125.130
> > > > Address: 216.187.125.130#53
> > > >
> > > > ** server can't find www.fratm.com: NXDOMAIN
> > > >
> > > > fratm at mire:~/.domtool$ nslookup www.fratm.com ns1.hcoop.net
> > > > Server: ns1.hcoop.net
> > > > Address: 69.90.123.67#53
> > > >
> > > > Name: www.fratm.com
> > > > Address: 69.90.123.68
> > > >
> > > >
> > > > And as you can see in domtool-admin describe fratm.com it shows an A
> > > > record for www.
> > > >
> > > > fratm at mire:~/.domtool$ domtool-admin describe fratm.com
> > > > ==============================================================
> > > > Node deleuze
> > > > ==============================================================
> > > >
> > > > --------------------------------------------------------------
> > > > DNS SOA:
> > > > --------------------------------------------------------------
> > > >
> > > > master
> > > > 172800
> > > > ns1.hcoop.net
> > > >
> > > > 172800
> > > > 900
> > > > 1209600
> > > > 3600
> > > >
> > > > --------------------------------------------------------------
> > > > named.conf addition:
> > > > --------------------------------------------------------------
> > > >
> > > >
> > > > zone "fratm.com" {
> > > > type master;
> > > > file "/etc/bind/zones/fratm.com.zone";
> > > > allow-transfer {
> > > > 69.90.123.68;
> > > > };
> > > > };
> > > >
> > > > --------------------------------------------------------------
> > > > DNS zonefile contents:
> > > > --------------------------------------------------------------
> > > >
> > > > fratm.com. 172800 IN NS ns1.hcoop.net.
> > > > fratm.com. 172800 IN NS ns3.hcoop.net.
> > > > fratm.com. 172800 IN A 69.90.123.68
> > > > fratm.com. 172800 IN MX 1 aspmx.l.google.com.
> > > > fratm.com. 172800 IN MX 5
> > > alt1.aspmx.l.google.com.
> > > > fratm.com. 172800 IN MX 5
> > > alt2.aspmx.l.google.com.
> > > > fratm.com. 172800 IN MX 10 aspmx2.googlemail.com.
> > > > fratm.com. 172800 IN MX 10 aspmx3.googlemail.com
> > > .
> > > > fratm.com. 172800 IN MX 10 aspmx4.googlemail.com
> > > .
> > > > fratm.com. 172800 IN MX 10 aspmx5.googlemail.com.
> > > > www.fratm.com. 172800 IN A 69.90.123.68
> > > >
> > > > ==============================================================
> > > > Node mire
> > > > ==============================================================
> > > >
> > > > --------------------------------------------------------------
> > > > DNS SOA:
> > > > --------------------------------------------------------------
> > > >
> > > > slave
> > > > 172800
> > > > ns1.hcoop.net
> > > >
> > > > 172800
> > > > 900
> > > > 1209600
> > > > 3600
> > > >
> > > > --------------------------------------------------------------
> > > > named.conf addition:
> > > > --------------------------------------------------------------
> > > >
> > > >
> > > > zone "fratm.com" {
> > > > type slave;
> > > > file "/etc/bind/zones/fratm.com.zone";
> > > > masters { 69.90.123.67; };
> > > > };
> > > >
> > > >
> > > > So I suspect there might be an issue going on with the DNS servers.
> > > >
> > > > -Steve
> > > >
> > > > --
> > > > Blog - http://www.fratm.com/index.php/User:Fratm
> > > > "Knowing others is wisdom, knowing your self is Enlightenment." -
> > > Lao-Tzu
> > >
> > > --
> > > PGP/GPG: 5C9F F366 C9CF 2145 E770 B1B8 EFB1 462D A146 C380
> > >
> > > _______________________________________________
> > > HCoop-Discuss mailing list
> > > HCoop-Discuss at lists.hcoop.net
> > > https://lists.hcoop.net/listinfo/hcoop-discuss
> > >
> >
> >
> >
> > --
> > Jeff Basham
> > jeff at jeffbasham.com
> > http://www.jeffbasham.com
>
>
>
>
> --
> Jeff Basham
> jeff at jeffbasham.com
> http://www.jeffbasham.com
> _______________________________________________
> HCoop-Discuss mailing list
> HCoop-Discuss at lists.hcoop.net
> https://lists.hcoop.net/listinfo/hcoop-discuss
More information about the HCoop-Discuss
mailing list