Hi All,
Thanks Andrew and Marty for your replies.
Andrew Best wrote:
> On Thu, Jan 25, 2001 at 08:57:04PM +1100, Michael Lake wrote:
> > > ;; ADDITIONAL SECTION:
> > > DNS7.CP.MSFT.NET. 1d10h15m14s IN A 207.46.138.21
> > > DNS6.CP.MSFT.NET. 1d10h15m14s IN A 207.46.138.20
> > > DNS4.CP.MSFT.NET. 9h23m57s IN A 207.46.138.11
> > > DNS5.CP.MSFT.NET. 5h48m4s IN A 207.46.138.12
> >
> > I'm not familiar with DNS but do like to learn. What's
> > actually wrong here?
>
> DNS servers are all on the same network. This is bad because if that
> network become un-reachable (as is now the case) name resolution stops.
Ah now it clicks.
> If you dig against some other zones (eg battle.net) you will see an
> example of how nameservers should be on seperate networks.
Never used dig before and didn't know it existed. Tried it
on battle.net and I see what you mean.
$ dig slashdot.org
ns1.andover.net. 12h43m38s IN A 209.207.224.196
ns2.andover.net. 1d7h43m36s IN A 209.207.224.197
ns3.andover.net. 10h29m38s IN A 209.192.217.104
so I see slashdot, run by Andover has at least another DNS
on 217 as well as the 224 net.
> Microsoft have commited a cardinal sin of DNS administration and they
> are suffering for it now. Tough nuts to them I say.
Thanks.
I have learnt something and it was easy too!
Mike
--
--------------------------------------------------------------------
Michael Lake
University of Technology, Sydney
Email: mailto:[EMAIL PROTECTED] Ph: 02 9514 1724 Fx: 02
9514 1628
URL: http://www.science.uts.edu.au/~michael-lake/
Linux enthusiast, active caver and interested in anything
technical.
--------------------------------------------------------------------
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
