From: Suman Nath (sknath@cs.cmu.edu)
Date: 02/04/03
There is a confusion about whether the line "dns server=128.2.206.1"
should be deleted from the oa.cfg file.
The answer is "no, you should keep it there".
On Tue, 4 Feb 2003, Jennifer Morris wrote:
>
>
> At 08:53 AM 2/4/2003 -0800, Suman Nath wrote:
> >You should use the server 128.2.206.1 in your oa.cfg file. Why did you
> >delete that line?
> >
> >Delete the existing DNS entires (by delete command) before adding them again
> >(by addfile, breakfile)
>
>
>
> I thought I was supposed to. Here's the email thread from the mailing list
> that told us to do that.
>
> -Jen
>
>
>
> To: irisnet-course@intel-iris.net
> Subject: Re: dns
>
> I used the workaround proposed by Suman, and deleted the dns server line
> from oa.cfg. However, my machine still resolves the relevant IPs to
> 10.212.3.33. I used dig to check the dsan.net server, and it has the
> correct IP.
>
> Apparently the DNS server I am using is caching the old value. Is there a
> way to fix this?
>
> Thanks,
>
> Jim
>
> On Sat, 1 Feb 2003, mukesh agrawal wrote:
>
> >
> > Short answer: The problem is the "dns server" line in the oa.cfg file.
> > Delete it (or comment it out), and your troubles will go away.
> >
> > Long answer:
> >
> > In order to update DNS, the OA has to send the new information to a DNS
> > server. The "DNS server" line tells the OA the IP address of the DNS
> > server to contact. Unfortunately, the value that's in the oa.cfg file
> > seems to be incorrect. It does not match the address of the nameserver
> > that is responsible for answering queries for dsan.net.
> >
> > When you delete the "dns server" line, the software that's responsible for
> > updating DNS figures out which DNS server to contact automatically.
> >
> > > According to the project description document, when we do the 'addfile'
> > > command, DNS should be updated appropriately. Is this true? It does not
> > > appear to be happening. In my xml file I have owner-sensor set to my own
> > > IP, but DNS doesn't seem to be changed.
> > >
> > > At this point, CannedQueries is failing because it can't contact the right
> > > server (WH.CMU.Oakland.jnewsomePTROOT.dsan.net), which resolves to
> > > 10.212.3.33. This appears to be a default, as any_random_string.dsan.net
> > > resolves to the same IP.
> >
> >
> >
>
>
This archive was generated by hypermail 2.1.5 : 06/10/04 EDT